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 payload request to add an offer to the reservation workbench as part of the booking workflow. The reference payload request sends identifiers from the Search response instead of full itinerary details.

NDC supports only the reference payload detailed here. For GDS, 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-based 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 reference payload 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.

You can also repeat Add Offer to add a GDS air offer to an existing reservation that has hotel and/or car offers.

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 modifier 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.

If the requested modifier does not have any fares associated with it, the workbench commit fails and returns the error message No Fare Found. Pricing happens at commit, not at Add Offer.

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.