LCC API Booking Without GDS: How Indian Agents Connect to IndiGo, Akasa and SpiceJet Directly
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
Indian LCCs like IndiGo, Akasa, and SpiceJet were never designed to live on GDS platforms — they distribute direct or via aggregator APIs. Here's how agents actually connect, what it costs, and where GDS still makes sense.
TL;DR — The Core Answer
Indian LCCs — IndiGo, Akasa Air, and SpiceJet — are not meaningfully available on traditional GDS platforms like Amadeus or Sabre. Travel agents access them through aggregator APIs (Tripjack, eTrav, TBO, or similar) that have direct LCC connections. This is almost always cheaper than going through a GDS, because GDS adds a booking segment fee that LCCs typically pass onto the consumer. For most domestic-heavy agents in India, the GDS has become a tool primarily for international full-service carriers, not domestic LCC inventory.
Why LCCs Don't Really Exist on GDS
The economics of GDS distribution were built around full-service airlines. A GDS charges a booking fee per segment — historically somewhere in the $3-8 range per segment (the exact figure varies by GDS and contract, and changes regularly). For an airline selling a ₹2,500 domestic ticket, paying a GDS booking fee is a significant percentage of the revenue. LCCs globally — Ryanair, AirAsia, IndiGo — decided early that direct distribution was the only model that made unit economics work.
IndiGo has an agency-facing booking system (IndiGo Agency Connect / B2B portal) but it's not the same as GDS access — it's essentially a web interface on top of their own inventory system, with no real PNR interoperability with Amadeus or Galileo. Akasa, being newer, went even more directly to aggregator API distribution. SpiceJet has had an on-again, off-again GDS presence but most agents find the coverage patchy and the fares not competitive with going via an aggregator.
How Aggregator APIs Actually Work for Agents
Platforms like Tripjack, eTrav, TBO Holidays, and Riya Travel's B2B platform act as middle layers. They've signed direct content agreements with each LCC — IndiGo, Akasa, Air India Express, SpiceJet — and expose all of that inventory through a single API or web interface.
Here's what that flow looks like in practice:
- Agent logs into the aggregator portal (or their own OTA platform that's integrated the API)
- Searches a route — say DEL-GOI
- Gets real-time IndiGo and Akasa fares from the aggregator's live connection to those carriers
- Books: the aggregator creates the booking in the airline's system, holds the PNR, and deducts from the agent's prepaid wallet
- Agent receives the PNR, which is the actual airline PNR — it can be managed (web check-in, seat selection) directly on the airline's website
The key point: the aggregator's margin comes from a negotiated spread on the net fare, not a per-segment GDS fee. On high-volume routes like BOM-DEL, aggregator margins are thin enough that the fare the agent pays is often very close to what the airline's own website shows. On lower-volume routes, there may be a slightly higher spread baked in.
Cancellations, Changes, and the Operational Reality
This is where agents feel the pain. When you book through an aggregator API and the passenger wants to cancel, the refund has to travel backwards through the chain: airline → aggregator → agent → passenger. That can mean delays of anywhere from a few business days to a couple of weeks, depending on the aggregator's reconciliation cycle and the airline's refund processing speed.
IndiGo, in particular, has had periods where agent-channel refunds were significantly slower than direct-channel refunds. If your client is comfortable managing their own booking on IndiGo's app after you book the PNR, that actually reduces friction — they can cancel directly with the airline and get a credit shell immediately, which you then handle on the backend with the aggregator. Not every agent wants to explain this to passengers, but it works.
For itinerary changes, the aggregator portal usually exposes a change/rebook function that passes through to the airline system. Always double-check that a change made via the aggregator actually reflects in the airline's system within a few minutes — mismatches between aggregator PNR and airline PNR are rare but they do happen, especially during high-traffic periods.
SpiceJet deserves a special note in 2026: the carrier has had financial constraints that affect inventory availability and schedule reliability. Aggregator platforms vary on how they handle SpiceJet refunds — verify your specific aggregator's SpiceJet refund policy before booking anything non-refundable for a client.
Cost Savings vs GDS — The Real Numbers Picture
I won't give you fake exact figures, but here's the framework: a domestic IndiGo booking on GDS (the few that are accessible) would add a GDS booking fee per segment. A same booking via a direct aggregator API doesn't carry that fee — the aggregator's margin is already in the displayed fare, and it's typically smaller than the GDS surcharge. On a round-trip (two segments each way = four segments), that can add up to a noticeable saving per ticket when multiplied across an agency's monthly volume.
For agents doing mostly domestic volume — 50-200 tickets a month — the annual saving from shifting LCC bookings from GDS to an aggregator API can be meaningful. That said, it's worth running the numbers with your actual ticket mix. If your GDS contract has a good rebate structure that partially offsets booking fees, the calculation changes.
International FSC bookings (Air India, Emirates, Singapore Airlines, etc.) still largely favour GDS access for fare availability, interline ticketing, and the ability to issue multi-carrier itineraries on a single ticket. GDS isn't dead — it's just wrong for Indian domestic LCCs.
Tripjack vs eTrav vs TBO — Quick Comparison
These are the main aggregators most Indian agents use. I won't pretend to have perfect current data on each one's exact rates, because they change constantly and vary by agent tier and monthly volume. But here's the practical lay of the land as of 2026:
- Tripjack: Strong IndiGo and Air India Express coverage. Good tech — their API documentation is relatively clean. Popular with agents building their own front-ends. Wallet-based, requires a prepaid balance.
- eTrav: Good presence in tier-2 and tier-3 agent markets. Slightly older interface but solid inventory. Often cited as having responsive support compared to larger platforms.
- TBO (Travel Boutique Online): Broader B2B product mix including hotels and holidays, which is useful if you want one relationship for flights + hotels. Flight fare margins can vary more than the flight-only platforms.
- Riya Travel B2B / others: Several regional consolidators also have aggregator relationships — worth checking if you're already doing a lot of business with a specific one for better credit terms.
For agents building their own tech platform and accessing inventory programmatically, see also our article on Tripjack API vs building your own GDS integration. And for monitoring multi-carrier fare comparisons in real-time, FlightGPT's search is useful as a benchmarking layer.
When You Should Keep Your GDS Subscription
Despite everything above, don't cancel your Amadeus or Galileo contract yet if:
- You do meaningful international ticket volume — Air India, Emirates, Qatar, Singapore Airlines interline itineraries need GDS for clean ticketing
- You book multi-carrier itineraries where bags need to check through — this still requires an interline agreement on a single ticket, and GDS handles that correctly
- Your corporate clients need specific fare basis codes and policies that aren't accessible via aggregators
- You have a GDS contract with a cashback or incentive structure that partially offsets fees — do the math before walking away
The practical move for most agencies is a hybrid: GDS for international FSC, aggregator API for domestic LCC. Some agencies also reference FlightGPT Partner as a supplementary inventory layer for comparing across sources.
Frequently asked questions
Is IndiGo available on Amadeus GDS in India?
IndiGo has had limited GDS distribution — it appears on some platforms with restricted content, but for full fare availability and competitive pricing, most Indian agents use aggregator APIs (Tripjack, eTrav, TBO) that have a direct IndiGo connection. If you're booking IndiGo via a GDS terminal in 2026 and comparing it to what Tripjack shows on the same route, you'll likely see the aggregator is more complete and often cheaper.
Can I get IndiGo group fares through an aggregator API?
Group fares (typically 10+ passengers) are not usually available through aggregator API portals — they require a direct application to IndiGo's group desk. Some large aggregators have a group desk process, but it's handled manually, not through the automated API. For a genuine group booking, contact IndiGo's corporate/group sales directly or through a well-connected agent.
How long do aggregator refunds take for IndiGo cancellations?
It varies by aggregator and the fare type, but a realistic expectation is 7-15 business days for a refund to credit back to your agent wallet after the airline processes it. IndiGo's own refund to the aggregator can take 5-10 business days, and then the aggregator's internal reconciliation adds a few more days. Instant credits happen only when the fare is non-refundable and there's a credit shell — the actual cash refund timeline depends on IndiGo's processing queue.
Is it safe to book Akasa Air through a third-party aggregator in 2026?
Akasa Air is a live, operational carrier in 2026 and major aggregators (Tripjack, TBO, eTrav) carry their inventory. Booking via aggregator is safe in the sense that you get a real Akasa PNR that you can manage on Akasa's website. The main risk to understand is refund timing — same as IndiGo — and making sure your aggregator has an Akasa content agreement (most major ones do, but a small local aggregator might not).
Does SpiceJet still have B2B agent support in 2026?
SpiceJet is operational but has had financial and operational challenges. Most major aggregators still carry SpiceJet inventory, but agents report that refunds and changes can be slower compared to IndiGo or Akasa. For non-refundable bookings or time-sensitive travel, many agents have shifted that business to IndiGo or Akasa for reliability. Verify with your specific aggregator what their SpiceJet-specific refund and support terms are before committing client funds.