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.

To use the Add Offer reference payload request, your initial Search request must send offersPerPage to invoke caching if that Search was journey-based (leg-based search results are always cached). Sending the transaction identifier from the AirPrice response is also supported.
Add offer to expired booking (GDS only)

You can use this or the 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. Start with a post-commit workbench. GDS only; not supported for NDC.

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