Itinerary
A flight journey composed of legs and segments. Pricing options are commonly defined in itinerary-plus-agent context.
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?
Itinerary commonly appears across flight layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Google Flights: Partner Access, Offers and Booking Handoff
Understand Google Flights partner access, itinerary and seller ranking, fare equivalence and booking handoff through practical operational scenarios.
Explore →Skyscanner Flight API Integration: Developer Guide
Implement Skyscanner Flights Live Prices with x-api-key authentication, create/poll lifecycle, request-response models, itinerary/leg/segment mapping, agents, pricing options, rate limits and observability.
Explore →Skyscanner: Flight Discovery, Live Prices and Booking Handoff
Choose Skyscanner live or indicative flight data, preserve itinerary and seller identity, and diagnose price, polling and booking-handoff failures.
Explore →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 →Agoda: OTA and Multi-Vertical Travel Marketplace Profile
Understand Agoda as an OTA and multi-vertical travel marketplace spanning accommodation, flights and activities.
Explore →Amadeus Enterprise APIs and NDC Integration Guide
Design Amadeus Enterprise API Portal and Travel Platform/NDC integrations around access, entitlement, offer/order lifecycle, servicing, quota boundaries and observability.
Explore →