Resell API Reference

POST

modify/reservations/{LocatorCode}

For {LocatorCode} send the reservation locator code of the reservation or ticket to modify.

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 Resell API is the last step in the process of an exchange of a held booking or ticketed itinerary for a new itinerary. It must be preceded by a Reprice request to add the new itinerary to the workbench.

If additional payment is required when exchanging a ticketed itinerary, you may need to send Add Form of Payment and Add Payment before sending the Resell request.

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

No message payload.

Response

The Resell response uses the same format as the Commit Workbench response.

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

  • As in the Reshop request, the amounts in the Price object are not the amounts for the new offer but rather the new offer compared with the existing offer on the booking or ticket. 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

No message body.

Example Response

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

The exchange process can be used to exchange or update the air itinerary on either a held booking or a ticketed itinerary. The example below is the response for updating the itinerary on a held booking. The response is similar for exchanging a ticketed booking except that the new ticket numbers are also returned.