Skip to main content
Use the generated endpoint reference for the complete schema. This page highlights the fields most often used when creating or updating experiences through the Admin API.

Create Experience

POST /experiences creates the experience container. The request body accepts:
FieldRequiredDescription
nameYesCustomer-facing experience name.
timeZoneNoTime zone used when child distributions do not supply their own.
productsNoProduct mappings for the experience.
accessCodeNoExperience-level access code. Use sequence access codes for path-specific gates.
themeNoBrand theme overrides for this experience.
i18nNoExperience-level text overrides.
sequenceNoNested access path and distribution creation.
Experience openAt and closeAt appear in responses, but they are derived from the attached distribution windows. Set timing on the distribution records rather than sending top-level experience timing.

Nested Sequence Creation

The optional sequence object lets an integration create the first access path and its distributions in the same request:
FieldRequiredDescription
nameYesAccess path name.
audienceIdNoAudience required for this path.
accessCodeNoAccess code required for this path.
priorityNoHigher numeric priority is evaluated first.
productSelectionModeNoProduct selection mode for the products routed through this path.
sequenceProductsNoProduct allocation weights for system-assigned selection. Each item includes productId and weight.
queues, draws, auctions, appointments, timedReleasesNoDistributions to create under the sequence.
Nested distributions use the same field names as their standalone Admin API endpoints, without sequenceId because the API creates that relationship from the nested sequence. Waitlists are managed through the waitlist and sequence surfaces rather than the nested POST /experiences distribution array.

Update Experience

PUT /experiences/{id} updates top-level experience metadata only:
FieldDescription
nameExperience name.
timeZoneExperience time zone.
themeBrand theme overrides.
i18nText overrides.
Use product, sequence, and distribution endpoints to update product mappings, access paths, access codes, distribution timing, capacity, winner selection, auction pricing, waitlists, or timed-release settings.

Timing

Experience timing is calculated from child distributions:
DistributionTiming fields used for the experience envelope
QueueopenAt, closeAt
DrawopenAt, closeAt, drawAt
AuctionopenAt, closeAt, settleAt
AppointmentopenAt, closeAt
Timed releaseopenAt, closeAt
An experience with no scheduled distributions has no derived schedule until distributions are added.