Post-booking management integration

Let travellers access and manage their orders from your platform after confirmation.

A Post-booking management integration extends the traveller journey beyond booking confirmation.

Use the Orders API collection to build post-booking experiences that can:

• Retrieve current order details and status.
• Display existing orders in your application.
• Modify supported order information where available.
• Cancel eligible travel services within an order.
• Provide additional post-booking information and services where supported.

Choose this integration if you want to:

• Display existing orders within your application.
• Build a Manage my bookings experience where travellers can access their order details and status.
• Display car rental confirmation and voucher information.
• Let travellers modify supported order information.
• Let travellers cancel eligible travel services.
• Provide additional post-booking information or services where supported.

Before implementing this integration:

• Complete the Demand API prerequisites.
• Make sure you have the identifiers required to retrieve or manage the relevant order.
• If your application creates orders using the Demand API, store the required order information returned during order creation.

After an order has been created, your application uses the Orders API collection to retrieve and manage it throughout the supported post-booking lifecycle.

Unlike a booking flow, post-booking operations do not form a single sequential workflow. Your application can implement only the capabilities required by your traveller experience.

Depending on the travel service and order, your application can retrieve order details, modify supported information, cancel eligible travel services or access additional post-booking information.

Implement the capabilities required by your traveller experience.

Use the relevant order details endpoint to retrieve current information for an order.

The information available depends on the travel service and API version. Depending on the order, the response can include:

• Order and reservation identifiers.
• Order or reservation status.
• Traveller details.
• Travel dates and itinerary information.
• Payment information.
• Cancellation policies.
• Travel-service-specific information.

For car rentals, use the /orders/details/cars/live endpoint (Beta) to retrieve supported real-time post-booking information, such as purchased insurance documents.

Use the /orders/modify endpoint to change supported information for an eligible order.

The information that can be modified depends on the travel service, order and applicable conditions.

Before offering a modification to the traveller:

• Check that the modification is supported for the order.
• Present any relevant conditions or updated information.
• Submit the modification using the appropriate Orders endpoint.
• Handle unsuccessful modification requests without assuming the order has changed.

After a successful modification, retrieve or use the latest order information returned by the API to update the traveller-facing experience.

Use the /orders/cancel endpoint to cancel an eligible travel service within an existing order.

Before submitting a cancellation, retrieve the latest order details to verify the current status and review the applicable cancellation conditions.

A typical cancellation flow is:

1. Retrieve the latest order details.
2. Verify that the travel service is eligible for cancellation.
3. Review the applicable cancellation policy and any fees.
4. Present the cancellation conditions to the traveller.
5. Ask the traveller to confirm the cancellation.
6. Submit the cancellation request.
7. Confirm the cancellation result and display the updated status.

Depending on the travel service, cancellation can involve fees, refunds or other conditions. Use the cancellation information returned by the API as the source of truth.

Order information can change throughout the post-booking lifecycle.

Keep the information displayed by your application synchronised with the latest state available through the API.

In particular:

• Retrieve current order information before presenting actions that depend on order status or eligibility.
• Update the traveller-facing order state after a successful modification.
• Update the traveller-facing order or reservation state after a successful cancellation.
• Do not assume that previously retrieved order information is still current when performing a new post-booking operation.

Store the identifiers required to retrieve the order again, but use current API information for data that can change over time.

Some travel services provide additional information that can enhance the post-booking experience.

Depending on the travel service, order and API version, this can include:

• Insurance documents.
• Legal or policy information.
• Itinerary information.
• Booking confirmation details.
• Other travel-service-specific post-booking information.

For example, supported car rental orders can provide purchased insurance documents through the live order details endpoint.

Modification and cancellation requests can fail because the order state, eligibility or other conditions have changed since the information was last retrieved.

Your application should:

• Handle unsuccessful requests without assuming the order has changed.
• Display an actionable error message to the traveller.
• Retrieve current order information when necessary to determine the latest state.
• Avoid showing a modification or cancellation as successful until the API confirms the operation.

Before considering your Post-booking management integration complete, verify that:

Post-booking management works with existing orders. It does not provide the capabilities required to discover travel products or create new orders.

• To let travellers search for travel products and create orders on your platform, use the Search, look and book integration.
• Operational reporting and financial reconciliation are separate capabilities. See the Reporting and reconciliation integration for guidance.

After implementing Post-booking management:

1. Test order retrieval for the travel services supported by your integration.
2. Test successful and unsuccessful modification flows where modification is supported.
3. Test cancellation flows, including different eligibility states and cancellation conditions.
4. Verify that your application updates order information after post-booking operations.
5. Test any additional post-booking information or services used by your application.
6. Review the Orders FAQs for common questions about order retrieval, modifications, cancellations and order status.
7. Review error handling for the Orders APIs used by your integration.