End-to-end servicing flows for orders that already exist. Each flow sets out the API sequence, with request and response inputs and outputs documented at every stage. All flows are NDC 21.3.
Creating an order on hold, then requoting and confirming it before the hold expires.
The hold booking flow. Inputs and outputs are provided for each API at each stage of the sequence.
The requote and confirm held booking flow. Inputs and outputs are provided for each API at each stage of the sequence.
Adding seats and paid services to an order after the sale has completed.
Reserve free and/or paid seats against an existing order. See SeatAvailability samples and OrderChange samples under Post Sale Seat Purchase.
Add paid services to an existing order. See ServiceList samples under Post Sale Service Purchase Flow.
Correcting passenger names and identity documents on an existing order.
Correct minor errors in a passenger's name after a booking has been created — fixing typos or adjusting middle/last names — without reissuing a new ticket where the airline permits it.
Update or correct passenger identity information on an existing booking — passport details, nationality or date of birth — so passenger data reaches border control accurately before departure.
Changing itineraries, splitting orders and cancelling for refund.
The voluntary date and time change flow. Inputs and outputs are provided for each API at each stage of the sequence.
Separate one or more passengers from an existing booking into a new order, traditionally known as a Split PNR, so itineraries, ticketing, payments and modifications can be managed independently.
The voluntary cancel flow. Inputs and outputs are provided for each API at each stage of the sequence.
Flows are documented against NDC 21.3. For questions on any flow, raise a ticket through the Technical Support Helpdesk.
