Use /orders/details/accommodations, /orders/details/cars or /orders/details/flights endpoints to retrieve booking details across supported travel services. You can use this information to power post-booking experiences, support travellers, reconcile commissions, and integrate loyalty programmes.
After an order is created, you can retrieve detailed information about the reservation using the /orders/details/* endpoints.
These endpoints provide a consistent way to access post-booking data for:
- Accommodation reservations.
- Car rental reservations.
- Flight reservations.
Each travel service has its own endpoint and response schema, while following common patterns for request parameters and post-booking workflows.
Use the following endpoints to retrieve post-booking information:
Endpoint | Action | Use it to... |
|---|---|---|
| /orders/details/accommodations | Retrieves accommodation-specific order details. | ✓ Display reservation details, check status, retrieve cancellation policies, and support traveller enquiries. |
| /orders/details/cars /orders/details/cars/live (Beta) | Returns car rental reservations details. | ✓ Build "Manage My Booking" experiences, display pick-up and drop-off information, retrieve driver details, and check booking status. |
| /orders/details/flights | Returns flight reservation details. | ✓ Display itinerary, check booking status, support traveller queries. |
Post-booking endpoints are designed to support a wide range of operational and traveller-facing use cases.
Use order details to:
- Display reservation information to travellers.
- Build “Manage My Booking” pages.
- Show booking status and itinerary details.
- Generate confirmation pages or vouchers where applicable (for cars)
Use order details to:
- Support cancellation workflows and status checks.
- Retrieve information before modifying an order.
- Assist travellers through customer support channels.
The following fields are commonly used across post-booking endpoints:
Concept | |
|---|---|
status | Indicates the current state of the booking (for example: booked, cancelled, completed). |
affiliate | Identifies the partner responsible for the booking. Used for commission tracking and attribution. |
booker | Contains traveller or booker information where available and permitted by the applicable PII agreement. |
price | Provides booking-level pricing information for display, reconciliation, and reporting. |
commission | Contains commission-related information where supported by the travel service. |
Most /orders/details/* endpoints support:
- Retrieval by
ordersorreservationsidentifiers. - Optional enrichment via the
extrasparameter. - Optional currency conversion via
currency - Localised content using
language(where supported)
Refer to the documentation for each travel service to see which optional parameters are available.
- Results are typically returned in descending order of creation date.
- You can retrieve orders or reservations 1 year after creation.
- Use the
extrasparameter to control which additional fields are returned. - Some fields (such as driver or traveller details) are only returned when the appropriate PII permissions are enabled.
- Cancellation policies and pricing breakdowns may vary per travel service and product type.
Explore the service-specific guides for complete request parameters, response schemas, examples, and implementation guidance:
Accommodation order details
Car rental order details
Flight order details