Index of every page on this site: llms.txt
All skills
wix avatar

/wix-manage

@e2bc48e official
by Wix.comwix/skills40 stars
42
Run it yourself

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, donations, payments, CMS, and more — and to publish HTML, CSS and JavaScript files as a live Wix site, with or without a Wix account. 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: automations, stores, bookings, donations, get-paid, CMS, contacts, forms, media, app-installation, custom-apps, pricing-plans, restaurants, ricos rich-content, sites, collaborators, studio-workspace, blog, calendar, domains, events, site-properties, ecommerce, marketing, online-programs, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referenceseventsevent-schedule-policies-and-categories.md

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

Event Schedule, Policies and Categories

Goal

Set up what appears around an event on its page: the schedule, policies and categories. Each call takes the event's id — find it first with the query below. The event's URL slug, public guest list, details page and online conferencing are event updates, in Manage Wix Events.

Find the event by its title — this exact body:

curl -X POST 'https://www.wixapis.com/events/v3/events/query' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "query": {
      "filter": { "title": { "$eq": "<EVENT_TITLE>" } },
      "paging": { "limit": 100 }
    },
    "fields": ["DETAILS"]
  }'
  • paging is a sibling of filter inside query; nested inside filter it fails 400.
  • Don't send includeDrafts unless the user says the event is a draft — true needs a draft-events permission. If it fails 403, say draft events aren't readable from this connection.
  • The id is events[].id. If several events match, pick by date or ask (Manage Wix Events).

Reference pages for the calls below — the full contract of each; use these rather than searching for them:

Part Reference
Find the event, turn the schedule section on Query Events, Update Event
Schedule Add Schedule Item, Publish Draft, Query Schedule Items, Get Schedule Item, Update Schedule Item, Delete Schedule Item, Discard Draft
Policies Create Policy, Query Policies, Update Policy, Delete Policy, Reorder Event Policies
Categories Query Categories, Create Category, Bulk Create Category, Update Category, Delete Category, Assign Events, Unassign Events, List Event Categories, Reorder Category Events

The request bodies below are complete for the common path; the reference pages are for the fields this recipe doesn't use.

Schedule (agenda)

Item calls write to a draft schedule. Always run all three steps: add the items, publish the draft, then turn the schedule section on — skipping either of the last two leaves the event page without the schedule.

Use https://www.wixapis.com/events/v1/schedule. Some reference examples show https://www.wixapis.com/events/v1/agenda, which is not served.

1. Add items — one call per item, POST https://www.wixapis.com/events/v1/schedule/draft:

curl -X POST 'https://www.wixapis.com/events/v1/schedule/draft' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "eventId": "<EVENT_ID>",
    "item": {
      "name": "Doors open",
      "timeSlot": {
        "start": "2026-11-20T23:00:00Z",
        "end": "2026-11-21T00:00:00Z",
        "timeZoneId": "America/New_York"
      },
      "stageName": "Main hall",
      "tags": ["Welcome"]
    }
  }'
  • name (up to 120 characters) and timeSlot.start / timeSlot.end are required. Times are ISO-8601; work them out in the event's time zone and send that timeZoneId (the default is UTC).
  • Optional: description (up to 10,000), stageName (up to 30), tags (up to 5, each up to 30), hidden. Several items can share a time slot.
  • The response is { "item": { "id", ... } }.

2. Publish: POST https://www.wixapis.com/events/v1/schedule/publish with { "eventId": "<EVENT_ID>" }.

3. Turn the section on if it isn't: PATCH https://www.wixapis.com/events/v3/events/<EVENT_ID> with { "event": { "agendaSettings": { "enabled": true } }, "fields": ["AGENDA"] }.

Confirm from the three responses — each add returns the item's id, publish returns 2xx, and the update returns agendaSettings.enabled: true. No separate read of the schedule is needed.

Read the schedule — only to list or change items that already exist: POST https://www.wixapis.com/events/v1/schedule/query with { "query": { "filter": { "eventId": { "$eq": "<EVENT_ID>" } }, "paging": { "limit": 100 } } } returns items[]. Use this call to list items, not the GET list. One item: GET https://www.wixapis.com/events/v1/schedule/<ITEM_ID>?eventId=<EVENT_ID>&includeDraft=true.

