Skip to content
Trip composition connectivity

Packages API for travel teams

Component-based packages priced from live component cost.

Product overview

A clear contract for the next part of the journey.

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.

Composed from whatever product APIs your account has enabled.

ProductPackages
AvailabilityPlanned integration
AuthenticationOAuth 2.0 client credentials
ContractHTTPS · JSON
What to review

Shape the integration around your operation.

Planned scope, not implemented. Development requirements and timing are agreed per project.
Capabilities
  • Component composition
  • Package-level and component-level cancellation
  • Fixed departures with allotment
  • Minimum-pax enforcement
Integration notes
  • Bounded by the slowest enabled component API.
  • Not implemented.
  • Requires at least two live component APIs to be meaningful.
Endpoint reference

The packages surface at a glance.

POST/v1/packages/quote

Price a package from live component costs.

POST/v1/packages/bookings

Book every component of a package atomically where suppliers permit.

Need the complete contract?Review request fields, response schemas, authentication and launch requirements with the integration team.Discuss integration access