@wix/agent-skills 1.33.0 → 1.34.0

package/skills/wix-manage/references/events/create-wix-event.md

@@ -1,40 +1,46 @@
 ---
 name: "Create an Event with the Wix Events API"
-description: "Creates an event with the Wix Events V3 API — the required request body, ISO-8601 date and time settings, venue/online/TBD location, RSVP vs ticketed registration, guest capacity, short vs rich-text descriptions, ticket tiers and pricing, and recurring series. Covers the exact field shapes and the API's misleading validation messages. Use when the user wants to create an event, set its date, location, description, guest limit or ticket prices, or set up a repeating event."
+description: "Creates an event with the Wix Events V3 API — one-off or recurring, RSVP, ticketed, registration-free or with external registration — including date and time, venue or online location, guest limit, description and ticket tiers. Covers the exact field shapes and the API's misleading validation messages. Use when the user wants to create or set up an event, an information-only event, or a repeating event — including a weekly workshop, class or meetup series held on set dates at a venue or online; a Bookings class or course is booked per session instead."
 ---
 
 # Create an Event with the Wix Events API
 
 ## Goal
-Create an event on a Wix site — one-off or recurring, RSVP or ticketed, with ticket tiers. To
-publish, cancel, clone, update or count events that already exist, see
-[Manage Wix Events](manage-wix-events.md).
+Create an event on a Wix site — one-off or recurring, RSVP, ticketed, registration-free or with
+external registration, with ticket tiers. To change registration, publish, cancel, clone, update
+or count events that already exist, see [Manage Wix Events](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-events).
 
 ## First: pick the right "Events" API
 
 Several unrelated Wix APIs are called "Events". Routing to the wrong one is the most expensive
 mistake here, because the wrong API answers plausibly for several calls before failing.
 
-| The user means | API | Base path |
+| The user means | API | Base URL |
 | --- | --- | --- |
-| A public event guests attend — gala, concert, workshop, meetup | **Wix Events V3** — this recipe | `/events/v3/events` |
-| A bookable session on a staff or service calendar | Calendar Events V3 | `/calendar/v3/events` |
-| An entry on the marketing plan calendar | Marketing Calendar Event V1 | `/promote/marketing-plan-service/v1/events` |
-| An automation trigger | Triggered Events | `/automations/v1/events/report` |
+| A public event guests attend — gala, concert, workshop, meetup | **Wix Events V3** — this recipe | `https://www.wixapis.com/events/v3/events` |
+| A bookable session on a staff or service calendar | Calendar Events V3 | `https://www.wixapis.com/calendar/v3/events` |
+| An entry on the marketing plan calendar | Marketing Calendar Event V1 | `https://www.wixapis.com/promote/marketing-plan-service/v1/events` |
+| An automation trigger | Triggered Events | `https://www.wixapis.com/automations/v1/events/report` |
 
-A recurring *class or course that guests book* is Bookings. A recurring *event series guests
-attend* is Wix Events.
+A recurring *class or course that guests book* — a session with a staff member or a service
+calendar — is Bookings. A recurring *event series guests attend* — a weekly workshop, meetup or
+class with a date and a venue — is Wix Events: use this recipe and don't look at Bookings unless
+the user asks to book a service or appointment.
 
 ## Prerequisite — the Wix Events app
 
-Every `/events/v3` call against a site without it returns `428 WIX_EVENTS_APP_NOT_INSTALLED`.
+Every `https://www.wixapis.com/events/v3` call against a site without it returns `428 WIX_EVENTS_APP_NOT_INSTALLED`.
 Install with appDefId `140603ad-af8d-84a5-2c80-a0f60cb47351` via
-`POST /apps-installer-service/v1/app-instance/install`, body
+`POST https://www.wixapis.com/apps-installer-service/v1/app-instance/install`, body
 `{"tenant":{"tenantType":"SITE","id":"<SITE_ID>"},"appInstance":{"appDefId":"<APP_DEF_ID>"}}` —
