Create Wix Event

Create an event on a Wix site — one-off or recurring, RSVP or ticketed — with the Wix Events V3 API. To publish, cancel, clone, count, add tickets or set up a recurring series, see Manage Wix Events.

First: pick the right “Events” API

Several unrelated Wix APIs are called “Events”. Routing to the wrong one is the most expensive mistake on this surface, because the wrong API answers plausibly for several calls before failing.

A recurring class or course that guests book is Bookings, not Wix Events. A recurring event series guests attend is Wix Events.

Prerequisite — the Wix Events app must be installed

Every /events/v3 call against a site without the app returns:

Install it with appDefId 140603ad-af8d-84a5-2c80-a0f60cb47351 — see Install Wix Apps. Confirm with the user first unless they already asked for the event to be created.

Create the event

title, location, dateAndTimeSettings and registration.initialType are all required. Drop "draft": true to create the event already published; a draft has status: "DRAFT" and is invisible on the site until published with POST /events/v3/events/{eventId}/publish (empty body), which moves it to UPCOMING.

Date and time

startDate and endDate are ISO-8601 strings, not {seconds, nanos} objects.

The spec types these fields as string / format: date-time but also carries a pointer to the google.protobuf.Timestamp message, whose fields are seconds and nanos. That message describes the internal representation and must not be sent — it fails with 400 {"message":"Expected a string."}. This applies to every date-time field across the Wix APIs, not only Events.

The timeZoneId error reads as though the field is unsupported. It is not — it means the field is missing. Add timeZoneId; do not remove it.

Date to be announced: send dateAndTimeSettings as { "dateAndTimeTbd": true, "dateAndTimeTbdMessage": "Date coming soon" } and nothing else. The message is mandatory — omitting it fails with 400 getScheduleTbdMessage must not be a blank.

Location

location.type is VENUE or ONLINE. There is no TBD type — a to-be-announced location is a VENUE with locationTbd: true.

For a real street address, add an address object:

subdivision is the ISO-3166-2 code (US-NY), and the API fills in formattedAddress and geocode on the response. A VENUE with no address comes back with locationTbd: true set by the API whether or not you sent it.

Registration type and capacity

initialType must be nested under registration; at the root of event it is treated as omitted and fails with the same error. Accepted values are RSVP, TICKETING, EXTERNAL and NONE.

The API’s error text for this field advertises [RSVP,TICKETS,RSVP_AND_TICKETS]. Those values do not work — TICKETS is rejected. Use TICKETING.

initialType is immutable: an RSVP event can never become a TICKETING event or vice versa (either can later become EXTERNAL or NONE via registration.type). Choose correctly at creation time — “people should register by RSVP, not tickets” means RSVP.

Guest limit. For an RSVP event, the cap is registration.rsvp.limit:

A limit placed directly on registration is silently ignored — the event is created with no cap and no error. Set waitlistEnabled: true alongside it to let guests join a waitlist once the limit is reached. For a ticketed event the cap is per ticket type, via initialLimit on the ticket definition — see Manage Wix Events.

Description — two different fields

A plain sentence belongs in shortDescription. Sending a string to description fails with 400 {"message":"Expected an object"} — it takes a Ricos { "nodes": [...] } tree, as built in Rich Content:

shortDescription is only returned when the request asks for "fields": ["DETAILS"], and description only with "fields": ["TEXTS"]. Both are stored regardless.

Gotchas & troubleshooting

• An invalid enum value reports as a missing one. Sending 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.
• Error text names internal accessors, not request fields. getTimeZoneId, getScheduleTbdMessage and endDate.isDefined each map to the plain field of the same name.
• title is required, min 1 and max 120 characters. There is no separate name field.

Related APIs

• Wix Events V3: REST (opens in a new tab)
• Manage Wix Events — tickets, publish, cancel, clone, recurring, count
• Install Wix Apps — the 428 pre-flight