Can LCC content be mixed with GDS and NDC in the same search?

Yes, and most production portals do. Search results merge GDS, NDC, and LCC fares with clear labeling. Behind the scenes, booking flows and post-booking servicing differ across the three channels (PNRs for GDS, Orders for NDC, carrier-direct for LCC) and the platform must route correctly. adivaha handles routing transparently on a unified booking flow that abstracts the channel difference from the traveler.

LCC API Integration for Travel Portals and OTAs

Q: What is LCC API integration?

LCC stands for Low-Cost Carrier - airlines that operate on a no-frills, point-to-point, ancillary-revenue model. LCC API integration connects a travel portal to these carriers, which do not typically distribute through traditional GDS channels and instead offer their own direct APIs or use aggregators like Travelfusion, Mystifly, and TBO. Integration is essential for portals serving routes where LCCs dominate market share.

Q: Why don't LCCs distribute through GDS?

GDS distribution costs typically run 5 to 12 USD per booking, which is significant on a USD 50 ticket. LCCs built their model around lower distribution costs, so they bypassed GDS from the start. Most LCCs distribute through their own website (direct), through their own API to selected partners, or through aggregators that consolidate LCC content at lower cost than GDS. A few hybrid LCCs (like JetBlue, Southwest in some channels) do appear in GDS but with limited inventory.

Q: Which LCCs should I integrate first?

Pick by route share in your traveler markets. For India: IndiGo (~60 percent domestic share), SpiceJet, Akasa, and Air India Express. For SE Asia: AirAsia, Cebu Pacific, VietJet, Lion Air, Jetstar. For Europe: Ryanair, easyJet, Wizz Air, Vueling, Norwegian. For Middle East: Air Arabia, flydubai, SalamAir. Aggregators bundle most of these behind a single integration, which is the practical starting point unless one specific carrier dominates your routes.

Q: What ancillaries do LCCs sell through their APIs?

LCCs derive 25-40 percent of revenue from ancillaries, so the ancillary surface is rich. Standard items: checked baggage (multiple tiers), seat selection (with paid premium seats), meals, priority boarding, fast-track security, and travel insurance. Many LCCs also sell branded fare bundles (basic vs flex), cabin upgrades, hotel/car add-ons at booking time, in-flight WiFi packages, and carbon offsetting. Indian LCCs add web check-in, group bookings, and SpiceMax-type bundles. Capturing ancillary revenue is essential to LCC integration economics.

Q: How does fare-rule parsing work for LCCs?

LCC fare rules are less standardized than GDS fares. Each carrier exposes its own rule structure: change fees, no-show rules, refund eligibility, name-change handling, and ancillary refundability all vary by carrier and by branded-fare tier within the carrier. Integration requires per-carrier rule parsers that normalize the rules into a consistent platform model. The adivaha platform maintains these parsers centrally so portals do not write them per carrier.

Q: Direct LCC API or aggregator?

Aggregators (Travelfusion, Mystifly, TBO, Avia Solutions) cover dozens of LCCs through one integration. Per-transaction fees are slightly higher than direct, but engineering investment is dramatically lower. Most production portals start with an aggregator and add direct LCC integrations only when a specific carrier is critical to their route mix and the volume justifies the engineering. The adivaha platform sits one level above - we maintain aggregator and direct LCC connections so portals inherit coverage on connection.

Q: What payment routing patterns work for LCCs?

LCCs typically require payment at booking confirmation - no PNR-style hold available. Two payment routing patterns work in production. Pattern 1: traveler pays the portal via the portal's gateway, portal pays the LCC via credit-card pull or virtual card from the aggregator. Pattern 2 (LCC-direct in some integrations): traveler pays the LCC directly through a redirected checkout page. Pattern 1 is more common because it preserves the traveler relationship with the portal brand.

Q: How are LCC bookings serviced post-purchase?

Changes, cancellations, and add-ons happen through the same API surface. The LCC carrier owns the booking and the portal acts as the access channel. Change fees are passed through to the traveler (with the portal often adding a service fee on top). Cancellations follow the LCC's refund policy, which is often non-refundable for the base fare - the platform must handle the partial refund or insurance-driven full refund cases. Most LCC platforms expose modification APIs for date changes, name corrections (with carrier rules), and add-on additions after booking.

