Skip to content
Last updated

Booking Workflow

The diagram below illustrates the typical TripServices 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 booking, or in a separate workbench session, or later during ticketing, per the support noted in the Seats and Ancillaries guides.

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

Booking workflow: Required and optional steps

Create
new workbench

Add
offer

Add traveler/s
(traveler
remarks optional)

Add other remarks
& service requests
(optional)

Seat map
(optional)

Book seat/s
(optional; repeat
for each segment)

Ancillary shop
(optional)

Ancillary price
(required for NDC ancillaries;
not supported for GDS)

Book ancillary
(optional)

Form of payment
(optional and
GDS only at book)

Commit workbench;
create reservation

Create
new workbench

Add
offer

Add traveler/s
(traveler
remarks optional)

Add other remarks
& service requests
(optional)

Seat map
(optional)

Book seat/s
(optional; repeat
for each segment)

Ancillary shop
(optional)

Ancillary price
(required for NDC ancillaries;
not supported for GDS)

Book ancillary
(optional)

Form of payment
(optional and
GDS only at book)

Commit workbench;
create reservation

Form of payment (FOP) can be added during the booking workbench only for GDS. 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. When adding an unpriced segment to the workbench, use the Unpriced Segment API instead of Add Offer. Or, or if adding both an unpriced segment and an offer, send both Unpriced Segment and Add Offer.