/wix-manage

Manage Wix Events — Publishing, Cancelling, Cloning and Counting

Goal

Operate on events that already exist. Creating an event — including its date, location, description, guest limit, ticket tiers and recurring occurrences — is Create an Event.

Prerequisite — the Wix Events app

Every endpoint here returns 428 WIX_EVENTS_APP_NOT_INSTALLED against a site without the app. Install it first — do not guess the install path:

curl -X POST 'https://www.wixapis.com/apps-installer-service/v1/app-instance/install' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "tenant": { "tenantType": "SITE", "id": "<SITE_ID>" },
    "appInstance": { "appDefId": "140603ad-af8d-84a5-2c80-a0f60cb47351" }
  }'

appDefId nests under appInstance, not at the root — at the root it fails with 400 appInstance must not be empty. See Install Wix Apps.

Find an event

Every action below takes an eventId. When the user names the event instead, look it up with POST /events/v3/events/query — title supports $eq and, for several names at once, $in; there is no contains match:

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": "Open House" } },
      "paging": { "limit": 100 }
    },
    "fields": ["DETAILS"],
    "includeDrafts": false
  }'

filter and paging are siblings under query; paging nested inside filter fails 400. Matches come back in events[] with the id at events[].id, and pagingMetadata.total is the count.

Keep includeDrafts: false unless the user is asking about draft events. Setting it to true needs WIX_EVENTS.READ_DRAFT_EVENTS, and a caller without it gets 403 Requires WIX_EVENTS.READ_DRAFT_EVENTS permission rather than more results — so do not flip it as a precaution on an ordinary lookup, and do not probe for it and fall back. If the user does want drafts and the call returns that 403, say draft events are not readable from this connection instead of answering from published events alone.

Publish, cancel and delete

Publish and cancel take an empty body. Publishing is irreversible — a published event cannot return to DRAFT. Cancelling closes registration but keeps the event; deleting removes it.

Publish, cancel, clone and update all return { "event": { "id", "title", "slug", "status", ... } } — the same event object Create an Event shows in full. Delete returns { "eventId": "..." } and the bulk delete below returns {}.

To delete a set of events in one call, POST /events/v3/bulk/events/delete-by-filter:

{ "filter": { "filter": { "id": { "$in": ["<EVENT_ID>", "<EVENT_ID>"] } } } }

The request's one field, filter, takes a whole query-shaped object — the same object Query Events takes under query, with the conditions under its own filter key — not a bare condition map. That is why the key appears twice: filter.filter.<field>. A single level, { "filter": { "id": { "$in": [...] } } }, is not the documented shape. Resolve the ids with the query above first; one DELETE per event also works but costs a call each.

Draft events need the WIX_EVENTS.READ_DRAFT_EVENTS permission. Without it, publishing a draft fails 403 — as does querying it, fetching it by slug, or adding ticket definitions to it. If you hit that 403, the event was still created; the way forward is to create events already published rather than as drafts, which needs no publish step at all. See Create an Event.

Clone an event

POST /events/v3/events/{eventId}/clone with an empty body copies the registration form, notifications, translations and ticket configuration.

The clone does not keep the original's date. Its start date is reset to roughly 14 days from now and it comes back as a DRAFT. For a duplicate on a particular date, follow the clone with an update — and note the draft permission above.

Update an event

PATCH /events/v3/events/{event.id} with the fields to change nested under event:

curl -X PATCH 'https://www.wixapis.com/events/v3/events/<EVENT_ID>' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "event": {
      "dateAndTimeSettings": {
        "startDate": "2026-10-15T19:00:00.000Z",
        "endDate": "2026-10-15T22:00:00.000Z",
        "timeZoneId": "America/New_York"
      }
    }
  }'

The Events API takes no field mask and no revision on update — send only the fields you are changing. A revision, if you send one, is ignored rather than rejected.

When moving a date, send startDate and endDate together. dateAndTimeSettings is replaced wholesale rather than merged, so a patch carrying only startDate leaves the event with no end and fails 400 event cannot have negative duration — an error naming neither the missing field nor the replacement. timeZoneId is optional here, unlike on create; the stored one is kept.

Ticket definitions are the exception — PATCH /events/v3/ticket-definitions/{ticketDefinition.id} does require the current revision, which increments on every update.

Count events

POST /events/v3/events/query and read pagingMetadata.total:

{ "query": { "paging": { "limit": 100 } } }

Query Events returns only published events — drafts are excluded from both the results and the total, and including them needs the draft permission above. Create published, or publish first, if the count is meant to include the event you just made.

POST /events/v3/events/count-by-status exists, but an empty request body returns empty facets even when the site has events, so it is not the way to answer "how many events do I have".

Gotchas & troubleshooting

• An invalid enum value reports as a missing one — a value outside an enum returns <field> value is required rather than "invalid value". If a field you did send is reported as required, suspect the value, not its presence.
• includeDrafts stays false unless the request is about drafts — see Find an event. The WIX_EVENTS.READ_DRAFT_EVENTS note on the Query Events reference describes the permission; it does not mean the caller has it.
• Dates are always ISO-8601 strings, never {seconds, nanos}, and timeZoneId is required whenever dateAndTimeSettings is sent — see Create an Event.

Related APIs

• Wix Events V3: REST
• Event Guests: POST /events/v2/guests/query — who registered
• Create an Event — create body, dates, location, capacity, tickets, recurring