Ticket as FOP API Reference

Get

book/airoffer/reservationworkbench/{LocatorCode}/offers/buildfromoffer For {LocatorCode} send the locator code of the reservation to retrieve (returned in the workbench commit API call that ends a workbench session, finalizing all changes and requests in that session. Depending on the workbench transactions, the commit workbench request may create a reservation, issue a ticket or EMD, exchange tickets, or modify a reservation. in Confirmation/Locator/value). Send the locator code of the held booking A confirmed reservation with the carrier. A held booking is a reservation that has not yet been ticketed. The terms booking and reservation are interchangeable. you want to ticket, not the reservation locator Unique six-character alphanumeric code returned for a successful booking, e.g. JS7GH4. For NDC the airline returns an additional locator code, which can be called the vendor locator code. Sometimes called a PNR and used to refer to the booking record as a whole, but because the term PNR is specific to GDS, this online help uses the more generic terms "booking" for the booking record and "reservation locator" for the six-character code. code of the unused ticket. Base path: Pre-production https://api.pp.travelport.com/11/air/ Production https://api.travelport.com/11/air/

Related Content: Booking Guide, Ticketing Guide

For supporting NDC carriers only, the JSON APIs support using the value on an unused ticket as form of payment (FOP) Details for the payment to be used to pay for an offer, such as credit card information. The subsequent Add Payment step is required to charge the payment. when ticketing a separate, held booking.

Ticket as FOP Details

The following must be in place to use a ticket as FOP: 

• The passenger has a held booking made with the JSON APIs that is separate from the ticketed itinerary The entire trip on a booking, including all flights on all legs. Also called a journey..

• The passenger has an existing ticketed itinerary that is either fully unflown or partially flown with no active itineraries and that has not been voided, refunded, or exchanged.

Supported Options

When applying an unused ticket as FOP:

• Only one ticket per passenger can be exchanged.

• Tickets are non-transferable and must match the passenger listed on the order.

• If a held booking has multiple passengers, a ticket must be submitted for each passenger on the held booking.

• When exchanging multiple tickets, each ticket must have the same itinerary and coupon status.

• Tickets cannot have segments with an active itinerary.

Workflow

Use the following workflow to apply an unused ticket to a held booking:

1. Create post-commit workbench.

2. Send the OfferQueryBuildFromOffer request per below. The response returns the value of the ticket that can be applied to any new booking.

3. Additional steps may be required depending on the price of the held booking compared to the available ticket value. If the total price of the held booking:

   • exceeds the value of the unused ticket, before commit, you must send Form of Payment and Payment for the balance.

   • is less than the value of the unused ticket, at commit, the residual balance on the ticket is issued as a refund in the form of an EMD Electronic miscellaneous document (EMD); issued for a paid seat, ancillary, or any other paid service after successful payment. See the Ancillary and EMD Guide. coupon. No additional step is necessary.

   • is the exact same as the value of the unused ticket, no EMD is issued and no balance is due. No additional step is necessary.

4. Commit the workbench to issue the new ticket. If a balance due was paid for, the commit issues an EMD. If a balance remains, the passive PNR is updated with DI lines Document instruction (DI) lines in the booking record contain information such as price, flight information, confirmation, ticketing time limits, fees, and form of payment. Not returned as DI lines in the JSON APIs but available through a desktop program. referencing the EMD and the remaining balance contained on it.

Request

Query Parameters

None.

Request Body

Response

Pending.

Example Request

The example request below sends the ticket number for the unused ticket in DocumentNumber.

Example Response

In the following example excerpt from the commit response, the value of the unused ticket exceeded the cost of the held booking. In this case, an instance of Document with @type DocumentTicket returns the ticket number and an amount of 0, while the instance of Document with @type DocumentEMD has a positive amount of 118.2, indicating that a residual value of 118.2 remained on the ticket and has been issued as an EMD.