Ticket
The document or electronic record representing the right to air transport. An order can be confirmed while ticket issuance is still pending.
Why it matters
In the flight domain, itinerary, leg, segment, carrier and seller identity are distinct. Flattening them too aggressively mixes schedule, fare, agent and booking rules. The search UI can be simple, but the source model needs enough detail for repricing and handoff.
What does it look like in practice?
The same itinerary can be sold by multiple agents with different fare brands, baggage and booking conditions. Segment schedule and seller/offer identity are different concepts.
Implementation questions
- Which legs and segments form the itinerary?
- Are marketing and operating carriers separated?
- Is agent/provider identity retained?
- Is the source reference available for repricing?
Common mistakes
- Modeling an offer as flight number plus price
- Mixing marketing and operating carriers
- Embedding agent identity into itinerary identity
Where does it appear in the travel stack?
Ticket commonly appears across flight layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Order Confirmed but Ticket Not Issued Troubleshooting
Diagnose flight cases where an order is confirmed but ticket/document issuance is incomplete by separating order, payment and fulfillment state.
Explore →Flight Reprice, Schedule Change, Ticketing and Order State
Separate reprice, schedule change, order, PNR, payment and ticket/document states across the flight-booking lifecycle.
Explore →Travelport Air API Integration Guide
Design a production Travelport JSON Air v11 integration across OAuth, GDS/NDC offer lineage, AirPrice, workbenches, commit recovery, ticketing, reconciliation and monitoring.
Explore →Travelport APIs: Air Distribution Platform Profile
A technical profile of Travelport JSON APIs covering OAuth, air search, pricing, GDS and NDC offers, workbench booking, reservations, ticketing and lifecycle management.
Explore →NDC Offer/Order Lifecycle: Search to Servicing
Model NDC Offer/Order lifecycle across search, offer, revalidation, order creation, payment, ticketing, servicing and reconciliation states.
Explore →Travel PII and Passenger Data Boundaries
Design safe boundaries for passenger identity, contact, payment and travel-document data across search, booking, logging and provider integrations.
Explore →