Resell API Reference

POST

modify/reservations/{workbenchID}

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

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

The Resell API is the last step in modifying a held booking or exchanging a ticket for NDC. It commits the changes in the workbench and may issue tickets. It is part of the NDC modify/exchange workflow: Create a post-commit workbench, Reshop to shop for the new itinerary, Reprice to confirm pricing, and Resell as detailed here to commit the changes.

When exchanging a ticket, at Resell, if a partial refund is due, new tickets are issued and the refund is credited to the original form of payment. If a payment is due or the amount is an even exchange:

  • To issue the new tickets at commit, you must send Add Form of Payment and Add Payment before Resell to send payment and issue tickets. For an even exchange, send Add Payment with a zero amount.

  • To hold the booking, do not add any payment information in this workbench.

Some NDC carriers do not support held bookings for a ticket exchange and require that payment is sent and tickets issued at Resell. For carrier support details, see NDC capabilities by airline through JSON API in the Travelport Knowledge Base.

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. 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.

You can use the Reshop/Reprice/Resell workflow to modify the air itinerary on a held booking, or to exchange a ticketed itinerary. The example below is the response for updating the itinerary on a held booking. When exchanging a ticketed itinerary, the response is similar except that the new ticket numbers are also returned.