Reprice API Reference

POST

reprice/reservationworkbench/{workbenchID}/offers/buildfromcatalogofferings

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: Exchange, Refund, and Void Guide

When modifying a held 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. or exchanging a ticket for NDC, the Reprice API confirms pricing on a selected 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. from a preceding Reshop response and adds that offer to the workbench. It is part of the NDC modify/exchange workflow: Create a post-commit workbench, Reshop to shop for the new itineraryClosed The entire trip on a booking, including all flights on all legs. Also called a journey., Reprice as detailed here, and Resell to commitClosed API call that ends a workbench session, finalizing all changes and requests in that session. Depending on the workbench transactions, the commit workbench request may create a reservation, issue a ticket or EMD, exchange tickets, or modify a reservation. the changes.

When exchanging a ticket, if the new itinerary is greater than or equal to the previous itinerary, you may need to send Add Form of Payment and Add Payment after Reprice and before Resell.

For differences in how the JSON APIs support GDS and NDC content, see the support tables for seats, ancillaries, fare rules, and exchanges. Also see the NDC and GDS Functionality Comparison.
For carrierClosed An airline.-specific NDC differences, see NDC capabilities by airline through JSON API in the Travelport Knowledge Base. If you need login assistance, see Knowledge Base NDC Resources.

Request

Query Parameters

None.

Request Body

Response

The Reprice response uses the same format as the AirPrice Reference Payload API response, with the following differences:

  • OfferID is returned with @type value of OfferModify instead of Offer.

  • As in the Reshop response, the Price object does not return the price of the new offer but instead for the new offer compared with the existing offer. In Price/TotalPrice:

    • a positive number indicates the additional amount due for the new offer
    • a zero amount indicates an even exchange
    • a negative number indicates the offer costs less than the original itinerary and a partial refund is due

Example Request

Example Response

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

The response returns details for the modified itinerary, a total price difference, and a breakdown of the fare difference by PTCClosed Passenger Type Code, used to categorize travelers. The most common PTCs are adult (ADT), child (CNN), and infant (INF). You can request a maximum of 9 passengers in one Search request. for the selected offer.