Packages API
Packages API
Component-based packages priced from live component cost.
On the roadmapSpecified and architected. Not yet built — timeline agreed per partner.
Packages compose the other product APIs. Each component keeps its own availability and cancellation policy, so a package cannot be sold when one component underneath it is gone.
Coverage
Composed from whatever product APIs your account has enabled.
Latency behaviour
Bounded by the slowest enabled component API.
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
- Component composition
- Package-level and component-level cancellation
- Fixed departures with allotment
- Minimum-pax enforcement
What it does not do
- — Not implemented.
- — Requires at least two live component APIs to be meaningful.
Reference
Endpoints
The full surface, with real request and response shapes where the endpoint is implemented.
POST
/v1/packages/quotePrice a package from live component costs.
POST
/v1/packages/bookingsIdempotency-Key requiredBook every component of a package atomically where suppliers permit.