-`appDefId` nests under `appInstance`. See [Install Wix Apps](../app-installation/install-wix-apps.md).
+`appDefId` nests under `appInstance`. See [Install Wix Apps](https://dev.wix.com/docs/api-reference/business-management/app-installation/skills/install-wix-apps).
 
 ## Create the event
 
+Reference pages: [Create Event](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/create-event) and, for the read-backs below,
+[Query Events](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/query-events). The bodies in this recipe — including the recurring one
+— are complete for their cases; send them as shown rather than rebuilding them from the schema.
+
 ```bash
 curl -X POST 'https://www.wixapis.com/events/v3/events' \
   -H 'Content-Type: application/json' \
@@ -66,7 +72,7 @@ is created published (`status: "UPCOMING"`).
     "title": "Summer Gala",
     "slug": "summer-gala",
     "status": "UPCOMING",
-    "location": { "name": "Grand Hall", "type": "VENUE", "locationTbd": false },
+    "location": { "name": "Grand Hall", "type": "VENUE", "locationTbd": true },
     "dateAndTimeSettings": {
       "startDate": "2026-09-15T19:00:00Z", "endDate": "2026-09-15T22:00:00Z",
       "timeZoneId": "America/New_York", "recurrenceStatus": "ONE_TIME"
@@ -90,10 +96,8 @@ result from the top-level fields above and do not treat a missing `registration`
 
 ## Date and time
 
-**`startDate` and `endDate` are ISO-8601 strings, not `{seconds, nanos}` objects.** The spec types
-them as `string` / `format: date-time` but also points at `google.protobuf.Timestamp`, whose
-fields are `seconds` and `nanos`. That is the internal form and must not be sent. This applies to
-every date-time field across the Wix APIs.
+**`startDate` and `endDate` are ISO-8601 strings** — never `{seconds, nanos}` objects, even where
+the schema references `google.protobuf.Timestamp`.
 
 | Rule | If broken |
 | --- | --- |
@@ -106,6 +110,14 @@ every date-time field across the Wix APIs.
 
 Midnight is `00:00` of the next day. `2026-08-18T24:00:00.000Z` is not a valid ISO time.
 
+**Relative dates** ("next month", "the last Saturday", "this Friday") are counted from today in the
+event's time zone. Before creating, write down the local date and weekday you computed and check
+them against the request — for example, on 20 October "the last Saturday of next month" is
+Saturday 28 November. In JavaScript, `getMonth()` and the month argument of `Date.UTC()` are
+0-based, so `getMonth() + 1` passed back to `Date.UTC()` lands a month late. After the create,
+`dateAndTimeSettings.formatted.startDate` in the response shows the stored local date; if it
+isn't the date you meant, fix it before reporting.
+
 **Date to be announced:** send `dateAndTimeSettings` as
 `{ "dateAndTimeTbd": true, "dateAndTimeTbdMessage": "Date coming soon" }` and nothing else. The
 message is mandatory — omitting it fails `400 getScheduleTbdMessage must not be a blank`.
@@ -117,26 +129,67 @@ message is mandatory — omitting it fails `400 getScheduleTbdMessage must not b
 
 | Body | Result |
 | --- | --- |
-| `{ "name": "Grand Hall", "type": "VENUE" }` | Accepted |
+| `{ "name": "Grand Hall", "type": "VENUE" }` | Accepted, but stored with `locationTbd: true` — the event page shows the name in place of an address, as "to be announced" |
+| `{ "name": "Grand Hall", "type": "VENUE", "address": { ... } }` | Accepted — a real venue, `locationTbd: false` |
 | `{ "name": "To be announced", "locationTbd": true }` | Accepted — `type` defaults to `VENUE` |
 | `{ "locationTbd": true }` | `400 Location address must not be a blank` |
 | `{ "name": "TBA", "type": "TBD" }` | `400 type enum must be in [VENUE(0), ONLINE(1)]` |
 
-For a street address add `address`:
+**Online events:** use `{ "name": "Online", "type": "ONLINE" }`. For video-conference links, add
+`"onlineConferencing": { "enabled": true, "type": "MEETING" }` (`WEBINAR` for a webinar) to `event`.
+It needs a set date — not while the date is TBD — and a conferencing provider connected to the site.
+Without one, `enabled: true` is accepted and **not applied**: the response reads
+`onlineConferencing.enabled: false`, `type` `UNKNOWN_CONFERENCE_TYPE`. Check the response; if it is
+still `false`, create the event without conferencing and tell the user to connect a provider in the
+event's online settings — connecting one isn't possible through this API.
+
+**A venue name alone is a placeholder, not a venue.** When the user gives an address, send it as
+`address` so the event has a location and a map link. When they give only a name, create the event
+with the name, tell them the location shows as to be announced, and offer to add the street
+address — don't hold the event back to ask for it. The `address` shape:
 `{ "country": "US", "subdivision": "US-NY", "city": "New York", "postalCode": "10001",
 "streetAddress": { "number": "429", "name": "11th Ave" } }` — `subdivision` is the ISO-3166-2
-code; the API fills in `formattedAddress` and `geocode`.
+code; the API fills in `formattedAddress` and `geocode`. Read `location.address.formattedAddress`
+back and check the city: a short or ambiguous address can geocode to a different place, and the
+fix is a fuller address (street number, postal code, `subdivision`).
 
 ## Registration type and capacity
 
 `initialType` must be nested under `registration`; at the root of `event` it is treated as
-omitted. Accepted values are **`RSVP`**, **`TICKETING`**, `EXTERNAL` and `NONE`.
+omitted. It accepts exactly two values: **`RSVP`** and **`TICKETING`**.
+
+> Ignore the values the error text and event object list (`TICKETS`, `RSVP_AND_TICKETS`,
+> `EXTERNAL`, `NONE`) — each fails `400 ... initialType value is required`.
 
-> The API's error text advertises `[RSVP,TICKETS,RSVP_AND_TICKETS]`. Those do not work —
-> `TICKETS` is rejected. Use `TICKETING`.
+`initialType` can't be changed later, so pick it from the request: "RSVP", "sign up", "register"
+→ `RSVP`; "sell tickets", "paid entry", or several ticket types → `TICKETING`. "Free" alone does not
+mean RSVP — a ticketed event can sell `"0"` tickets.
 
-`initialType` is immutable: an `RSVP` event can never become `TICKETING` or vice versa. Choose
-correctly at creation — "register by RSVP, not tickets" means `RSVP`.
+To switch an **existing** event between RSVP and ticketed, don't create anything yet: explain that
+a new event would replace it, that its RSVPs or orders would not carry over, and ask first — see
+[Manage Wix Events](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-events).
+
+The other registration setups are flags on an RSVP or ticketed event, sent in the same
+`registration` object:
+
+| The user wants | `registration` |
+| --- | --- |
+| Guests RSVP on the site | `{ "initialType": "RSVP" }` |
+| Guests buy tickets on the site | `{ "initialType": "TICKETING" }`, then add tickets |
+| No registration — an information-only listing | `{ "initialType": "RSVP", "registrationDisabled": true }` |
+| Guests register on another website | `{ "initialType": "RSVP", "external": { "url": "https://..." } }` |
+| Only site members can register | add `"allowedGuestTypes": "MEMBER"` |
+
+Never send `registration.type` or `registration.status` — they are read-only. If the created
+event's `registration.type` is not what the user asked for (ask for it with
+`"fields": ["REGISTRATION"]`), apply the flag with an update — do not recreate the event:
+`PATCH https://www.wixapis.com/events/v3/events/<EVENT_ID>` with
+`{ "event": { "registration": { "registrationDisabled": true } }, "fields": ["REGISTRATION"] }`
+(or the `external` / `allowedGuestTypes` value from the table).
+
+**Guest answers (RSVP events).** An RSVP event created without `rsvp.responseType` accepts only
+"yes" — a guest or organizer adding a "no" fails `UNEXPECTED_RSVP_STATUS`. Send
+`"rsvp": { "responseType": "YES_AND_NO" }` when guests can decline.
 
 **Guest limit (RSVP events).** The cap is `registration.rsvp.limit`:
 `"registration": { "initialType": "RSVP", "rsvp": { "limit": 30 } }`. A `limit` placed directly
