All skills
wix avatar

/wix-manage

@4895cc9 official
by Wix.comwix/skills33 stars
33

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, payments, CMS, and more. Open the matching recipe for the exact endpoint, method, and payload before calling — never guess a Wix API, never write Wix dashboard URL from memory. Routes to: stores, bookings, get-paid, CMS, contacts, forms, media, app-installation, pricing-plans, restaurants, ricos rich-content, sites, blog, calendar, domains, events, site-properties, ecommerce, marketing, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-manage

This session only. Nothing lands on disk.

referencesecommerceshippingecom-shipping-setup-pickup.md

≈1.8k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Set Up Store Pickup Location

Routing rule: BEFORE taking any action, call ReadFullDocsArticle on Shipping API Reference. The endpoint shapes for List Installed Delivery Carriers, Query Delivery Profiles, Add Delivery Region, and Add Delivery Carrier all live there. Do NOT call any of these APIs without loading it first.

Prerequisites

  • Wix Stores (or another eCommerce business solution) installed on the site
  • The Pickup carrier must be installed on the site (it is a built-in carrier, not a third-party app)

Required APIs


Step 1: Discover the Pickup carrier

Call List Installed Delivery Carriers to find the Pickup carrier's id.

Endpoint: GET https://www.wixapis.com/ecom/v1/delivery-profiles/installed-carriers

Response:

{
  "installedDeliveryCarriers": [
    {
      "id": "50d8c12f-715e-41ad-be25-d0f61375dbee",
      "displayName": "Pickup",
      "fallbackDefinitionMandatory": false,
      "toggleGetCarrierSettingsEnabled": true
    },
    {
      "id": "45c44b27-ca7b-4891-8c0d-1747d588b835",
      "displayName": "Basic Shipping",
      "description": "Manage shipping rates and options for this region",
      "fallbackDefinitionMandatory": false,
      "toggleGetCarrierSettingsEnabled": true
    }
  ]
}

Look for the carrier with "displayName": "Pickup" and save its id. This is the appId you will use in Step 4.

If no Pickup carrier appears in the list, the Pickup app is not installed on the site and must be installed before proceeding.


Step 2: Find the default delivery profile

Call Query Delivery Profiles to retrieve the site's default delivery profile.

Endpoint: POST https://www.wixapis.com/ecom/v1/delivery-profiles/query

Request:

{}

The response contains an array of deliveryProfiles. Find the one where "default": true. Save its id and revision. Inspect its deliveryRegions array.

Decision point:

  • Region exists for the user's country (match on destinations[].countryCode): save that region's id → skip to Step 4.
  • No matching region: proceed to Step 3.

Step 3: Add a delivery region for the pickup country

If no region exists for the user's country in the default profile, call Add Delivery Region to create one.

Endpoint: POST https://www.wixapis.com/ecom/v1/delivery-profiles/{deliveryProfileId}/delivery-region

Replace {deliveryProfileId} with the default profile's id from Step 2.

Request:

{
  "deliveryRegion": {
    "name": "US Pickup",
    "active": true,
    "destinations": [
      {
        "countryCode": "US"
      }
    ]
  },
  "revision": "3"
}
  • name: descriptive, e.g. "{Country} Pickup".
  • countryCode: ISO-3166 alpha-2 code (e.g. "US", "IL", "DE", "GB").
  • revision: from the profile returned in Step 2.

Response:

{
  "deliveryProfile": {
    "id": "02625bf4-70b4-49b7-93f0-5c9d72608937",
    "name": "General profile",
    "default": true,
    "deliveryRegions": [
      {
        "id": "23823d4a-0ad2-4f92-a48a-467497a9470a",
        "name": "US Pickup",
        "active": true,
        "deliveryCarriers": [],
        "destinations": [
          {
            "countryCode": "US",
            "subdivisions": []
          }
        ]
      }
    ],
    "revision": "4"
  }
}

Save the new region's id from the response.