Change items (then publish again):

  • Edit: PATCH https://www.wixapis.com/events/v1/schedule/draft/<ITEM_ID> with { "eventId": "<EVENT_ID>", "item": { "name": "Keynote" }, "fields": { "paths": ["item.name"] } }. Always send fields.paths, one path per field you change — without it the item is replaced by what you sent, and every field you left out (name, tags, time slot) is cleared.
  • Hide or cancel an item: "hidden": true or "status": "CANCELED" the same way (SCHEDULED to restore).
  • Delete: confirm with the user first, then DELETE https://www.wixapis.com/events/v1/schedule/draft/items?eventId=<EVENT_ID>&itemIds=<ITEM_ID>.
  • Discard all unpublished changes: confirm with the user first, then DELETE https://www.wixapis.com/events/v1/schedule/draft?eventId=<EVENT_ID>.
  • After moving the event's date or time, update each item's timeSlot the same way, then publish.

Policies

An event takes up to 3 policies; a fourth fails 428 POLICIES_LIMIT_REACHED — list them first and offer to edit one instead. The examples use https://www.wixapis.com/events/v2/policies; the reference's https://www.wixapis.com/events-policies/v2/policies is the same API.

  • Create: POST https://www.wixapis.com/events/v2/policies
{ "policy": { "eventId": "<EVENT_ID>", "name": "Refund policy", "body": "Tickets are refundable up to <b>7 days</b> before the event." } }

name 1–40 characters; body 1–50,000 and may use simple HTML (<p>, <b>, <ul>).

  • List: POST https://www.wixapis.com/events/v2/policies/query with { "query": { "filter": { "eventId": { "$eq": "<EVENT_ID>" } } } } → policies[] with id and revision.
  • Edit: PATCH https://www.wixapis.com/events/v2/policies/<POLICY_ID> with all of id, revision (current), eventId, name and body under policy.
  • Delete: confirm with the user first, then DELETE https://www.wixapis.com/events/v2/policies/<POLICY_ID>.
  • Reorder: POST https://www.wixapis.com/events/v2/policies/reorder with eventId, policyId, and exactly one of beforePolicyId / afterPolicyId.

Categories

Categories are site-wide; create one once, then assign events to it. An event can be in several.

  • List categories: POST https://www.wixapis.com/events/v1/categories/query with { "query": { "paging": { "limit": 100 } }, "fieldset": ["COUNTS"] } → categories[] (id, name, states) and metaData.
  • Create: POST https://www.wixapis.com/events/v1/categories with { "category": { "name": "Workshops" } } (name 1–30). Several at once (up to 10): POST https://www.wixapis.com/events/v1/bulk/categories/create with { "categories": [ { "name": "..." } ] }.
  • Rename: PATCH https://www.wixapis.com/events/v1/categories/<CATEGORY_ID> with { "category": { "id": "<CATEGORY_ID>", "name": "New name" } }.
  • Delete: confirm with the user first, then DELETE https://www.wixapis.com/events/v1/categories/<CATEGORY_ID> — the events stay.
  • Add events to a category: POST https://www.wixapis.com/events/v1/categories/<CATEGORY_ID>/events with { "eventId": ["<EVENT_ID>", "<EVENT_ID>"] } (up to 100).
  • Remove events from a category: DELETE https://www.wixapis.com/events/v1/categories/<CATEGORY_ID>/events?eventId=<EVENT_ID>&eventId=<EVENT_ID>.
  • An event's categories: GET https://www.wixapis.com/events/v1/categories/<EVENT_ID> (the path takes the event id), or Get Event with fields=CATEGORIES.
  • Order events within a category: POST https://www.wixapis.com/events/v1/categories/<CATEGORY_ID>/reorder with eventId and one of beforeEventId / afterEventId.

Leave categories in the RECURRING_EVENT state alone — don't rename them or assign events to them; create and assign MANUAL categories (the default). You may delete a RECURRING_EVENT category whose series has been deleted.

Related APIs

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alerttoday4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill is a comprehensive management tool for Wix sites. It contains potential security risks such as an indirect prompt injection surface from site scraping and the ability to define JavaScript-based automation logic, but it includes strong requirements for user confirmation before any site changes.

  • Sockettoday

    No alerts

  • Snyk1d

    Risk: CRITICAL · 3 issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub yesterday.

Activeupdated 4 days ago
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.