@@ -152,13 +205,15 @@ waitlist. Ticketed events cap per tier instead, via `initialLimit` below.
 
 A plain sentence belongs in `shortDescription`. A string sent to `description` fails
 `400 Expected an object` — it takes a Ricos `{ "nodes": [...] }` tree, as built in
-[Rich Content](../rich-content/author-ricos-rich-content.md). `shortDescription` is returned only
+[Rich Content](https://dev.wix.com/docs/api-reference/assets/rich-content/skills/author-ricos-rich-content). `shortDescription` is returned only
 with `"fields": ["DETAILS"]`, `description` only with `["TEXTS"]`; both are stored regardless.
 
 ## Ticket tiers
 
-For events created with `"initialType": "TICKETING"`. One call per tier — there is no
-bulk-create, and up to 100 tiers per event.
+For events created with `"initialType": "TICKETING"`: one call per tier, against the `event.id`
+the create call returned, one after another. After adding tickets, wait a few seconds before
+reading `registration.status`: it reads `CLOSED_AUTOMATICALLY` until the first ticket is on sale,
+then `OPEN_TICKETS`.
 
 ```bash
 curl -X POST 'https://www.wixapis.com/events/v3/ticket-definitions' \
@@ -174,48 +229,26 @@ curl -X POST 'https://www.wixapis.com/events/v3/ticket-definitions' \
   }'
 ```
 
-| To create | `pricingMethod` |
-| --- | --- |
-| Fixed price | `{ "fixedPrice": { "value": "25.00", "currency": "USD" } }` |
-| Free | `{ "fixedPrice": { "value": "0", "currency": "USD" } }` |
-| Donation, with a minimum | `{ "guestPrice": { "value": "5.00", "currency": "USD" } }` |
+- **`feeType` is required.** Free ticket (`fixedPrice` of `"0"`): `NO_FEE`. Paid ticket:
+  `FEE_ADDED_AT_CHECKOUT` (the guest pays the service fee), or `FEE_INCLUDED` when the user asked to
+  absorb it. On `400 INVALID_FEE_TYPE`, read the error's `description`: `feeRequired=false` means
+  the site collects no ticket fees — retry that ticket once with `NO_FEE`; `feeRequired=true` means
+  `NO_FEE` was sent on a paid ticket — retry once with `FEE_ADDED_AT_CHECKOUT`.
+- **`value` is a string** — `"value": 10` fails `400 Unexpected value for field value`. A free
+  ticket is a `fixedPrice` of `"0"`.
+- Quantity is **`initialLimit`**; omit it for unlimited.
 
-The response is the definition under `ticketDefinition`:
-
-```json
-{
-  "ticketDefinition": {
-    "id": "<TICKET_DEFINITION_ID>",
-    "eventId": "<EVENT_ID>",
-    "revision": "1",
-    "name": "General Admission",
-    "limited": true, "initialLimit": 100, "actualLimit": 100,
-    "pricingMethod": { "fixedPrice": { "value": "25.00", "currency": "USD" } },
-    "feeType": "FEE_ADDED_AT_CHECKOUT",
-    "saleStatus": "SALE_STARTED"
-  }
-}
-```
-
-Keep `revision` — `PATCH /events/v3/ticket-definitions/{id}` requires the current value, and it
-increments on every update.
-
-- **`feeType` is required.** A free ticket (`fixedPrice` of `"0"`) takes `NO_FEE`. A paid ticket
-  takes `FEE_ADDED_AT_CHECKOUT` (the guest pays the service fee) unless the user asked to absorb it,
-  then `FEE_INCLUDED`. `NO_FEE` on a paid ticket is accepted only on sites that do not collect ticket
-  fees. If a paid ticket fails with `400 INVALID_FEE_TYPE`, the site is one that does not collect
-  ticket fees: retry that ticket once with `NO_FEE`.
-- **`value` is a string.** `"value": 10` fails `400 Unexpected value for field value`.
-- **No writable `free` flag** — `pricingMethod.free` is read-only; a free ticket is a `fixedPrice`
-  of `"0"`.
-- Quantity is **`initialLimit`**, not `initialQuantity`; omit for unlimited. `limitPerCheckout` is
-  read-only. `name` max 30 chars.
+For anything beyond a plain fixed or free price — a donation ticket, several prices in one ticket
+(each option needs a generated `optionId`), a sale period or a hidden ticket — and for the full
+list of read-only fields, follow [Manage Event Tickets](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-event-tickets#add-a-ticket-type).
+Editing, repricing, reordering and deleting tickets are there too.
 
 ## Recurring events
 
 Wix Events has **no recurrence rule** — no `RRULE`, no "weekly" pattern. Calculate every
-occurrence yourself and list them all (up to 1000). **Each occurrence needs its own
-`timeZoneId`**; omitting it fails with a cryptic `ZoneOffset` error:
+occurrence yourself. The event's own `startDate`/`endDate` are the **first occurrence**, and
+`individualEventDates` lists only the **remaining** ones (up to 1000). **Each occurrence needs its
+own `timeZoneId`**; omitting it fails with a cryptic `ZoneOffset` error:
 
 ```json
 "dateAndTimeSettings": {
@@ -224,25 +257,55 @@ occurrence yourself and list them all (up to 1000). **Each occurrence needs its
   "timeZoneId": "America/New_York",
   "recurringEvents": {
     "individualEventDates": [
-      { "startDate": "2026-10-20T18:00:00.000Z", "endDate": "2026-10-20T19:00:00.000Z", "timeZoneId": "America/New_York" },
-      { "startDate": "2026-10-27T18:00:00.000Z", "endDate": "2026-10-27T19:00:00.000Z", "timeZoneId": "America/New_York" }
+      { "startDate": "2026-10-27T18:00:00.000Z", "endDate": "2026-10-27T19:00:00.000Z", "timeZoneId": "America/New_York" },
+      { "startDate": "2026-11-03T19:00:00.000Z", "endDate": "2026-11-03T20:00:00.000Z", "timeZoneId": "America/New_York" }
     ]
   }
 }
 ```
 
-Pick a sensible horizon for "weekly" and say how many occurrences you created. The event returns
-`recurrenceStatus: "RECURRING"`. Each occurrence is an independent event with its own ID; all
-share a generated `recurringEvents.categoryId`, which is how you query the series.
+That example creates **three** events: 20 Oct, 27 Oct and 3 Nov. **Do not repeat the first
+occurrence inside `individualEventDates`** — it then exists twice (four events for three dates, one of
+them marked `RECURRING_UPCOMING`). Leaving out the top-level `startDate`/`endDate` fails `400`.
+
+**Work out each occurrence's date in the event's own time zone, then convert to UTC.** "Every
+Thursday 7–9pm Pacific" is Thursday 19:00 in `America/Los_Angeles` — which is Friday 02:00 or 03:00
+UTC, depending on daylight saving. Deriving the weekday from the UTC date, or applying one fixed
+offset across a daylight-saving change, puts occurrences on the wrong day or hour. Check the local
+weekday of every generated `startDate` before sending.
+
+Don't query for an existing series before creating unless the user says one may exist — the
+read-back below is the one check this flow needs.
+
+Before creating, tell the user how many occurrences you will create and that each one is listed as
+its own event, with its own registration or tickets. Pick a sensible horizon for "weekly".
+
+**Then read the series back — always, before answering.** The create response carries only the
+first occurrence (`recurrenceStatus: "RECURRING"`), with the series'
+`dateAndTimeSettings.recurringEvents.categoryId`. Wait a few seconds, then:
+
+```json
+POST https://www.wixapis.com/events/v3/events/query
+{ "query": { "filter": { "dateAndTimeSettings.recurringEvents.categoryId": { "$eq": "<CATEGORY_ID>" } }, "paging": { "limit": 100 } } }
+```
+
+Report `pagingMetadata.total` — the number of events that exist — not the number you intended. If
+it is lower, wait a few seconds and query once more; occurrences appear shortly after the first.
+Don't count by title: other events can share it.
+Each occurrence is its own event with its own `id`: to change or cancel one later, find the
+occurrence by its `startDate` and act on that `id` only ([Manage Wix Events](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-events)).
 
 ## Gotchas & troubleshooting
 
 - **An invalid enum value reports as a missing one** — `<field> value is required` rather than
   "invalid value". If a field you *did* send is reported as required, suspect the value.
+- **`registration.type` / `registration.status` in a request do nothing** — they are read-only and
+  dropped without an error. Use `registrationDisabled` or `external.url`.
 - **Error text names internal accessors**: `getTimeZoneId`, `getScheduleTbdMessage`,
   `endDate.isDefined` each map to the plain field of the same name.
 
 ## Related APIs
 - **Wix Events V3**: [REST](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3)
 - **Ticket Definitions V3**: [REST](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/ticket-definitions-v3)
-- [Manage Wix Events](manage-wix-events.md) — publish, cancel, delete, clone, update, count
+- [Manage Wix Events](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-events) — registration settings, publish, cancel, delete, clone, update, count
+- [Manage Event Tickets](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-event-tickets) — edit, hide, reorder and price tickets

package/skills/wix-manage/references/events/events-dashboard-navigation.md

@@ -0,0 +1,81 @@
+---
+name: "Events Dashboard Navigation"
+description: "Builds direct links to Wix Events dashboard pages on manage.wix.com — the published and draft event lists, a new event, categories, staff, a recurring series' occurrences, and one event's pages: overview, edit, tickets, guests (RSVP or ticketed), orders, schedule, registration settings and form, and policies. Pairs each Events entity with its read API so you can fetch an entity and hand back a 'view it in your dashboard' link. Use when the user asks where something is in the Wix dashboard, wants a direct link to a dashboard page, or you need a dashboard URL to include with the result of an API operation."
+---
+
+# Events Dashboard Navigation
+
+Build direct links into the Wix Events pages of a site's dashboard. For the general URL contract
+(metaSiteId, fallbacks, redirects), see [Dashboard Navigation](../dashboard-navigation/dashboard-navigation.md).
+
+Every Events page is under the `events` namespace of the Wix Events app
+(`140603ad-af8d-84a5-2c80-a0f60cb47351`). Take routes from these tables — don't build one from an
+API path or a page title.
+
+## Main Pages
+
+| Page | URL after `/dashboard/{metaSiteId}/` | What it manages |
+|---|---|---|
+| Events list | `events` | Published events (upcoming, past, cancelled) |
+| Drafts | `events/drafts` | Unpublished events |
+| New event | `events/new` | Create an event; add `?eventType=RSVP` or `?eventType=TICKETS`, and `&recurrenceStatus=RECURRING` for a series. `TICKETS` is the dashboard's value — the API's `registration.initialType` is `TICKETING`; don't swap them |
+| Categories | `events/categories` | Site-wide event categories |
+| Staff | `events/staff` | Staff who check guests in |
+| Occurrences | `events/occurrences/{categoryId}` | All occurrences of a recurring series — `dateAndTimeSettings.recurringEvents.categoryId` |
+
+## One Event's Pages
+
+An event's pages are `events/event/{eventId}/{tab}`. For an event whose `status` is `DRAFT`, insert
+`draft/`: `events/event/draft/{eventId}/{tab}`. An unknown tab redirects to the overview.
+
+| Page | `{tab}` | Notes |
+|---|---|---|
+| Overview | `overview` | |
+| Edit details | `edit` | Title, date, location, description |
+| Tickets | `tickets` | Ticketed events only |
+| One ticket | `tickets/{ticketDefinitionId}` | Edit a ticket type |
+| New ticket | `tickets/new` | |
+| Guests — RSVP event | `rsvp-guests` | `registration.initialType` `RSVP` |
+| One RSVP | `rsvp-guests/{rsvpId}` | |
+| Guests — ticketed event | `ticketed-guests` | `registration.initialType` `TICKETING` |
+| One ticket holder | `ticketed-guests/{ticketNumber}` | e.g. `FM9X-EHKF-ZO1P` |
+| Orders | `orders` | Ticketed events only |
+| One order | `orders/{orderNumber}` | e.g. `FM9X-EHKF-ZO` |
+| Schedule (agenda) | `features/schedule` | |
+| Video conferencing | `features/video-conferencing` | |
+| Promotion | `promotions` | |
+| Settings | `settings` | |
+| Registration settings | `settings/registration-settings` | Open/close registration, guest limit, waitlist |
+| Registration form | `settings/registration-form` | Form questions |
+| Registration messages | `settings/registration-messages` | Confirmation texts; also `settings/registration-closed`, `settings/tickets-unavailable` |
+| Policies | `settings/policies` | One policy: `settings/policies/{policyId}` |
+| Ticket settings | `settings/tickets-settings` | Tickets per order, tax |
+| Guest emails | `settings/rsvp-confirmation-email`, `settings/order-confirmation-email`, `settings/reminder-email`, `settings/cancellation-email`, `settings/waitlist-email` | |
+
+Pick the guests tab from the event's type: `rsvp-guests` for RSVP events, `ticketed-guests` for
+ticketed ones. Read it with `"fields": ["REGISTRATION"]` when you don't already have it.
+
+## Pairing Entities with Their Read APIs
+
+Fetch the entity, then link its page.
+
+| Entity | Read API | Dashboard link |
+|---|---|---|
+| Event | `POST https://www.wixapis.com/events/v3/events/query` · `GET https://www.wixapis.com/events/v3/events/{eventId}` | `events/event/{eventId}/overview` (`draft/` inserted for a draft) |
+| Ticket definition | `POST https://www.wixapis.com/events/v3/ticket-definitions/query` | `events/event/{eventId}/tickets/{ticketDefinitionId}` |
+| RSVP | `POST https://www.wixapis.com/events/v2/rsvps/search` | `events/event/{eventId}/rsvp-guests/{rsvpId}` |
+| Order | `GET https://www.wixapis.com/events/v1/events/{eventId}/orders/{orderNumber}` · list: `GET https://www.wixapis.com/events/v1/orders?eventId={eventId}` | `events/event/{eventId}/orders/{orderNumber}` |
+| Ticket | `GET https://www.wixapis.com/events/v1/tickets/{ticketNumber}?eventId={eventId}` · list: `GET https://www.wixapis.com/events/v1/tickets?eventId={eventId}` | `events/event/{eventId}/ticketed-guests/{ticketNumber}` |
+| Policy | `POST https://www.wixapis.com/events/v2/policies/query` | `events/event/{eventId}/settings/policies/{policyId}` |
+| Category | `POST https://www.wixapis.com/events/v1/categories/query` | `events/categories` |
+| Recurring series | the event's `dateAndTimeSettings.recurringEvents.categoryId` | `events/occurrences/{categoryId}` |
+
+See [Manage Wix Events](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-events#find-an-event) for finding an event by title, and
+[Manage Event Guests](https://dev.wix.com/docs/api-reference/business-solutions/events/skills/manage-event-guests) for the guest reads.
+
+Example — after adding a guest to a ticketed event:
+
+```
+Added Sam Lee to Winter Gala.
+Guest list: https://manage.wix.com/dashboard/{metaSiteId}/events/event/{eventId}/ticketed-guests
+```