Activities API
Activities API
Tours, tickets and experiences with session-level availability.
On the roadmapSpecified and architected. Not yet built — timeline agreed per partner.
Activities behave unlike hotels: availability is per session and per pax type, and cut-off rules are tight. The model is specified separately rather than forced into the hotel shape.
Coverage
Planned through experience aggregators and direct DMC product. No coverage claim until the first contract.
Latency behaviour
Not published before implementation.
Authentication
OAuth 2.0 client credentials
Stated plainly:This API is not implemented. The endpoints below describe the intended contract so you can design against it; calling them today will not return live travel data.
Capabilities
- Session and timeslot availability
- Per-pax-type pricing (adult, child, infant, senior)
- Language and pickup options
- Ticket delivery with QR redemption
What it does not do
- — Not implemented.
- — Same-day booking cut-offs vary sharply by operator and will be surfaced per product.
Reference
Endpoints
The full surface, with real request and response shapes where the endpoint is implemented.
GET
/v1/activities/searchSearch experiences by destination and date.
GET
/v1/activities/{activityId}/availabilitySession-level availability for one product.
POST
/v1/activities/bookingsIdempotency-Key requiredBook an activity session.