Understand NDC vs GDS content differences as a travel API integrator

domain: travel-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. GDS (Global Distribution Systems: Amadeus, Sabre, Travelport) aggregate content from hundreds of airlines via EDIFACT-based protocols; NDC (New Distribution Capability) is IATA's XML standard allowing airlines to distribute rich, personalized content directly.
  2. Many airlines now withhold their cheapest fares, bundles, and ancillaries from GDS and only distribute them via NDC channels — if your API only accesses GDS content, you may show higher prices than the airline's own website.
  3. To access NDC content, you either connect directly to each airline's NDC API (requires certification and commercial agreements) or use an aggregator that has done this (Duffel, Verteil, TravelFusion, and others).
  4. NDC responses are richer but less standardized than GDS — fields like baggage allowance, fare rules, and seat maps vary significantly in structure between airlines even within the NDC standard.
  5. When aggregating both GDS and NDC content, deduplication is necessary — the same flight may appear as a GDS fare and an NDC fare with different prices, different ancillary inclusion, and different booking conditions.
  6. Refund and change rules differ by channel: a ticket booked via NDC direct must typically be changed via the same NDC channel — cross-channel modifications (book NDC, change via GDS) are often not supported.

Known gotchas

Related routes

Ingest and normalize travel itinerary data across booking sources using the Expensify Integrations API
integrations.expensify.com · 6 steps · unrated
Understand the SilverRail and rail GDS integration model for multi-carrier European rail content
silverrail.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans