Booking Workflow

The diagram below illustrates the typical JSON API workflow to create a reservation, including all required and some optional steps. See All Book and Ticketing Workflows Diagrams for additional workflow options.

Seats and ancillaries can be added during bookingClosed 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 in a separate workbench session, or later during ticketing, per the support noted in the Seats and Ancillaries guides.

In the initial booking workbench only, if needed you can send Cancel Workbench Items to remove all offers. (Cannot be used to cancelClosed Cancel a ticket outside the void period without rebooking on another itinerary. Depending on the airline ticket policy, canceling a ticket may result in a full, partial, or no refund. offers from existing reservations, only out of the workbench.) Traveler details and the workbench session are retained. Supported at this time only for NDCClosed New Distribution Capability, an XML standard for exchanging data that supports airlines in distributing their content directly to online travel agencies. See the NDC Guide..

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

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

Form of payment (FOP) can be added during the booking workbench only for GDSClosed Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. In the JSON APIs, GDS content is distributed from Travelport.. If FOP is added for NDC during booking it is not stored and must be sent again at ticketing. Or, for NDC only, you can send both FOP and payment in the same workbench session to book and ticket at once in the NDC Instant Pay flow.