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.

referencesstorescreate-product-catalog-v1.md

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

RECIPE: Business Recipe - Create Product (Catalog V1)

STEP 1: Create a Simple Product

Use POST https://www.wixapis.com/stores/v1/products to create a product.

CRITICAL: Description accepts an HTML string in V1 (unlike V3 which requires rich text nodes).

curl -X POST 'https://www.wixapis.com/stores/v1/products' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{
  "product": {
    "name": "Air Max Runner",
    "description": "<p>Premium running sneaker with advanced cushioning technology.</p>",
    "visible": true,
    "productType": "physical",
    "priceData": {
      "price": 129.99
    }
  }
}'

Key V1 fields:

Field Type Notes
name string Required. Max 80 characters
description string HTML string — NOT rich text nodes (e.g. "<p>text</p>")
productType string "physical" only (digital not supported via API)
priceData.price number Product base price
visible boolean Whether the product is visible to customers

STEP 2: Create a Product with Options

In V1, options are defined via productOptions. Variants are auto-generated from the choices — you do not need to define them manually.

curl -X POST 'https://www.wixapis.com/stores/v1/products' \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH>' \
-d '{
  "product": {
    "name": "Colombian Arabica",
    "description": "<p>The best organic coffee that Colombia has to offer.</p>",
    "visible": true,
    "productType": "physical",
    "priceData": {
      "price": 35
    },
    "productOptions": [
      {
        "name": "Weight",
        "optionType": "drop_down",
        "choices": [
          { "value": "250g", "description": "250g", "inStock": true, "visible": true },
          { "value": "500g", "description": "500g", "inStock": true, "visible": true }
        ]
      },
      {
        "name": "Ground for",
        "optionType": "drop_down",
        "choices": [
          { "value": "Stovetop", "description": "Stovetop", "inStock": true, "visible": true },
          { "value": "Filter", "description": "Filter", "inStock": true, "visible": true }
        ]
      }
    ]
  }
}'

V1 Options structure:

  • optionType: "drop_down" for text choices, "color" for color swatches
  • choices[].description: Display name shown to customers
  • choices[].value: Internal value (use hex color code for color type, e.g. "#000000")
  • choices[].inStock: Whether this choice is in stock
  • choices[].visible: Whether this choice is visible to customers

Variants in V1 responses are returned as an object with option name keys:

"choices": {
  "Weight": "250g",
  "Ground for": "Stovetop"
}

This is different from V3 which uses an array structure.


Key Differences from V3

Feature Catalog V1 Catalog V3
Create endpoint POST /stores/v1/products POST /stores/v3/products
Description HTML string ("<p>text</p>") Rich text nodes object
Options field productOptions options
Option type field optionType (drop_down, color) optionRenderType (TEXT_CHOICES, SWATCH_CHOICES)
Choice visibility choices[].visible choices[].isVisible
Variants Auto-generated from choices Must be explicitly defined in variantsInfo.variants
Variant choices Object: {"Weight": "250g"} Array of optionChoiceNames
Price field priceData.price (number) price.actualPrice.amount (string)

Important Notes

  • Never use /stores/v3/ endpoints on a CATALOG_V1 site — they return 428 Precondition Required.
  • Check the site's catalog version in dynamic context before choosing endpoints.
  • productType only supports "physical" via the API.
  • To add media to a product, use the separate Add Product Media endpoint after creation.
  • To query products on a V1 site, see Query Products (Catalog V1).

References

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.