Q: How long does LCC integration take?

Through an aggregator: 2 to 6 weeks including sandbox testing and go-live. Direct LCC integration: 4 to 12 weeks per carrier depending on the carrier's API maturity and ancillary scope. Most production portals stick with aggregators for the long tail and integrate directly only with their highest-volume carriers. The adivaha platform reduces aggregator integration to 1 to 3 weeks because connections are centralized and tested.

Q: What does LCC integration cost?

adivaha LCC integration is included in the Standard plan at USD 99 per month (with USD 999 one-time setup) and the Standard plan at (included in Standard above) (no booking fees). Per-transaction fees vary by carrier and aggregator. Building LCC integration in-house through an aggregator typically costs USD 20K to USD 80K upfront plus ongoing maintenance. Direct LCC integration is significantly more expensive - typically USD 30K to USD 100K per major carrier.

LCC API integration connects a travel portal to low-cost carriers that distribute outside the traditional GDS rail. Low-cost carriers - IndiGo, AirAsia, Ryanair, Wizz, SpiceJet, Jetstar and dozens of others - operate on a no-frills, ancillary-revenue model and built their distribution around their own APIs and dedicated aggregators rather than GDS. For any portal serving routes where LCCs hold meaningful market share, LCC integration is not optional.

This page covers the commercial and technical patterns for LCC distribution: which carriers matter by region, how ancillaries and fare rules differ from GDS, direct-vs-aggregator routes, payment routing, and how the adivaha platform packages LCC integration for portal teams.

For the broader API architecture context, see our hub on the integration approach. For NDC content (richer airline-direct distribution), see NDC API integration. For GDS coverage, see the GDS walkthrough. For the commercial portal that bundles all three, see our hub on adivaha's platform.

Planning LCC integration for your portal?

Talk to our team for a 30-minute technical walkthrough: LCC supplier coverage in your priority markets, ancillary economics, and integration timelines.

Book a technical call

What Is LCC API Integration?

A low-cost carrier (LCC) operates on a model that maximizes operational efficiency and minimizes the unbundled base fare, then sells add-ons (baggage, seat selection, meals, priority boarding) as a-la-carte ancillaries. Examples include IndiGo, SpiceJet, AirAsia, Ryanair, Wizz Air, easyJet, Jetstar, Cebu Pacific, and many others.

Most LCCs do not distribute through traditional GDS channels because the per-booking GDS fee (USD 5 to 12) is large relative to the base fare. Instead, they distribute through their own websites, through direct APIs to selected partners, and through specialized aggregators (Travelfusion, Mystifly, TBO, Avia Solutions) that consolidate LCC content at much lower cost than GDS.

LCC API integration is the technical work of connecting a portal to these distribution channels and normalizing the content into a unified booking flow.

Why LCC Integration Matters

Three commercial reasons every flight-selling portal must integrate LCCs.

Market share. In many markets, LCCs hold 40 to 70 percent of route share. India: IndiGo alone holds around 60 percent domestic market share. Europe: Ryanair, easyJet, and Wizz together carry hundreds of millions of passengers a year. SE Asia: AirAsia and Lion Air dominate intra-region routes. A portal without LCC content shows travelers a thin and expensive view of those routes.

Ancillary economics. LCCs derive 25 to 40 percent of revenue from ancillaries. Portals that surface ancillaries at booking time capture a share of that revenue through service fees. Portals that only sell the base fare leave money on the table and (worse) push travelers to add ancillaries elsewhere, weakening the brand relationship.

Competitive parity. Travelers comparison-shop. A portal that consistently shows higher prices than competitors because it lacks LCC content loses share over time. LCC integration is table stakes, not a differentiator.

LCC Supplier Coverage by Region

Pick LCC integration priorities by your traveler-residency markets and route mix.

Region	Major LCCs	Notes
India	IndiGo, SpiceJet, Akasa, Air India Express	IndiGo alone ~60% domestic share. Direct APIs available; aggregators cover all four.
SE Asia	AirAsia, Cebu Pacific, VietJet, Lion Air, Jetstar, Scoot	AirAsia dominates intra-region. VietJet growing rapidly. Aggregators preferred for coverage.
Europe	Ryanair, easyJet, Wizz, Vueling, Norwegian, Eurowings	Largest LCC market globally. Ryanair restricts third-party API access; aggregators handle this.
Middle East	Air Arabia, flydubai, SalamAir, Jazeera	Growing market. Air Arabia largest. Most distribute through aggregators.
Americas	JetBlue, Frontier, Spirit, Volaris, Azul, GOL	Mixed - some distribute through GDS, some only direct. Hybrid coverage.
Africa	FlySafair, Mango (now defunct), Air Peace, Air Arabia Maroc	Smaller market. Some carriers GDS-distributed, others direct only.

