GDS vs Flight API for Indian Travel Startups: True Cost Compare
By Arjun Kapoor (Arjun Kapoor tracks error fares, mileage runs and award-chart sweet spots for Indian travellers. He moderates two Telegram fare-alert channels and has booked Europe round-trips at sub-₹25,000 four times in the last 24 months.) · Published · 11 min read
GDS or REST API — it's the first real infrastructure decision for any India travel startup. GDS wins on breadth and BSP compliance; APIs win on cost and LCC coverage. Here's the real-world cost breakdown and a decision matrix by stage and volume.
TL;DR: Which Should You Actually Pick?
If you're building a travel startup in India and need flight inventory, GDS (Amadeus, Galileo/Travelport, Sabre) gives you the widest breadth — most full-service carriers, IATA BSP ticketing, and robust ancillary support. REST API providers (like Kiwi.com's Tequila, Duffel, TBO Holidays, Via.com, or direct airline APIs) are cheaper to stand up, cover LCCs that GDS often misses, and don't require you to commit to a long-term IATA contract. For most Indian startups doing under a few thousand tickets a month, a solid API aggregator beats a GDS hands down on cost and speed-to-market. At serious scale — thousands of BSP tickets a month, corporate travel, or IATA-required products — the GDS becomes worth the pain.
Read on for the full breakdown.
What Is a GDS and Why Does It Matter for India?
A Global Distribution System is, at heart, a massive real-time database of airline seat inventory — connected directly to carrier reservation systems via IATA-standard protocols. Amadeus (headquartered in Madrid, dominant in India), Galileo (now under Travelport), and Sabre all have India-specific operations and are wired into BSP-India, which is how IATA governs agent ticket settlement in this market.
If you want to issue a proper IATA e-ticket for Air India, Vistara (historical — now merged into Air India as of 2024), or international carriers like Emirates, Singapore Airlines, or Lufthansa, you almost certainly need a GDS connection or an IATA-accredited subagent relationship. Full-service international carriers don't typically expose their full fare classes and ancillaries through cheap REST APIs.
The Indian domestic picture is different. IndiGo, Air India Express, Akasa Air, and SpiceJet all have APIs (direct or via aggregators). IndiGo in particular is notoriously GDS-unfriendly — its domestic inventory on GDS platforms is often limited to published fares, while the airline's own API and aggregators like Via.com or TBO Holidays have better access. This is the core tension that every Indian travel tech builder runs into.
True GDS Setup and Running Costs in India (2026 Reality)
Let me be honest: GDS pricing in India is not public, and it's negotiated. What I can tell you from the market is the rough shape of the costs.
- IATA accreditation: To ticket directly on GDS, your agency needs IATA approval. The accreditation process involves a financial guarantee (often a bank guarantee or deposit, typically in the range of ₹2–8 lakh depending on the bank and guarantee level), IATA application fees, and audited accounts. Plan for 3–6 months end-to-end.
- GDS connection costs: Amadeus and Travelport typically charge a booking transaction fee — per-segment or per-ticket — rather than a flat monthly fee at the agency level. But if you're building a tech platform rather than an agency, you'll apply for GDS API access (Amadeus Self-Service or Enterprise, Travelport's JSON API), and those contracts involve minimum commitment thresholds and setup fees that can run anywhere from a few lakh to ₹15 lakh or more depending on what tier you negotiate.
- Development effort: GDS APIs — especially Amadeus Enterprise or Sabre's Red App ecosystem — are not REST-simple. They carry legacy SOAP/XML baggage, complex PNR management, fare calculation rules, and ticketing workflows that take a developer team months to implement correctly. Budget 3–6 months of developer time before you can reliably ticket and process refunds.
- Ongoing segment fees: Every booking costs a GDS transaction fee (paid by the agency or passed back via productivity bonuses depending on your deal). These add up at low volumes and can make economics tight unless you're generating enough bookings to unlock rebate tiers.
Total first-year cost to go live on GDS properly — tech build, IATA accreditation, financial guarantee, and GDS contract — is realistically in the ₹10–25 lakh range for a small startup, sometimes more. That's before you've acquired your first customer.
REST API Providers: What You're Trading Off
The alternative path is to use one of the growing number of REST API aggregators. In India, the main ones travel startups actually integrate are:
- TBO Holidays API: Huge inventory, strong LCC coverage in India, relatively straightforward integration. Requires a B2B agent relationship and credit/wallet arrangement.
- Via.com API / Riya Travels B2B: Strong on domestic India inventory including IndiGo. Often used by smaller OTAs.
- Duffel: UK-based, clean modern REST API, growing carrier connections. Not all Indian carriers are live but improving. Works without IATA accreditation — Duffel holds the IATA license and you operate as a subagent effectively.
- Kiwi.com Tequila: Great for multi-city, self-transfer itineraries. Less relevant for pure India domestic.
- Airline direct APIs: IndiGo, Akasa, and Air India Express each have direct B2B channel APIs with varying access requirements.
The trade-offs: REST APIs are faster to integrate (weeks, not months), cheaper to stand up (often no large upfront commitment), and frequently have better LCC coverage than GDS. What you lose is depth on international full-service carriers, the ability to ticket directly on BSP, and often the sophisticated fare-rule handling that GDS provides. You're also dependent on someone else's cache and availability, so you may see stale fares occasionally.
For a bootstrapped startup or a platform doing under a few thousand tickets a month, REST API aggregators make more sense while you build volume. You can always add a GDS layer later when the economics justify it.
Decision Matrix: GDS vs API by Stage and Volume
| Situation | Recommended path | Reason |
|---|---|---|
| Pre-revenue / MVP stage | REST API aggregator | Low cost, fast integration, no IATA overhead |
| India domestic LCC focus | REST API (TBO, Via, direct) | GDS coverage of IndiGo/Akasa is weak |
| International FSC-heavy | GDS (Amadeus preferred in India) | Fare depth, seat maps, ancillaries |
| Corporate travel product | GDS | Negotiated corporate fares, policy tools |
| High volume (5,000+ tickets/month) | GDS (negotiate hard) | Segment rebates improve economics at scale |
| IATA BSP ticketing required | GDS or accredited subagent | BSP settlement mandated by IATA for certain products |
| Mixed LCC + FSC platform | API + GDS hybrid | Best coverage, complex to build but standard at scale |
The FlightGPT Partner portal (agent.flightgpt.in) takes a different route — it aggregates inventory via metasearch so agents get fare comparison across sources without needing to build and maintain GDS connections themselves. Worth exploring if you want to test B2B inventory flows before committing to infrastructure.
Hidden Cost: Developer Time and Maintenance
Nobody talks about this enough. GDS integrations aren't one-time builds. Fare rules change, carrier participation changes, BSP reporting formats update, and the GDS itself releases new API versions. A solid GDS integration is a living codebase that needs someone paying attention to it.
With REST API aggregators, most of this maintenance burden shifts to the provider. When IndiGo changes its baggage rules, TBO or Via updates their API — you just consume a cleaner field. When you're on a direct GDS connection and an airline changes its fare filing format, that's your problem to handle.
Budget for at least one developer spending meaningful time each month on fare-tech maintenance regardless of which path you choose. If your founding team doesn't have this in-house, factor in the cost of a flight-tech consultant — there are specialists in India who work specifically on GDS and airline system integrations.
What About AI Flight Search Platforms?
Increasingly, travel platforms aren't building their own GDS or API connections at all — they're using metasearch layers that pull prices from multiple sources and then redirect to agents or OTAs for actual booking. FlightGPT operates this way: an AI-powered search layer that compares across sources with natural-language queries, without requiring the startup to maintain inventory connections.
If you're building something customer-facing (rather than an agent-facing booking system), this model is worth seriously considering. The inventory problem is solved; you focus on the user experience. If you need deep booking functionality — PNR creation, ticketing, post-booking services — you still need the underlying connections, but you can start with metasearch to validate demand before committing to infrastructure.
Also worth reading: our piece on which GDS is actually best for India agents and the B2B wallet and credit system guide if you're thinking through how agent payments work in your platform.
Frequently asked questions
How much does GDS access cost for a travel startup in India?
It varies considerably by GDS (Amadeus, Galileo/Travelport, Sabre), your negotiated tier, and whether you're going via IATA accreditation or through an aggregator. Realistic first-year costs — including IATA financial guarantee, setup, and basic tech build — are often in the ₹10–25 lakh range. Verify current terms directly with Amadeus India or Travelport India as pricing is negotiated, not public.
Can a travel startup access GDS without IATA accreditation?
Yes — you can connect as a subagent through an IATA-accredited aggregator (like TBO Holidays or Via.com in India), or use platforms like Duffel which hold the IATA license and expose inventory via a clean REST API. You lose some flexibility on fare access but avoid the accreditation overhead, which is significant for early-stage companies.
Does IndiGo have good GDS coverage?
IndiGo's GDS coverage has historically been limited for domestic fares — the airline prefers its own B2B channel. API aggregators like TBO Holidays and Via.com typically have better domestic IndiGo inventory than GDS platforms. This is one of the main reasons Indian domestic-focused startups often prefer the API route.
What's the fastest way to get flight inventory for an Indian travel startup MVP?
A REST API aggregator — TBO Holidays, Via.com, or an international provider like Duffel — is the fastest path. Integration typically takes weeks rather than the months a GDS connection requires. You won't have the same international fare depth, but for an MVP validating demand, it's sufficient. You can layer in GDS later when volume and economics justify it.
Is there a GDS that's better than the others for India specifically?
Amadeus has the strongest footprint in India — more airlines participating, stronger BSP-India integration, and more experienced local support. Travelport (Galileo) is the second choice for many India agents. Sabre has a smaller India presence. For the full comparison, see our <a href='/blog/amadeus-vs-galileo-vs-sabre-india-travel-agent-2026'>Amadeus vs Galileo vs Sabre guide</a>.
Should a B2B travel portal in India use GDS or API for agent access?
For a B2B portal serving agents (rather than end consumers directly), the answer depends on what your agents need. If they're primarily booking domestic LCC travel and international travel via consolidators, an API aggregator layer works well and is cheaper. If your agents are issuing BSP tickets for full-service international routes, you need GDS access or an IATA subagent arrangement. Many mature B2B portals in India run both.