Add Offer Full Payload API Reference

POST

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

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

Full payload is not supported for NDC; use the reference payload instead. For GDS, you can send either a reference payload or a full payload.
Add Multiple Offers (GDS)
You can repeat the Add Offer step as needed to combine multiple offers into one reservation, either in the initial booking workflow or for an existing reservation. While there is no specific limit on the number of offers that can be combined, a reservation cannot have more than 16 flight segments. Supported only in the Add Offer full payload request, not the reference payload request. GDS only; not supported for NDC.
Add offer to expired booking (GDS only)

You can use this or the reference 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.

Pricing modifiers and brand information

The full payload request supports optional pricing modifiers and/or brand information. You must send these modifiers during the initial booking workbench session - you cannot add them later.

  • Pricing modifiers: If no pricing modifier is sent, the auto stored fare is added to the reservation. If a requested modifier does not have any fares associated with it, the Add Offer step returns a successful response but the Commit step will fail and return the error message No Fare Found.

  • Brand information: You can store fares with brand information at either or both the offer or segment level.

    • To store brand information at the offer level, send PricingModifiersAir/Brand/tier with any valid brand tier value.
    • To store brand information at the segment level, send the brand tier with the flight segment in ProductCriteriaAir/SpecificFlightCriteria/brandtier. You can send brandTier for any or all segments.
    • There is no change in the response when brand information is requested. Brand details are returned after booking in the Reservation Retrieve.

Request

Query Parameters

None.

Request Body

Basic Add Offer Request - Full 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

The following example full payload request adds an offer for a one-way itinerary.

Example Response

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