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: NDC Modify, Cancel, and Exchange Guide

NDC only; not supported for GDS.

The Reshop API allows you to search for a new itinerary or make other supported air itinerary changes to either a held booking or a ticketed itinerary. First establish a workbench session, send the Reshop request detailed here, then send a Reprice request to continue the exchange.

See the NDC Modify, Cancel, and Exchange Guide for details on supported options and workflows.
For differences in support between GDS and NDC in the JSON APIs, see the support tables for seats, ancillaries, fare rules, and exchanges. Also see the NDC Carrier-Specific Notes and the NDC and GDS Functionality Comparison Chart.
For carrier-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 offer identifier, and the identifiers for all products (a product is one leg 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. The price difference between the original itinerary and that 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

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