Admin Experience Contracts

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: 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: 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: 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: An experience with no scheduled distributions has no derived schedule until distributions are added.