Reshop API Reference

POST

change/catalogofferingsairchange

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

The Reshop API allows you to in search for a new itineraryClosed The entire trip on a booking, including all flights on all legs. Also called a journey. 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. It is part of the NDC modify/exchange workflow: Create a post-commit workbench, Reshop as detailed here, Reprice to confirm pricing, 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.

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

The message payload requires several identifiers: the workbench identifier returned when the workbench is created, the 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. identifier, and the identifiers for all products (a product is one legClosed The flight or connecting flights between one origin and destination pair. For example, on a round-trip flight, LAX > MSP could be the first leg (aka outbound leg) and MSP > DEN > LAX could be the second leg (aka inbound leg). The JSON APIs use the term product (see below) to represent one leg of the itinerary. of the itinerary). If you want to change only specific segments, you must reshop the entire itinerary, not just the products to modify.

Response

The Reshop response uses the same general structure as the Search API response. The table below notes differences in the Reshop response and references the Search API Reference for objects that are the same.

There is no maximum on the number of offers returned, which depends on availability for the search criteria.

Each offer is returned in an instance of CatalogOffering. For each offer, CatalogOffering/Price/TotalPrice does not return the price of the new offer but instead for the new offer compared with the existing offer:

Example Request

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

Example Response

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

The response is structured similarly to the Search response. The price difference between the original itinerary and each offer is returned in CatalogOffering/Price/TotalPrice:

  • a positive number indicates the additional amount due for that 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