Experiences

Create, read, update and list experiences (tours, activities, events), and check their guest-facing availability. Anonymous and unauthenticated requests see only ACTIVE experiences that are publicly listed; authenticated callers additionally see their own experiences (any status) plus any experiences other organizers have explicitly shared with them. All multilingual fields follow the platform multilang convention — stored as {"en": "...", "de": "...", ...} objects; on read they resolve to a single string in the language selected by the language query parameter (falling back to English when the whole object is not consistently translated), unless showTranslations=true is passed, in which case the full per-language object is returned.

Availability is a two-step flow under /v2/experiences/{experienceId}/availability: call dates to paint a calendar of bookable days in a range, then slots for a selected day to get concrete bookable time slots per option, with per-variant availability and explicit unavailability reasons. Both accept an optional participants spec (typeId:count,typeId:count); when omitted the check is participant-agnostic (a party of one). You only see availability for experiences you can see — anything else is a 404.

Endpoints