Add Offer Reference Payload API Reference

POST

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

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: Booking Guide, Booking Session Workflow

Use the Add Offer reference payloadClosed In the JSON APIs, an API call that sends identifers referring to a previous response for the itinerary to be shopped, priced, added, etc. instead of full itinerary details. request to add an 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. to the reservation workbench as part of the 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. workflow. The reference payload request sends identifiers from the Search response instead of full itineraryClosed The entire trip on a booking, including all flights on all legs. Also called a journey. details.

NDCClosed New Distribution Capability, an XML standard for exchanging data that supports airlines in distributing their content directly to online travel agencies. See the NDC Guide. supports only the reference payload detailed here. For GDSClosed Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. In the JSON APIs, GDS content is distributed from Travelport., you can send either a reference payload or a full payload.

Start with a post-commit workbench. before sending Add Offer, per the booking workflow.

To use the Add Offer reference payload request following a search request, your initial Search request must send offersPerPage to invoke caching if that Search was journey-based (leg-basedClosed A Search that returns offers for only the first leg of the itinerary. Must be followed by a Next Leg Search request that selects an offer for the first leg and returns offers to combine with that leg. A multi-city itinerary requires another Next Leg Search for the third leg. See the Air Shopping Guide for details. See journey-based above. search results are always cached). If you add the offer after a price request, you can send the transaction identifier from the AirPrice response.
Add Multiple Offers (GDS)

In either the initial booking workflow, or for an existing reservation, you can send one or more Add Offer requests to add multiple GDS air offers in a single booking. While there is no specific limit on the number of offers that can be combined, a reservation cannot have more than 16 flight segments. Also supported in the Add Offer full payload request. GDS only; not supported for NDC. Your PCCClosed Pseudo city code. A travel provider's identification code for the JSON APIs, provisioned from Travelport. Used to determine access and other settings in the JSON APIs for your company. must be provisioned for multi-offers; contact your Travelport representative if necessary.

You can also repeat Add Offer to add a GDS air offer to an existing reservation that has hotel and/or car offers. See the Booking Guide for Air, Car, and Hotel for workflow details.

Add offer to expired booking

For GDS only, you can use this Add Offer reference payload request, or the Add Offer full payload request, to add an offer to an existing reservation, such as when the previously added offer has expired and can no longer be booked. (For NDC, use the NDC-specific Standalone Reprice API instead.)

Request

Query Parameters

None.

Request Body

Basic Add Offer Request - Reference Payload

PricingModifiersAir (optional pricing modifiers)

Optionally, you can store fares with one or more pricing modifiers. If a pricing modifierClosed A modifier that refines the API request based on fare and ticketing options and not the travel itself; sent in the PricingModifiersAir object. See the Air Shopping Guide for a list. is not added, the auto stored fare is added to the reservation. There is no change in the AirReservation response when pricing modifiers are requested. AirReservation applies modifiers from Add Offer and earlier steps as follows:

  • Modifiers sent in the Add Offer request (supported for both full and reference payload)

  • If no modifiers are sent in Add Offer, any pricing modifiers sent in AirPrice are applied

  • If no modifiers were sent in AirPrice, any pricing modifiers sent in Search are applied

GDS only; modifiers are not supported for NDC.

Response

The response returns the system-generated offer identifier. This identifier must be sent in several subsequent transactions, such as payment and ticketing.

Example Request

Example Response

The response returns the system-generated offer identifier. This identifier must be sent in several subsequent transactions, such as payment and ticketing.