Reservation and Ticketing Workflows
The AirReservation and AirTicketing APIs provide flexible reservation and ticketing options that support multiple workflows. Both APIs use multiple calls to build a workbench, perform additional steps such as adding an offer, travelers, and form of payment details, and then commit that workbench to end transact the process.
The AirReservation workflow creates a reservation with a PNR, while the AirTicketing workflow issues a ticket. The possible workflows vary by when the form of payment (FOP) information is sent, and whether the itinerary is GDS or NDC. In addition, the workflow for ticketless carriers does not use ticketing at all.
The table below summarizes the possible workflows and steps in AirReservation and AirTicketing that make up each option.
For simplicity the workflows below do not include adding remarks or booking seats, all of which are optional in the AirReservation workflow and are covered in their own topics.
|
Hold and Pay 1: Book, then ticket with FOP |
Hold and Pay 2: Book with FOP, then ticket |
Instant Pay: Book and ticket in one workbench session |
Ticketless Carrier: Book with FOP, no ticketing |
---|---|---|---|---|
Description: |
Use AirReservation to book the itinerary without adding any FOP. Use AirTicketing to send FOP, add that payment, and ticket the itinerary. |
Use AirReservation to book the itinerary and send FOP to be stored until ticketing. Use AirTicketing to add payment and ticket the itinerary. |
Use only AirReservation to send FOP, add payment, and both create a PNR and issue the ticket in the final step. |
Use AirReservation to book the itinerary, sending FOP and committing without adding payment. Ticketless carriers do not accept payment or issue a ticket. |
Supports: |
GDS and NDC |
GDS Only |
NDC only |
Ticketless carriers only |
Workflow steps: |
AirReservation: AirTicketing:
|
AirReservation:
AirTicketing: |
AirReservation: |
AirReservation:
|