Modify 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.net/11/air/

Production https://api.travelport.net/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 Modify 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 Modify as detailed here to commit the changes.

When exchanging a ticket, in the case of either an even exchange or add collect (price of new itinerary is greater than existing itinerary), payment is required prior to ticketing. Some NDC carriers require tickets to be issued at commit while others support booking now and sending payment later. See the Support Table and Workflow Summary in the Exchanges Guide for details.

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

Request

As part of the request requirements, also see Authentication and Common Flights API Headers.

Header Parameters

Parameter

Description

Required/Optional

TVP-Feature-Set

Send with the value EnhancedAirChangeWorkflow to return the price difference between the selected offer and the amount originally paid for the ticket. The response includes a ModifyPrice object to itemize the price difference.

Optional

RepriceReasonCode

Send with the value UPDATE_PRICE along with ActionContextCode=UPDATE_PRICE to update the Order for which the TST has expired.

If not sent, the reservation is checked to determine if the modify is on hold for the originally ticketed booking.

Optional

ActionContextCode

Supported values: 

  • DEFERRED_PAYMENT_IN_EXCHANGE – Send to modify and hold a ticketing booking. When used, do not send a RepriceReasonCode.

    To check that the modify is on hold for the originally ticketed booking, following conditions are validated:

    • whether a valid DocumentTicket is present

    • OfferRef is not blank in ReceiptPayment

    • Check that the Total Price in OfferModify is greater than zero

  • UPDATE_PRICE – Send to update the price for a held booking, such as when the TST has expired. The order is updated without issuing a ticket.

  • SERVICING_PAY_AND_ISSUE – Send to update the price for a modify hold booking that was originally ticketed.

  • UPDATE_PAYMENT_METHOD_AND_PAY – Send to adjust the form of payment (for example, to add a credit card for OB fees).

Optional

Query Parameters

None.

Request Body

No message payload.

Response

The Modify response uses the same format as the Workbench Commit 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, download the developer toolkits and see Using Postman and Developer Toolkits.

You can use the Reshop/Reprice/Modify 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.