Ancillary Book API Reference

POST

book/airoffer/reservationworkbench/{workbenchID}/offers/buildancillaryoffersfromcatalogofferings

For {workbenchID} send the workbench identifier returned in ReservationResponse/Identifer/value in the workbench create response.

Base path:

Pre-production https://api.pp.travelport.com/11/air/

Production https://api.travelport.com/11/air/

Related Content: Ancillary and EMD Guide, Ancillary Shop API Reference, Ancillary Workflow Diagram

The Ancillary Book request adds a selected ancillary to a workbench for an existing reservation. You must first send an Ancillary Shop request and, for NDC only, an Ancillary Price request. Ancillaries can include baggage, pets, meals, lounge access, wifi, etc.

See the Ancillary and EMD Guide for a list of supported ancillaries. To book seats, use the Seat Book request.

To add ancillaries or seats to a multi-offer booking, send the Seat Map or Ancillary Shop request, then send one book request for each offer. You can send the book requests in any order: first and second offer, or second and first offer. Supported for an existing booking for ancillaries and seats; supported in the initial booking workflow only for free seats. GDS only; multi-offers not supported for NDC.
You may also need to add payment for the ancillary in the same workbench session. See payment and EMD details in the Ancillary and EMD Guide.

Request

Query Parameters

None.

Request Body

Response

The Ancillary Book response returns details of the ancillary added to the workbench.

Example Request

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

The GDS ancillary book request sends identifiers from the Ancillary Shop request. Ancillary Price is not supported for GDS.

The NDC ancillary book request sends identifiers from the Ancillary Price request, which is a mandatory step for NDC ancillaries.

Example Response