Skip to content
Last updated

Ticketing Workflow

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

You can add optional seats and ancillaries during either booking 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) to use and the offer to pay for with that FOP. To ticket an itinerary, 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 and seat payment requirements.

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

Ticketing workflow: Required steps

Create post-commit
workbench

Form of payment
(if not stored
in reservation)

Payment for air
offer/s

Commit workbench;
issue ticket/s

Create post-commit
workbench

Form of payment
(if not stored
in reservation)

Payment for air
offer/s

Commit workbench;
issue ticket/s