For most portals, an aggregator (Travelfusion, Mystifly, TBO, Avia Solutions) covers 80-90 percent of the relevant LCCs through one integration. Direct integration becomes worth the engineering only when a specific carrier dominates your routes and the per-transaction savings justify the build.

Direct LCC API vs Aggregator

The decision shapes engineering investment and operational ongoing cost.

Aggregator route (recommended starting point)

Travelfusion is the largest LCC aggregator globally. Mystifly, TBO Holidays, and Avia Solutions are major alternatives, especially in Asia-Pacific. Each aggregator covers 50 to 150 LCC carriers through one integration. Per-transaction fees typically run USD 1 to USD 4 per booking on top of the carrier's direct cost.

Pros: one integration covers many carriers; aggregator handles certification and ongoing maintenance; fares and ancillary metadata normalized across carriers; faster time to market. Cons: slightly higher per-booking cost; less granular control over rate-shopping; some carrier-specific features may not surface through the aggregator.

Direct LCC route (for high-volume carriers)

Engineer directly to a carrier's API. Saves the aggregator fee but requires per-carrier integration, certification, and ongoing maintenance.

Pros: lower per-booking cost (often USD 1-2 saved per transaction); access to the carrier's full content including loyalty integration and premium ancillaries; direct relationship for issue escalation. Cons: 4-12 weeks engineering per carrier; ongoing maintenance burden as the carrier evolves its API; supplier-management overhead.

The hybrid that wins in practice

Most mature portals run a hybrid: aggregator for the long tail of LCCs (50-100 carriers), direct for the 1-3 carriers that dominate route share. This minimizes engineering investment while capturing the per-booking economics on high-volume routes.

Ancillary Handling Patterns

Ancillary integration is the most complex part of LCC engineering and the most commercially important.

Offer-time vs post-booking

Some LCCs expose ancillaries at offer time (the traveler picks bags and seats during checkout). Others expose them only post-booking (the traveler completes the base fare, then sees an "add to your trip" page). Mature integrations support both flows seamlessly, with the carrier dictating the model.

Carrier-specific ancillary catalog

Each LCC has its own ancillary catalog with carrier-specific naming and pricing. The platform must normalize these into a consistent traveler-facing catalog while preserving carrier-specific rules. For example, "Cabin Bag" on Ryanair, "Carry-On" on Spirit, and "Hand Baggage" on AirAsia mean different things with different sizes and weights.

Ancillary refundability

Most LCC ancillaries are non-refundable. Some specific add-ons (like seat selection on certain carriers) are refundable on cancellation. The platform must track ancillary refundability per item and apply correctly during the cancellation workflow.

Payment Routing for LCCs

LCCs require payment at booking confirmation - there is no PNR-style hold pattern available. Two production routing patterns.

Portal-pays-carrier (most common)

The traveler pays the portal through the portal's payment gateway. The portal pays the carrier through credit-card pull (the carrier charges a portal-owned card) or via virtual card issued at booking time (the aggregator provides a single-use virtual card). The traveler relationship stays with the portal brand. Reconciliation runs through the portal's books.

Carrier-direct payment (less common)

The portal redirects the traveler to the carrier's checkout page for payment. Simpler to integrate but the traveler interacts with the carrier brand at the moment of purchase, weakening the portal relationship. Some aggregators do not support this pattern.

Multi-currency considerations

LCCs often price in carrier-base currency (EUR for Wizz, USD for AirAsia long-haul, INR for IndiGo). Portals serving travelers in different currencies must FX-convert at display and confirmation, with a small buffer for FX movement between booking and settlement.

Pricing and Plans

adivaha LCC integration is included in our two standard plans plus a custom tier.

Standard: USD 999 setup + USD 99/month

