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-registration-form.md

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

Event Registration Form

Goal

Change what guests are asked when they RSVP or check out for one event, and the messages they see. Each event has its own form, addressed by the event id — not by a form id from a dashboard URL. Find the event first (below). Whether registration is open, the guest limit and the waitlist are event settings, changed under event.registration with PATCH https://www.wixapis.com/events/v3/events/<EVENT_ID> — not on the form (Registration settings). This is not the Wix Forms app's forms — those are in Forms.

Every change here applies to the live form right away; there is no separate publish step.

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: Query Events (find the event), Get Form, Add Control, Update Control, Delete Control, Update Messages. The control bodies in the table below are complete — send them as shown rather than rebuilding them from the schema.

Read the form

curl -X GET 'https://www.wixapis.com/events/v1/events/<EVENT_ID>/form' \
  -H 'Authorization: <AUTH>'

form.controls[] is the list of questions, sorted by orderIndex. Each control has an id (for example phone-1a4acde6c958ff66), a type (INPUT, TEXTAREA, DROPDOWN, RADIO, CHECKBOX, NAME, GUEST_CONTROL, ADDRESS_SHORT, ADDRESS_FULL, DATE), inputs[] with each input's name, label, mandatory and options, and system: true on the built-in name and email controls, which can't be removed — only relabeled. form.messages holds the messages below. The same form comes back from GET https://www.wixapis.com/events/v3/events/<EVENT_ID>?fields=FORM under event.form.

Read the form before every change: to avoid adding a question that already exists, and to get the control id an update or delete needs.

Add a question

POST https://www.wixapis.com/events/v1/events/<EVENT_ID>/form/control (singular control) with exactly one key naming the kind of question:

curl -X POST 'https://www.wixapis.com/events/v1/events/<EVENT_ID>/form/control' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "dropdown": {
      "label": "Choose main course",
      "options": ["Vegetarian", "Fish", "Steak"],
      "mandatory": true
    }
  }'
Question Body
Short text { "text": { "label": "Company", "mandatory": false, "maxLength": 200 } }
Long text / comments { "text": { "label": "Dietary restrictions", "mandatory": true, "maxLength": 1000, "multiLine": true } }
Dropdown (2–200 options) { "dropdown": { "label": "...", "options": ["A", "B"], "mandatory": true } }
Checkboxes (1–200 options) { "checkbox": { "label": "...", "options": ["I agree to the terms"], "mandatory": true } }
Radio buttons (2–200 options) { "radioButton": { "label": "...", "options": ["Yes", "No"] } } — no mandatory field
Date { "date": { "label": "Date of birth", "mandatory": false } }
Phone { "phone": { "label": "Mobile", "mandatory": true } }
Address { "address": { "labels": { "addressLine": "Address" }, "full": false, "mandatory": false } } — full: true for separate street, city, country and postal code fields
Additional guests { "additionalGuests": { "labels": { "single": "+1", "multiple": "Guests" }, "namesMandatory": true, "maxGuests": 5 } }
  • Additional guests lets one registrant bring others. maxGuests is 1–10: 1 is a single plus-one, 5 is "up to 5 guests". namesMandatory asks for each guest's name. If the form already has a GUEST_CONTROL, update it instead of adding a second one.
  • Labels: up to 200 characters (100 for date, phone and address labels); text.maxLength 0–1000.
  • A new question goes to the end of the form; orderIndex can't be set on add — move it with an update.
  • The response is { "id", "form" } — confirm the new control is in form.controls. Control ids are short names, not GUIDs — a long-text question comes back as custom, the additional-guests field as additionalGuests — so always take the id from the returned form. Guests must answer a mandatory question straight away: RSVPs that leave it empty fail 400 INVALID_FORM_RESPONSE (input custom [''] must not be empty).
  • 400 INVALID_EVENT_CONFIGURATION — the control's configuration is not valid for this event; check the limits above. On ticketed events the number of attendees comes from the ticket quantity, so "bring guests" there means more tickets, not an additional-guests question.

Change, reorder or remove a question

Update: PUT https://www.wixapis.com/events/v1/events/<EVENT_ID>/form/controls/<CONTROL_ID> (plural controls) with the same one-of key as on add — carrying the control's full new configuration, since this replaces it — and optionally orderIndex:

{ "orderIndex": 3, "phone": { "label": "Work phone", "mandatory": false } }
  • Make a question required or optional: resend it with mandatory changed.
  • Add a dropdown option: resend the whole options array with the new value.
  • Reorder: send the control's current configuration with a new orderIndex; controls sort in ascending orderIndex. Read the current values from the form and pick the index between the neighbours you want.
  • Relabel the built-in fields: { "name": { "labels": { "firstName": "Given name", "lastName": "Family name" } } } or { "email": { "label": "Work email" } } on their control ids.

Delete: confirm with the user first, then DELETE https://www.wixapis.com/events/v1/events/<EVENT_ID>/form/controls/<CONTROL_ID>. The returned form can still list the control with "deleted": true — ignore controls flagged that way, and confirm with a fresh read of the form.

404 CONTROL_NOT_FOUND — the id is not on this event's form; read the form again.

Change the messages guests see

PATCH https://www.wixapis.com/events/v1/events/<EVENT_ID>/form/messages with the messages under messages and one path per message you change under fields.paths. Always send fields.paths — without it the call replaces all messages, and every message you didn't send (such as the RSVP button label) is cleared.

curl -X PATCH 'https://www.wixapis.com/events/v1/events/<EVENT_ID>/form/messages' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "messages": {
      "rsvp": { "positiveMessages": { "confirmation": { "title": "See you there!" } } },
      "registrationClosed": { "message": "Registration is full — check our news page for updates." }
    },
    "fields": {
      "paths": [
        "messages.rsvp.positiveMessages.confirmation.title",
        "messages.registrationClosed.message"
      ]
    }
  }'
Message Path under messages
RSVP answer labels and button rsvp.rsvpYesOption, rsvp.rsvpNoOption, rsvp.submitActionLabel
After an RSVP "yes" rsvp.positiveMessages.confirmation.{title, message, addToCalendarActionLabel, shareActionLabel}
After joining the waitlist rsvp.waitlistMessages.confirmation.{title, message, addToCalendarActionLabel, shareActionLabel}
After an RSVP "no" rsvp.negativeMessages.confirmation.{title, shareActionLabel}
Ticket checkout checkout.{title, submitActionLabel}, checkout.confirmation.{title, message, downloadTicketsLabel, addToCalendarLabel, shareEventLabel}
Registration closed registrationClosed.{message, exploreEventsActionLabel}
Tickets unavailable ticketsUnavailable.{message, exploreEventsActionLabel}

These are the texts on the event's pages; the emails guests receive can't be edited through this API.

Not supported

  • Conditional questions (show a question only after another answer) — the event form has no conditional logic; say so.
  • Validating an answer against a list (a members-only code) — answers are not checked.
  • One form per ticket holder on ticketed events is an event setting, not a form control: PATCH https://www.wixapis.com/events/v3/events/<EVENT_ID> with { "event": { "registration": { "tickets": { "guestsAssignedSeparately": true } } } }.

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.