Connecting Amadeus, Sabre and GDSs
APIs, NDC, monitoring, error handling: what keeps a GDS connection running in production, and why it most often breaks.
- A GDS (Amadeus, Sabre, Travelport) provides inventory and booking functions; it does not provide user journeys or business rules.
- NDC will not replace the GDS overnight: both channels coexist and need to be reconciled.
- Most incidents come from exceptions, not the happy path.
- Without granular monitoring, a degraded connection stays invisible until it affects a customer.
What is a GDS, and what is an Amadeus or Sabre connection for?
A GDS (Global Distribution System) is travel’s traditional marketplace: it aggregates offers from airlines, hotel chains and car rental companies, and exposes search, booking, ticketing and modification functions. Connecting to Amadeus or Sabre lets an agency, tour operator or platform use these offers through its own tools, without going through the GDS interface.
What a GDS connection enables in practice
- Search and compare availability and fares
- Create, modify and cancel booking records
- Retrieve fare rules and applicable conditions
- Feed a back office, CRM or reporting tool
Why does a GDS integration break in production?
Because the happy path is rarely the problem. Breakdowns come from exceptions: a fare disappearing between search and booking, an unexpected response format, a timeout, an overlooked fare rule or a record changed on the supplier side. With real volumes and real peaks in production, these cases become daily occurrences.
| Common cause | What to put in place |
|---|---|
| Fare expiration between search and booking | Systematic revalidation before confirmation |
| Partial response or unexpected format | Payload validation and explicit fallback |
| Variable response times | Timeouts, controlled retries and graceful degradation |
| Unclassified supplier error | Automatic classification and routing to the right team |
Should you move to NDC and abandon the GDS?
It is not an either-or decision. NDC (New Distribution Capability) lets airlines distribute richer offers directly, but not every route, content type or servicing process is available everywhere. In practice, both channels coexist: you need to compare offers from both sources, reconcile them and process them using the same business rules.
How can you tell whether a GDS connection is reliable?
Through three measurable signals: the incident rate across flows, the volume of manual rework in operations and the time taken to detect an anomaly. A connection is reliable when anomalies are detected before customers report them, and errors are classified automatically instead of generating alerts that nobody handles.
How does Travel Tech Factory address this?
This is Travel Connect Factory’s remit: connectors designed to withstand production, granular monitoring of data exchanges and automated error handling that detects, classifies and resolves issues instead of simply raising alerts. Every intervention aims to reduce operational workload and manual rework.
Further reading
- IATA — New Distribution Capability (new tab)
The exchange standard for airlines, distributors and technology providers.
- Amadeus for Developers — the booking journey (new tab)
Offer search, fare confirmation, booking creation and management through the Self-Service APIs.
Automating incoming email management
Classification, routing, enriching booking records, executing authorised actions: what email automation really changes in a travel agency.
Read the guide GUIDE · AI IN TRAVELAI in a travel agency
Where AI brings measurable gains in an agency, where it fails and what governance framework makes its use sustainable.
Read the guide GUIDE · SBT & BUSINESS TRAVELSelf Booking Tools (SBTs) and conversational AI
What an SBT is, what to check in the booking journey and what a conversational interface can offer.
Read the guideReady to transform
your travel ?
Start with your most pressing need.
We will shape the next steps with you.