Seats Workflows
The diagram below illustrates workflows to add seats either during booking
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 to an existing reservation, and, optionally, to send ancillary Any paid optional service filed for a flight. Industry examples include paid seats, paid baggage, carbon offsets, pet transport fees, and unaccompanied minor charges. See the Ancillary and EMD Guide for supported ancillaries. payment in the same session.
Seats are also supported in the NDC Instant Pay workflow by sending seat map and seat book requests after adding travelers.
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. carriers. For some NDC carriers and all GDS 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. carriers, you must commit API call that ends a workbench session, finalizing all changes and requests in that session. Depending on the workbench transactions, the commit workbench request may create a reservation, issue a ticket or EMD, exchange tickets, or modify a reservation. the booking workbench to confirm the seat/ancillary, and send payment and issue the EMD Electronic miscellaneous document (EMD); issued for a paid seat, ancillary, or any other paid service after successful payment. See the Ancillary and EMD Guide. in a separate workbench. For ancillary payment requirements by NDC carrier An airline., see NDC capabilities by airline through JSON API in the Travelport Knowledge Base. (If you need login assistance, see Knowledge Base NDC Resources.)Each box in the diagram represents one API call in the workflow.
Related Content: Seats Guide, Seat Map API Reference, Seat Book API Reference
