Exchange Ticketing Guide / API Reference

Exchange Ticketing is the last step in the GDS exchange workflow. Per below, Exchange Ticketing uses the standard JSON AirTicketing APIs - Add Form of Payment, Add Payment, and Commit Workbench - with additional objects or parameters that are specific to exchanges. At workbench commit, you can choose whether to hold or ticket the modified itinerary.

It follows the Exchange Eligibility, Exchange Search , and AddModify Offer APIs, which confirm eligibility, search for a new itinerary, and choose a modified itinerary from the search results.

This combined guide and API reference provides the POST requests and examples for all requests in the workflow.

Related Content: GDS Exchanges Guide, Cancel, Exchange, and Refund Options

In this guide:

• Document Overrides (optional)
• Form of Payment (FOP)
  • Add Form of Payment
  • Multiple FOP (optional)
  • Forfeit Residual Amounts (optional)
  • Waive a Change Fee (optional)
• Add Payment
• Commit Workbench (Ticket Now or Hold Booking)

Document Overrides (optional)

As an optional step, you can send a document override request. You must send the request after adding the offer and before adding FOP or payment.

Exchange Ticketing supports the following document overrides to the exchange process; for payloads and details see Document Override Remarks for GDS Exchanges in the Remarks & Service Requests Guide:

• Commission
• Tour Code
• Endorsements
• Adding or modifying a ticket designator
• Overriding a change fee collection method

Form of Payment

The Form of Payment (FOP) step is required anytime there is an add collect (additional payment is due for the new itinerary). In this case you cannot use the FOP on the existing reservation. FOP is not required if the modified itinerary costs less than the original itinerary, or in the case of an even exchange.

Optionally, you can send an FOP request per below to use multiple forms of payment, forfeit residual amounts, or waive a change fee.

All steps in this section use the following endpoint with the payload detailed below for each. This is the same endpoint used to add FOP in initial ticketing. The response returns a confirmation identifier.

POST	payment/reservationworkbench/{workbenchID}/formofpayment 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/

Add Form of Payment

To add a form of payment if necessary, send a request to the FOP endpoint above with one of the payloads (cash, credit, agent invoice) in the Add Form Of Payment API Reference.

Add Multiple Forms of Payment (optional)

When an add collect is due (which may include a change fee), you can choose to use different or multiple forms of payment for a single traveler (for BSP only), or use different or multiple forms of payment for each traveler on the same itinerary.

To add multiple FOP:

1. Send a request to the FOP endpoint above with the cash or credit payload in the Add Form Of Payment API Reference.

2. Repeat as needed for additional FOP.

Note the following:

Change Fee to EMD:

• A change fee cannot be split across multiple FOPs.

• The first payment referenced will be used for the change fee and will not be used for the add collect.

• If a change fee to EMD is being collected during an exchange, then the first FOP referenced in the Payment service will be used for the change fee and any other FOPs referenced will be used for the add collect (if applicable).

Add Collect:

• A maximum of 3 FOPs can be used for one ticket – for BSP only.

• ARC does not allow multiple FOPs for an add collect.

When adding FOP:

• Do not add FOPs that already exist in the workbench, unless it’s a credit card for which only the expiration date has changed.

• Supported FOPs are cash, invoice, and credit card.

When adding payment below:

• Always include a traveler reference.

• When splitting payments across one ticket, ensure the amounts in Add Payment request add up to the total add collect and/or change fee.

• Always send the Amount object in the Add Payment step even if the value = zero (e.g., forfeit scenario).

Forfeit Residual Amounts (optional)

Optionally, agencies can forfeit residual amounts during the exchange/reissue of a ticket. An agency can forfeit the total residual amount, the base amount, the total taxes, or individual taxes with a tax code.

To send FOP to forfeit residual amount:

1. Send an FOP request to the FOP endpoint above with the Add FOP Forfeit Request payload below.

