Ticketing Workflow

The diagram below illustrates the workflow to ticket an existing reservation.

You can add optional seats and ancillaries during either 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. or ticketing, or in a separate workbench session, per the support noted in the Seats and Ancillaries guides.

Add Payment references both the 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. to use and the offer In the JSON Search APIs, an offer is a product available at a specific price under a set of terms and conditions. An offer includes the flight or connecting flights for one leg of the itinerary, plus a service level that includes the cabin class and any fare codes that may apply. At booking, the selected offer from the Search response - including the flight/s, service level, price, terms and conditions, and brand if applicable - is converted into a single Offer object that is subsequently returned for that booking. to pay for with that FOP. To ticket an itinerary The entire trip on a booking, including all flights on all legs. Also called a journey., at a minimum you must send payment for the offer for the flight/s. It may be optional or mandatory to add payment for offers for any ancillaries or paid seats that have been added, if those have not already been paid for. See the Ancillary and EMD Guide for more about ancillary Any paid optional service filed for a flight. Industry examples include paid seats, paid baggage, carbon offsets, pet transport fees, and unaccompanied minor charges. See the Ancillary and EMD Guide for supported ancillaries. and seat payment requirements.

Each box in the diagram represents one API call in the workflow.

Related Content:Booking Guide, Ticketing Guide, All Book and Ticketing Workflows Diagrams