Listings, experiences, and resource groups
The vocabulary you’ll see everywhere in this API:- A listing is how an experience is presented on a brand’s storefront - the title, photos, description, and price that guests browse and search. When you want “all the experiences a brand offers” for display, fetch Get all listings - that’s the customer-facing catalog.
- An experience is the bookable item itself: its sessions, capacity, and price tiers. Every booking targets an experience - you’ll use an
experienceIdwhen checking availability and creating bookings. There is also a Get experiences endpoint that returns these records directly - reach for it when you need scheduling configuration, not for building a storefront.
kind:
experience- a time-based activity (a tour, a class). The listing carries itsexperienceIddirectly.resource- the listing wraps a resource group collection (say, “Poolside Cabanas”) made up of resource groups (“Cabana Row A”), whose bookable units are each backed by their own experience. That’s why, forresourcelistings, theexperienceIdcomes from the session you select rather than from the listing itself.event- a one-off happening with its own sub-flow.

Where to start
Quickstart
Make your first authenticated API call in five minutes.
Build a booking integration
The end-to-end guide: list experiences, pick a session, take payment, and book.
API Reference
Every endpoint, testable in the browser with your own API keys.
Webhooks
Get notified when bookings are created, cancelled, or rescheduled.