Travel API vs GDS is a common question, and a slightly misleading one. A GDS (global distribution system) is a network that holds airline, hotel and car content; a travel API is the software connection your platform uses to search and book. Every GDS has its own APIs, and most travel API aggregators use the GDSs as one of their sources. The real choice is between connecting to a GDS directly and connecting through an aggregator such as Tripgic, which reaches Amadeus, Sabre and Travelport through one API and adds NDC and 100+ low-cost carriers.
This guide sets out what each route gives you: content, access, time, cost and the people you need. It explains where the GDS is still strongest, where it falls short, how NDC changes the picture, and how to decide. The facts come from the GDS companies’ own developer pages, ARC, and Tripgic’s GDS page, API docs and pricing page.
First, Clear Up the Terms
Four things get called a “travel API” or a “GDS”, and mixing them up is where most bad decisions start.
| Term | What it is | Example |
|---|---|---|
| GDS | A network holding airline, hotel and car content for travel sellers | Amadeus, Sabre, Travelport |
| GDS API | The programming interface one GDS offers to its network | Amadeus Enterprise APIs, Sabre APIs, Travelport TripServices |
| Travel API aggregator | One API in front of many sources — GDSs, NDC, low-cost carriers, hotels | Tripgic and other multi-source APIs |
| Direct airline API | One airline’s own API, often NDC | An airline’s NDC programme |
So “travel API vs GDS” usually means “direct GDS API vs travel API aggregator”. Both are APIs; the difference is how many sources you get through one connection and how much of the work you carry. For the GDS itself, see what a GDS is; for the aggregator model, what a travel API aggregator is.
Why the Choice Exists: A Short History
For decades there was no choice to make. Airline reservation systems grew into the GDSs: Sabre began in 1960, built by American Airlines with IBM, and opened to travel agents in 1976; Amadeus was founded in 1987 by Air France, Iberia, Lufthansa and SAS; Travelport brought together three older systems — Galileo (1G), Apollo (1V) and Worldspan (1P). If you sold flights, you sold them through a GDS.
Three changes opened the door to other routes. Low-cost carriers grew up largely outside the GDS and sold through their own websites and APIs. Airlines adopted NDC to build and sell their own richer offers. And travel moved online, where new businesses needed to launch quickly with small teams. Travel API aggregators grew in that gap: one connection that brings the GDS content together with everything the GDS does not carry.
Direct GDS vs Aggregator: The Key Differences
| Direct GDS API | Travel API aggregator | |
|---|---|---|
| Content | One network’s content: deep full-service airline fares, hotels, cars | Several GDSs plus NDC, low-cost carriers and hotel suppliers |
| Connections to build | One per GDS | One |
| Access | Commercial agreement, often accreditation, a pseudo city code | One agreement with the aggregator |
| Certification | Per GDS, before live data | Usually handled by the aggregator with its sources |
| Time to first booking | 6–12 months per GDS | Your own build time, once |
| Data format | Each GDS’s own, sometimes SOAP and REST mixed | One normalized format |
| Duplicate results | Yours to merge if you use several GDSs | Usually merged for you |
| Commercial model | Set in each GDS contract | Per booking: percentage or flat fee, sometimes an activation |
| Who it suits | High-volume, accredited sellers with GDS skills | New and growing platforms, OTAs, B2B portals, startups |
Neither column is “modern” or “old”. GDS companies now offer REST and JSON APIs — Travelport’s TripServices, for example, is REST and JSON only. The difference that matters is scope: one network per contract versus many sources through one.
What the GDS Does Best
The GDS earned its place, and it still has real strengths:
- Full-service airline depth. Most full-service airlines distribute through the GDSs, with fares, rules and availability that have been standardised for decades.
- Corporate travel. Travel management companies and corporate booking tools are built around the GDS. Sabre, for example, says it holds 75% of North American managed business travel.
- Agent workflows. Experienced agents use GDS terminals and formats every day; large agencies have staff and processes built on them.
- Servicing. Exchanges, refunds and schedule changes on GDS bookings follow mature, well-known procedures.
- Hotels and cars for business trips. The GDSs carry hotel chains and car rental used heavily in corporate travel.
If your customers are corporations, your agents work in a GDS terminal, and you sell mainly full-service airlines, a direct GDS connection can be the right foundation.
Where the GDS Falls Short
- Low-cost carriers. Many low-cost airlines sell mainly through their own channels and APIs, so a GDS-only connection misses fares your customers can see elsewhere. See our low-cost carrier API guide.
- NDC content. Airlines increasingly build their best offers in NDC — fare families, bundles, NDC-only fares. ARC reports that NDC made up 21.5% of US agency air transactions it settled in August 2026.
- GDS surcharges. Some airlines add a charge to bookings made through the traditional GDS channel; Lufthansa Group introduced a 16-euro charge of this kind in 2015. The same seat can cost more via the GDS than via NDC. See NDC in airlines.
- One network at a time. Each GDS has different strengths by airline and region. Covering all three means three contracts, three integrations and three certifications.
- Access barriers. Contracts, accreditation, pseudo city codes and certification make the GDS slow to enter for a new business.
None of these is a reason to avoid GDS content. They are reasons to combine it with other sources — which is exactly what an aggregator does.
How You Get Access to Each
Direct GDS
- Agree commercial terms with the GDS company and decide which APIs and markets your contract covers.
- Sort out ticketing authority: your own IATA (BSP) or ARC accreditation, or a host agency or consolidator.
- Receive credentials and a pseudo city code (PCC), which defines your workspace and region.
- Build and test in the GDS’s test environment.
- Pass certification, where the GDS reviews your flows before live data.
- Repeat for each additional GDS.
The GDS developer pages make the first steps easy — Sabre offers a free Developer Hub sandbox and Travelport free TripServices trial credentials — but production needs the full path. Our Sabre API guide, Travelport API guide and Amadeus API guide cover each network’s steps.
Through an aggregator
- Talk to the aggregator and agree terms.
- Build in its sandbox, once.
- Go live when you are ready, with all its sources at once.
With Tripgic, the steps are set out on the pricing page: request access, sign an NDA and check live rates for your market in a Live Rate Check Panel, build in a free sandbox, then pay a one-time activation when you are ready; live credentials are usually provisioned in 3–5 business days.
Cost: How the Two Compare
The two routes charge in different places.
| Cost | Direct GDS | Aggregator |
|---|---|---|
| Contract and access | Negotiated per GDS; may include access fees and minimums | One agreement; sometimes an activation fee |
| Per booking | Set in the GDS contract; airlines and hotels also pay the GDS per booking | A percentage of the booking or a flat fee per transaction |
| Certification | Per GDS, plus your team’s time | Usually none on your side |
| Build | Per GDS, in its format | Once |
| Maintenance | Per GDS, as each changes | Mostly the aggregator’s |
| Airline surcharges | Apply to GDS bookings where airlines charge them | Depends on the source used for each fare |
For a large agency with high volume and an existing GDS team, direct contracts can be cheaper per booking. For most new and growing businesses, the aggregator is cheaper in total because the expensive part — integration and certification — happens once, not three times. For a full breakdown, see our guide to GDS API cost, and for aggregator models, travel API pricing.
Time to Launch
| Stage | Direct GDS | Aggregator |
|---|---|---|
| Agreement | Weeks to months, per GDS | Days to weeks, once |
| Build | Per GDS, often with a learning curve | Once, in one format |
| Certification | Per GDS, with its own queue | Usually not your queue |
| Total | 6–12 months per GDS | Mostly your own build time |
The 6–12-month figure is from Tripgic’s GDS page for any direct GDS connection. It matches what GDS developers report: the business side and certification take longer than the code.
After the Sale: Servicing on Each Route
Selling the ticket is half the work. Changes, refunds and disruptions decide how much each booking really costs you.
| Servicing task | Direct GDS | Aggregator |
|---|---|---|
| Voids, refunds, exchanges | GDS procedures your team runs, with GDS-trained staff | API calls to the aggregator, with its stated fees |
| Schedule changes | Arrive in GDS queues your team must work | Arrive through the aggregator; check how it notifies you |
| NDC bookings | Serviced by the airline’s own order process | Depends on the aggregator’s NDC handling |
| Low-cost bookings | Usually outside the GDS, handled separately | In the same API as everything else |
| Reconciliation | Against each GDS’s and airline’s reports | Against one statement |
Ask any option the same question before you choose: what happens, step by step, when a customer wants to change a ticket? The clearer the answer, the lower your support cost will be. On Tripgic, flight voids, refunds, reissues and name changes run through the API and carry a flat service fee per ticket plus any airline penalty, as its pricing page states.
The People You Need
A direct GDS project needs people an aggregator project often does not:
| Role | Direct GDS | Aggregator |
|---|---|---|
| Developers with GDS experience | Strongly recommended | Not required |
| Someone to manage GDS contracts and certification | Yes, per GDS | One provider relationship |
| Ticketing and accreditation lead | Yes | Depends on the provider’s ticketing model |
| Support staff trained on GDS formats | Usually | Trained on your own tools |
For a small team, this row is often the deciding factor: a direct GDS asks for skills the team does not have yet. Hiring them takes time too, and it adds to the months the business side already needs.
How NDC Changes the Choice
Airlines are moving offers to NDC, their own modern channel. That changes the comparison in three ways:
- A GDS-only seller sees less. NDC-only fares and bundles may not appear, or appear with surcharges.
- The GDSs are adapting. Each now carries NDC content, but what passes through depends on the GDS, the airline and your contract.
- Aggregators blend both. An aggregator can return NDC offers and GDS fares side by side, so customers see the best option regardless of channel.
For most sellers, this tips the balance further toward a multi-source connection. See our guides to NDC vs GDS and the NDC aggregator model.
Which Should You Choose?
| Your situation | Likely the better fit |
|---|---|
| Large agency or TMC, high volume, accredited, GDS-skilled staff | Direct GDS (often plus an aggregator for low-cost content) |
| Corporate clients who require a specific GDS | Direct GDS, or an aggregator that carries that GDS |
| New OTA, travel app or startup | Aggregator |
| Agency moving online with a small team | Aggregator |
| B2B portal selling to agents | Aggregator, possibly adding direct GDS later |
| Seller needing low-cost carriers and NDC | Aggregator |
| Seller needing more than one GDS | Aggregator |
Many businesses do both over time: an aggregator first, to sell quickly, then a direct GDS contract once volume justifies the cost and the team.
Using Both: How a Hybrid Setup Works
Many mature sellers run a direct GDS and an aggregator side by side. It works well when three rules are followed:
- Decide what each source is for. For example: the direct GDS for corporate clients and negotiated fares; the aggregator for low-cost carriers, NDC and hotels.
- Merge before you show. The same flight can arrive from both. Remove duplicates and keep the better price, or customers see the same flight twice.
- Keep one booking record. Store every booking in your own system with its source, so support, finance and changes work the same way whichever route it took.
A hybrid setup costs more to run than either alone, so it usually comes later, once volume and a specific need — a corporate contract, a negotiated fare — justify the second connection.
Common Mistakes When Choosing
- Choosing on the label. “API” and “GDS” are not opposites. Compare what content each option returns for your routes.
- Ignoring low-cost carriers. If your customers fly them, a GDS-only setup will look expensive.
- Underestimating certification. It is the stage where direct GDS timelines slip most.
- Forgetting ticketing. Decide whose accreditation issues your tickets before you sign anything.
- Signing for one GDS when you need two. Each additional network is a new contract, build and certification.
- Comparing per-booking fees only. Build, certification and maintenance are usually the larger costs.
Three Worked Scenarios
A new OTA in South Asia. Its customers fly full-service airlines to the Gulf and Europe and low-cost carriers regionally. A single GDS would miss much of the low-cost market, and the team has no GDS experience. An aggregator with GDS, NDC and low-cost content lets it launch with every fare its customers compare.
A corporate TMC in North America. Its clients mandate specific booking tools and fares, its agents work in a GDS terminal, and its volume is high. A direct GDS connection is its backbone; it may still add an aggregator for low-cost and NDC content its corporate customers ask for.
A B2B portal for travel agents. Agents expect every airline, plus hotels and transfers, in one place, at net prices they can mark up. An aggregator gives the breadth and one format; a direct GDS can be added later for specific markets.
Questions to Ask Before You Decide
| Question | Why it matters |
|---|---|
| Which airlines and routes do my customers fly most? | Decides whether GDS content alone is enough |
| Do I need low-cost carriers and NDC offers? | GDS-only connections often miss them |
| Am I accredited, or who will issue my tickets? | Needed for any direct GDS ticketing |
| Do I have, or can I hire, GDS-skilled developers? | Direct GDS has a steep learning curve |
| How soon must I sell? | 6–12 months per GDS versus one build |
| Will I need more than one GDS? | Each adds a contract, a build and a certification |
| What does each option cost at my volume? | Model the whole cost, not only the per-booking fee |
How Tripgic Gives You GDS Content Through One API
Tripgic is a B2B travel API aggregator built for the second route. From its own pages:
- All three GDS networks. Amadeus, Sabre and Travelport through one REST API, with no GDS contract or per-GDS certification on your side, per its GDS page.
- Merged results. When the same flight appears in more than one GDS, it is returned once, at the best available price, in normalized JSON.
- NDC and low-cost in the same search. 100+ low-cost carriers and NDC content beside the GDS fares — 800+ airline and LCC connections in total.
- The full flight flow. Fifteen flight endpoints in the API docs: search, branded fares, validation, travellers, booking, baggage, seats, meals, ticketing and cancellation.
- More than flights. 2M+ hotel properties and 8 product families in all, over 73 endpoints, in one format.
- Final prices, flat fee. Prices at validation and booking are final: the supplier net fare plus a flat Tripgic amount per passenger, never a percentage; figures on the pricing page.
- Test first. A free sandbox after a short call; activation for live use usually takes 3–5 business days.
Final Thoughts
“Travel API vs GDS” is really “one GDS at a time, or many sources through one API”. The GDS remains the backbone of full-service airline and corporate travel, and a direct connection makes sense for sellers with the volume, accreditation and skills to run it. For most others — new OTAs, agencies moving online, B2B portals, travel apps — an aggregator that includes the GDSs, NDC and low-cost carriers is faster, simpler and usually cheaper in total.
Decide from your customers’ routes, your team and your timeline, not from the label. Then test the option you choose with your own searches before you sign. Run your twenty busiest routes, compare the fares and carriers that come back, and book, change and cancel a test reservation. A week of that tells you more than any comparison table, including this one.
Want GDS, NDC and low-cost fares through one API? Book a demo and get Tripgic sandbox credentials after a short call.
Golam Shahrier