Step 4: Add the Pickup carrier to the region

Call Add Delivery Carrier to attach the Pickup carrier to the delivery region.

Endpoint: POST https://www.wixapis.com/ecom/v1/delivery-profiles/add-delivery-carrier

Request:

{
  "deliveryRegionId": "<REGION_ID>",
  "deliveryCarrier": {
    "appId": "50d8c12f-715e-41ad-be25-d0f61375dbee",
    "backupRate": {
      "title": "Pickup at 123 Main St, New York",
      "amount": "0",
      "active": true
    }
  }
}
  • deliveryRegionId: from Step 2 (existing region) or Step 3 (new region).
  • appId: the Pickup carrier id from Step 1.
  • backupRate.title: the pickup address customers see at checkout.
  • backupRate.amount: "0" for free pickup, or a price string like "5.00".
  • backupRate.active: must be true for the option to appear at checkout.

Response:

{
  "deliveryProfile": {
    "id": "02625bf4-70b4-49b7-93f0-5c9d72608937",
    "name": "General profile",
    "default": true,
    "deliveryRegions": [
      {
        "id": "23823d4a-0ad2-4f92-a48a-467497a9470a",
        "name": "US Pickup",
        "active": true,
        "deliveryCarriers": [
          {
            "appId": "50d8c12f-715e-41ad-be25-d0f61375dbee",
            "backupRate": {
              "title": "Pickup at 123 Main St, New York",
              "amount": "0",
              "active": true
            },
            "additionalCharges": []
          }
        ],
        "destinations": [
          {
            "countryCode": "US",
            "subdivisions": []
          }
        ]
      }
    ],
    "revision": "5"
  }
}

Error Handling

Error Cause Fix
DESTINATIONS_COLLISION The country is already assigned to another region in the same profile. Skip Step 3 — use the existing region's id and add the carrier to it in Step 4.
CARRIER_ALREADY_EXISTS_IN_REGION The Pickup carrier is already configured in this region. The pickup option is already set up. No action needed.
DELIVERY_CARRIER_MISSING_BACKUP_RATE The backupRate or backupRate.amount field is missing. Ensure backupRate includes title, amount, and active.

Related Documentation

Source: SKILL.md on GitHub

1 warning1d4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The wix-manage skill is an extensive collection of management recipes for Wix sites, covering business solutions such as eCommerce, Bookings, SEO, and site provisioning. It utilizes official Wix REST endpoints and incorporates robust safety patterns, including mandatory user confirmation for sensitive operations and careful validation of site data before mutation.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4895cc9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
compatibility
Requires Wix REST API access (API key or OAuth).
  • wix
  • rest-api
  • ecommerce
  • bookings
  • cms
  • contacts
  • blog
  • domains
  • restaurants
  • site-configuration
  • api-integration

README badge

README badge for wix/skills/wix-manage

REST API operations for configuring Wix business solutions including stores, bookings, CMS, contacts, domains, and ecommerce. Routes to site setup, entity management (products, services, staff), bulk administrative operations, and server-to-server integrations across Wix's business app ecosystem.

Generated from the current SKILL.md.

Do I need API credentials to use these recipes?
Yes. The skill requires Wix REST API access via either an API key or OAuth token to execute any management operations.
Can I use these recipes to display data on my site frontend?
No. These recipes are for backend REST API operations only — site configuration, entity management, and administrative tasks. They do not cover frontend development or displaying data to users.
What business domains do these recipes cover?
The skill covers stores, bookings, payments, CMS, contacts, forms, media, apps, pricing plans, restaurants, rich content, sites, blogs, calendars, domains, and site properties.
Do these recipes handle OAuth authentication with external services like Google Calendar?
Yes. The external calendar integration recipe covers OAuth-based setup with Google Calendar, Microsoft Outlook, and Apple Calendar for bidirectional event sync.

Generated from the current SKILL.md. These answers refresh after source changes.