Ancillary Shop API Reference

POST

ancillaryshop/catalogofferingsancillaries

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 Workflow Diagram

The Ancillary Shop request searches for available ancillaries. It can be sent after pricing, in the initial bookingClosed A confirmed reservation with the carrier. A held booking is a reservation that has not yet been ticketed. The terms booking and reservation are interchangeable. workbench, or for an existing reservation. The request uses the same endpoint but a different payload for each option, per below.

See the Ancillary and EMD Guide for workflow details and specific ancillaries supported.

For paid seats use the seat requests in the Seats Guide.

Request

Query Parameters

None.

Request Body

Be sure to see the Ancillary and EMD Guide for currently supported ancillaries in each flow.
Ancillary shop request after AirPrice (no workbench; GDS only)

This request supports ancillary shop for an entire offerClosed In the JSON Search APIs, an offer is a product available at a specific price under a set of terms and conditions. An offer includes the flight or connecting flights for one leg of the itinerary, plus a service level that includes the cabin class and any fare codes that may apply. At booking, the selected offer from the Search response - including the flight/s, service level, price, terms and conditions, and brand if applicable - is converted into a single Offer object that is subsequently returned for that booking.. It cannot be used to shop ancillaries on a segmentClosed A flight or flights under one flight number. One flight equals one segment. A segment could have multiple flights if the flight number remains the same, which happens if a flight makes a stop without changing planes. (a segment is a product in the JSON APIs).

Ancillary shop request in the initial booking workflow (pre-commit)

In the initial booking workflow, for either GDS or NDC, use the following payload.

For NDC only, you can send this same payload to shop ancillaries after AirPrice without a workbench. For GDS, see the section above for the payload to send after AirPrice.

Ancillary shop request for existing reservation (post-commit)

For an existing reservation, for either GDS or NDC, use the following payload.

Response

The Ancillary Shop response is the same following a request sent in either the initial booking flow or for an existing reservation.

Example Request

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.
Be sure to see the Ancillary and EMD Guide for currently supported ancillaries in each flow.
Ancillary shop request after AirPrice (no workbench; GDS only)
Ancillary shop request in the initial booking workflow (pre-commit)
Ancillary shop request for existing reservation (post-commit)

Example Response

The Ancillary Shop response is the same regardless of where in the workflow the shop request is sent.