2. When you send the add payment request in the next step below, reference the FOP identifier for the Forfeit and send one of the following objects as appropriate to identify the amount to forfeit:

   1. Total residual amount: Amount object, example: "Amount": { "code": "USD", "value": 863.40 }

   2. Base amount: BaseAmount object, example: "BaseAmount": { "code": "USD", "value": 123.45 } }

   3. Total taxes: Taxes object with TotalTaxes, example: "Taxes": { "@type": "TaxesDetail", "TotalTaxes": 23.0 }

   4. Individual tax: Taxes object with individual Tax object, example: "Taxes": { "@type": "TaxesDetail", "Tax": [ { "currencyCode": "USD", "taxCode": "YQ", "value": 34 } ] }

Waive a Change Fee (optional)

You can waive a change fee with or without a waiver code. Waiver forms of payment are automatically applied to all travelers in a reservation.

WaiverCode/value is optional and if sent is added to the Endorsement Box in the reservation.

To send FOP to waive a change fee:

1. Send a request to the FOP endpoint above with the Add FOP Waiver request payload below.

2. When you send the add payment request in the next step, reference the FOP identifier for the waiver code.

Add Payment

Add Payment is required in the exchange workflow even if you will not ticket the reservation at commit:

• To issue the ticket at commit, send Add Payment and then commit without sending the payLaterInd query parameter, or with payLaterInd set to false.

• To hold the booking at commit without issuing tickets yet, send Add Payment and then commit with payLaterInd set to true.

Send the Add Payment request to the endpoint below, which is the same endpoint used to add payment in initial ticketing.

POST	paymentoffer/reservationworkbench/{workbenchID}/payments 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/

The response returns a confirmation identifier.

Commit Workbench (Ticket Now or Hold Booking)

Last, commit the workbench to commit the changes, setting the payLaterInd query parameter to either issue the new ticket/s now, or create a held booking for later fulfillment.

Send the request to the following endpoint. This is the same endpoint used to commit any workbench. The only difference is that the payLaterInd and DocumentValue parameters below are supported only for exchanges.

There is no message payload.

POST	book/reservation/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/

Query parameter	Description	Require
payLaterInd	Required in Exchange Ticketing 23.11.13 and later. Sets whether to issue the new ticket/s now, or create a held booking for later fulfillment. Supported values: true: Holds changes for later fulfillment and ticketing. false: Issues ticket and any other documents such as EMDs on commit.	Required
DocumentValue	If sent, send with a value of REFUND, which refunds an EMD that has a refundable balance to the original FOP and is the only supported value. Refunds are indicated in the Exchange Search response by a negative amount in ModifyPrice/TotalPrice, and a value of either EMD or MCO in TermsAndConditions/FulfillmentMethod/RefundMethod. Alternately, you can refund or forfeit any EMD value using the EMD Void request. If the new itinerary is ticketed at the time of reservation (pay now flow), and there is a residual balance to an MCO (miscellaneous change order), the MCO is issued along with the ticket at workbench commit. If the new itinerary is booked but not ticketed (pay later flow), any MCO is created but not issued yet. This allows customers to display, modify, and issue their own MCO outside of the JSON APIs if desired. If the reservation is subsequently ticketed using Exchange Ticketing, the MCO is issued as usual at commit.	Optional If not sent any value remains on the EMD.

The Commit response returns all details of the new reservation, including price modifications in the ModifyPrice object. Any refund issued is indicated in FulfillmentMethod/RefundMethod/value. The reissued ticket numbers are returned in an instance of Receipt of type ReceiptPayment as shown below. The response does not include any itinerary data from the previous booking.

The commit response returns the following Document @type values:

• The previous (exchanged) ticket details are returned with Document @type DocumentTicketExchange.

• The newly issued ticket details are returned with Document @type DocumentTicket.

• If an EMD is issued during the exchange, such as for a change fee or a residual balance, the commit response returns Document @type DocumentEMD with the EMD number and the amount.