Full LCC integration coverage across India, SE Asia, Europe, Middle East, Americas, and Africa through Travelfusion, Mystifly, TBO, and Avia Solutions. Direct integrations to the largest 8 carriers globally. Sandbox access, REST/JSON documentation, ancillary support, multi-currency. 7-day free trial. See full pricing.

Custom (enterprise scope)

Same LCC coverage as Monthly, billed annually. Includes the B2B sub-agent module for portals running agent networks. Saves USD 789 a year.

Custom

For portals needing direct integration to specific LCCs beyond our standard roster, custom ancillary surfacing, or enterprise SLA terms. Talk to sales for scoping.

Sandbox and Documentation

All plans include sandbox access for LCC integration testing. Sandbox covers the major aggregators and direct-LCC endpoints with test bookings, ancillary purchases, and end-to-end reconciliation traces. API documentation at docs.adivaha.com with REST/JSON examples, Postman collection, and per-carrier integration notes.

Why adivaha for LCC Integration

Three reasons portals choose adivaha for LCC integration.

Aggregator coverage in one place. Travelfusion, Mystifly, TBO, Avia Solutions - and direct integrations to the largest LCC carriers - all behind a single connector. Your engineering team writes one integration.

Production-grade ancillary handling. Carrier-specific catalog normalization, offer-time and post-booking ancillary flows, refundability tracking - all production-tested across hundreds of portal deployments. Your team skips the operational learning curve.

Mature operations. Refund workflows, supplier-side reconciliation, change-fee handling, and chargeback processes are baked into the platform. You inherit the operational maturity on connection.

FAQs

Q1. What is LCC API integration?

LCC stands for Low-Cost Carrier - airlines on a no-frills, ancillary-revenue model. LCC API integration connects portals to these carriers, which distribute outside traditional GDS through direct APIs or aggregators like Travelfusion, Mystifly, and TBO.

Q2. Why don't LCCs distribute through GDS?

GDS costs (USD 5-12 per booking) are too high relative to LCC base fares. LCCs built their model around lower distribution costs, distributing through their own website, direct APIs to partners, or specialized aggregators.

Q3. Which LCCs should I integrate first?

Pick by route share in your traveler markets. India: IndiGo, SpiceJet, Akasa. SE Asia: AirAsia, Cebu Pacific, VietJet. Europe: Ryanair, easyJet, Wizz. Middle East: Air Arabia, flydubai. Aggregators bundle most.

Q4. What ancillaries do LCCs sell through their APIs?

Standard: baggage, seat selection, meals, priority boarding, fast-track security, insurance. Many add branded fare bundles, cabin upgrades, hotel/car add-ons at booking, WiFi, carbon offset. Ancillaries = 25-40% of LCC revenue.

Q5. How does fare-rule parsing work for LCCs?

Per-carrier rule parsers required because LCC fare rules are less standardized than GDS. Each carrier exposes its own rule structure for change fees, refund eligibility, name changes, and ancillary refundability. adivaha maintains parsers centrally.

Q6. Direct LCC API or aggregator?

Aggregators cover dozens of LCCs through one integration. Slightly higher per-transaction cost but dramatically lower engineering investment. Most portals start with an aggregator and add direct integration only for top-volume carriers.

Q7. What payment routing patterns work for LCCs?

Portal-pays-carrier (most common): traveler pays portal, portal pays carrier via credit-card pull or virtual card. Carrier-direct (less common): traveler pays carrier directly via redirect. Pattern 1 preserves traveler-portal brand relationship.

Q8. How are LCC bookings serviced post-purchase?

Through the same API surface. Carrier owns the booking; portal acts as access channel. Change fees pass through; cancellations follow carrier policy. Most LCCs expose modification APIs for date changes, name corrections, and post-booking add-ons.

Q9. How long does LCC integration take?

Aggregator: 2-6 weeks. Direct LCC: 4-12 weeks per carrier. Production portals stick with aggregators for the long tail and integrate directly only for top carriers. adivaha reduces aggregator integration to 1-3 weeks.

Q10. What does LCC integration cost?

adivaha LCC is included in the Standard plan at USD 99/month (with USD 999 one-time setup) and Annual at (included in Standard above). Per-transaction fees vary by carrier. Building in-house through an aggregator: USD 20K-80K upfront. Direct LCC: USD 30K-100K per carrier.