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

NDC only; not supported for GDS. See the Exchange, Refund, and Void Guide for GDS options.

The Reshop API allows you to in search for a new itinerary when modifying a held booking 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 commit 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 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. 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:

  • 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