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.

referencescmscms-schema-management.md

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

CMS Schema Management

Standard call shape (every curl below). The <AUTH> placeholder is shorthand for Authorization: Bearer <TOKEN> only. Body-bearing requests also need Content-Type: application/json.

This recipe covers managing the structure (schema) of Wix CMS collections using the REST API.

Prerequisites

  1. Wix CMS application installed on the site (appDefId: e593b0bd-b783-45b8-97c2-873d42aacaf4)
  2. API access with CMS permissions (Manage Data Collections scope)

Required APIs

  • Collections API: REST

List All Collections

Lightweight listing (recommended for existence checks):

curl -X GET \
'https://www.wixapis.com/wix-data/v2/collections?fields=displayName' \
-H 'Authorization: <AUTH>'

Full listing (includes all field schemas):

curl -X GET \
'https://www.wixapis.com/wix-data/v2/collections' \
-H 'Authorization: <AUTH>'

Collection Types: NATIVE (user-created), WIX_APP (Wix app collections), BLOCKS_APP, EXTERNAL

Get Collection Schema

Endpoint: GET https://www.wixapis.com/wix-data/v2/collections/{collectionId}

curl -X GET \
'https://www.wixapis.com/wix-data/v2/collections/Products' \
-H 'Authorization: <AUTH>'

Create a New Collection

Endpoint: POST https://www.wixapis.com/wix-data/v2/collections

{
  "collection": {
    "id": "Products",
    "displayName": "Products",
    "fields": [
      {"key": "title", "displayName": "Title", "type": "TEXT", "required": true},
      {"key": "price", "displayName": "Price", "type": "NUMBER"},
      {"key": "description", "displayName": "Description", "type": "TEXT"},
      {"key": "inStock", "displayName": "In Stock", "type": "BOOLEAN"}
    ],
    "permissions": {
      "insert": "ADMIN",
      "update": "ADMIN",
      "remove": "ADMIN",
      "read": "ANYONE"
    }
  }
}

Add a Field to Existing Collection

Endpoint: POST https://www.wixapis.com/wix-data/v2/collections/create-field

{
  "dataCollectionId": "Products",
  "field": {
    "key": "sku",
    "displayName": "SKU",
    "type": "TEXT",
    "description": "Product SKU code"
  }
}

Add a Reference Field

Same endpoint as above: POST https://www.wixapis.com/wix-data/v2/collections/create-field. The two bodies below differ only in type and typeMetadata; omitting typeMetadata fails with WDE0075 (see Error Handling).

Type Field Type Relationship Example
Single Reference REFERENCE One-to-one, Many-to-one Product → Category
Multi-Reference MULTI_REFERENCE One-to-many, Many-to-many Product → Tags

Single reference — typeMetadata.reference names the referenced collection:

{
  "dataCollectionId": "Products",
  "field": {
    "key": "category",
    "displayName": "Category",
    "type": "REFERENCE",
    "typeMetadata": {
      "reference": {
        "referencedCollectionId": "Categories"
      }
    }
  }
}

Multi-reference — typeMetadata.multiReference also names the field created on the other collection:

{
  "dataCollectionId": "Products",
  "field": {
    "key": "tags",
    "displayName": "Tags",
    "type": "MULTI_REFERENCE",
    "typeMetadata": {
      "multiReference": {
        "referencedCollectionId": "Tags",
        "referencingFieldKey": "products",
        "referencingDisplayName": "Products"
      }
    }
  }
}

To link items through these fields, see Reference Fields in the CMS Data Items CRUD recipe.

Delete a Field from Collection

Warning: This permanently deletes all data stored in this field across all items.

Endpoint: POST https://www.wixapis.com/wix-data/v2/collections/delete-field

{
  "dataCollectionId": "Products",
  "fieldKey": "sku"
}

Update Collection Settings

Endpoint: PATCH https://www.wixapis.com/wix-data/v2/collections/{collectionId}

{
  "dataCollection": {
    "id": "Products",
    "displayName": "Product Catalog"
  }
}

This works for displayName/displayField. Permission updates currently fail with WDE0075: Not recognized role provided in permissions. Use the full-replace endpoint below to update a collection's permissions.

To change permissions on an existing collection, use the full-replace endpoint instead (UpdateDataCollection, not PatchDataCollection) — it requires the collection's current revision and full fields array (get both from a GET first), but it does work:

Endpoint: PUT https://www.wixapis.com/wix-data/v2/collections

{
  "collection": {
    "id": "Products",
    "revision": "3",
    "displayName": "Product Catalog",
    "fields": [ /* the collection's full current non-system fields, from GET */ ],
    "permissions": {
      "insert": "ADMIN",
      "update": "ADMIN",
      "remove": "ADMIN",
      "read": "SITE_MEMBER"
    }
  }
}

Don't delete and recreate a collection just to change its permissions — this full-replace call is the working path.

Field Types Reference

Type Description Example Value
TEXT String "Hello World"
NUMBER Numeric 99.99
BOOLEAN True/false true
DATE Date only "2024-01-15"
DATETIME Date and time { "$date": "2024-01-15T10:00:00.000Z" }
IMAGE Image reference "wix:image://v1/..."
MEDIA_IMAGE Wix Media Image { "id": "<mediaId>", "url": "http://...", "height": 640, "width": 480, "altText": "Picture" }
MEDIA_VECTOR_ART Wix Media Vector Art { "uri": "wix:vector://v1/...", "viewBox": "0 0 100 100", "contentType": "shape", "svgContent": "<svg>...</svg>" }
URL Web URL "https://example.com"
RICH_TEXT HTML content "<p>Rich text</p>"
ARRAY_STRING Array of strings ["tag1", "tag2"]
OBJECT JSON object {"key": "value"}
REFERENCE Single reference Item ID string
MULTI_REFERENCE Multiple references Array of IDs

Permission Levels

Role Description
ANYONE All visitors (including anonymous)
SITE_MEMBER Logged-in site members
SITE_MEMBER_AUTHOR Members who created the item
PRIVILEGED Access to collection is controlled per role
ADMIN Site admins only

Error Handling

Error Cause Solution
WDE0075 (Metadata for Reference type field not provided) create-field with type REFERENCE or MULTI_REFERENCE but no typeMetadata Send typeMetadata.reference.referencedCollectionId (or typeMetadata.multiReference…), see Add a Reference Field
WDE0075 (Not recognized role provided in permissions) PATCH /collections/{id} with a permissions change Use the full-replace PUT /collections (see Update Collection Settings) or the Data Permissions API
WDE0110 Wix CMS (Wix Data) app is not installed on the site Install it: POST https://www.wixapis.com/apps-installer-service/v1/app-instance/install with body {"tenant":{"tenantType":"SITE","id":"<SITE_ID>"},"appInstance":{"appDefId":"e593b0bd-b783-45b8-97c2-873d42aacaf4"}}, then retry. See the Install Wix Apps recipe.

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.