Skip to content
Voraal

Guide · Flight content

Flight booking API or a direct GDS connection: which one should your travel business build on?

When a business decides to sell flights online, the first architecture question is where the content comes from. One route is a direct contract and integration with a GDS. The other is a flight booking API from an aggregator that has already connected GDS, NDC and low-cost sources. This guide compares the two on the things that decide success: who you contract with, who issues tickets, what content you get, what it costs and who services the booking.

Built for

  • OTA and app founders
  • Banks, wallets and super-apps
  • Agencies planning IATA accreditation
  • Corporate booking tool builders
  • CTOs

Short answer

Should you use a flight booking API or connect directly to a GDS?

Use a flight booking API if you want broad content (GDS, NDC and low-cost carriers) quickly, do not hold IATA accreditation or want to avoid multiple certifications. Connect directly to a GDS when you are accredited, have the volume to earn incentives and want full control of ticketing and servicing. Many growing sellers combine both; Voraal's Avunzo API and Rezencia platform support either path.

By the Voraal team · Updated · 7 min read

What does a direct GDS connection involve?

A commercial contract, an office identity, an integration project and certification. You sign an agreement with Amadeus, Sabre or Travelport for your market, which assigns you an office ID or pseudo city code and sets incentive and fee terms, often linked to segment volume. Your developers integrate the GDS's web services, and the GDS certifies the integration before production access. To issue tickets yourself on BSP, you also need IATA accreditation.

In return you get the GDS's full breadth of full-service carrier content, your own private fares loaded against your office, terminal access for your ticketing team, and GDS incentives on qualifying segments. You also take on the work: maintaining the integration through version changes, handling queues, and servicing every booking.

The barriers for small developers have recently risen. Amadeus closed the self-service section of its developer portal in July 2026, disabling self-service API keys; enterprise customers continue on its enterprise APIs. Startups that relied on that free tier now need either an enterprise agreement or an aggregator.

What does a flight booking API give you instead?

One integration to several sources, with someone else holding the supplier contracts. A flight booking API provider connects to one or more GDSs, NDC airlines and low-cost carriers, normalises their responses into one data model and exposes search, pricing, booking, ticketing and servicing through a single REST or JSON interface. Depending on the provider, it may also act as the ticketing entity, so you can sell without your own IATA accreditation.

The trade-offs are less control over some servicing actions, the provider's fees or markup on top of net fares, and dependence on the provider's coverage and uptime. Check carefully which content is live, how ticketing and settlement work in your currency, and which post-booking actions the API exposes. Our flight booking API page lists the questions we think every buyer should ask.

Flight booking API vs direct GDS: how do they compare?

FactorFlight booking API (aggregator)Direct GDS connection
ContractWith the API providerWith each GDS, per market
Accreditation neededOften none; provider may ticket on its own accreditationIATA accreditation to ticket on BSP yourself
Content breadthGDS plus NDC plus low-cost carriers, depending on providerThat GDS's content; NDC only where the GDS supports it
Low-cost carriersCommonly included via direct LCC connectionsLimited; many LCCs are thin or absent in GDS
Integration effortOne API, one sandboxPer-GDS integration and certification
Time to first bookingShorter — no certification of your ownLonger — contract, build, certification
Pricing to youUsage-based fees or markup on net faresSegment-linked fees and incentives under your GDS contract
Private and negotiated faresProvider's fares, or your own if it supports loading themYour own fares on your office ID
Ticketing controlThrough provider's rules and hoursFull control, including terminal entries
ServicingAs exposed by the API; check refunds and reissuesFull GDS servicing, by your own team
Maintenance burdenProvider maintains supplier changesYou maintain your integration

Which option fits which business?

A decision matrix based on the situations we see most often.

Business situationRecommended startWhyRevisit when
New OTA without IATA accreditationFlight booking APIBreadth and ticketing without accreditation or certificationMonthly ticket volume justifies own accreditation
Bank, wallet or super-app adding flightsFlight booking APINo travel operations team; needs normalised data and servicingRarely — keep focus on customers
IATA agency with in-house ticketing teamDirect GDS plus API for NDC and LCCKeeps incentives and control; fills content gapsWhen NDC share on key airlines grows
Consolidator selling to sub-agentsDirect multi-GDS plus NDC and LCC via API or directNeeds private fares, incentives and full servicingWhen adding new markets or carriers
Corporate booking toolFlight booking API, or TMC's GDS via APIPolicy and approval logic matter more than source controlWhen TMC relationship changes

Why do low-cost carriers change the calculation?

Because they are often thin or absent in the GDS. CAPA notes that GDSs pay much lower rates for low-cost carrier segments, so agents earn little or nothing from GDSs on those bookings, and many low-cost airlines prefer their own direct or API channels. If your customers fly regional low-cost carriers — common on Gulf and domestic routes from Pakistan — a GDS-only strategy will miss fares. A flight API with direct LCC connections, or your own low-cost carrier integration, fills that gap.

How do businesses typically move from API to direct GDS?

A common path for a Pakistani OTA or agency that grows into an IATA ticketing business:

  1. 01

    Launch on a flight booking API

    Sell with broad content and the provider's ticketing, focusing engineering on the customer experience.

  2. 02

    Obtain IATA accreditation

    Once trading history, audited accounts and volume support it, apply for the accreditation model that fits your payment mix.

  3. 03

    Sign a GDS contract

    Negotiate terms and incentives based on your volume, and get your own office ID for private fares.

  4. 04

    Route full-service content directly

    Move ticketing for carriers where direct GDS gives better margin to your own office, through a platform that supports rule-based routing by airline.

  5. 05

    Keep the API for gaps

    Retain NDC and low-cost content through the API where direct connections are not worth building. Reconcile both sources in the same back office.

What hidden costs differ between the two?

With a direct GDS, the hidden costs are people and maintenance: developers to keep the integration current, a ticketing team to work queues and service bookings, and the capital tied up in an IATA financial guarantee. With an API, the hidden costs are usage fees at scale, look-to-book limits and any markup on net fares. Published aggregator pricing shows the shape of this: Duffel, for instance, lists a fixed fee per order, a percentage for managed content, a fee per paid ancillary and an excess-search charge. Model both at your year-two volume before committing; see our guide on travel agency software cost for a worksheet.

What should you test before committing to either route?

Test the bookings you actually sell, not a generic demo route. Pick your ten most common itineraries — for a Pakistani seller that might include Gulf, UK, Saudi and domestic routes — and compare search results, prices and response times through the API and through a GDS terminal on the same day. Then book, ticket, void, change and refund at least one real low-value ticket through the route you are considering, and check that every step appears correctly in your back office and on the supplier statement.

Also test what happens when something fails: a supplier timeout during booking, a payment that succeeds when ticketing does not, and a schedule change on a booking made through the API. How quickly the provider or your own team can recover in those cases is a better predictor of customer experience than search speed.

How Voraal fits

Voraal supports both routes on one core. Avunzo is a unified REST/JSON flight and travel API covering Amadeus, Sabre, Travelport, NDC airlines and low-cost carriers, with sandbox, OpenAPI specification, webhooks and usage-based pricing. Rezencia lets accredited agencies and consolidators run their own GDS offices (see Sabre integration) with rule-based ticketing that decides which GDS issues per airline, while still using aggregated NDC and LCC content. For Pakistani buyers, the flight booking API provider page for Pakistan covers local considerations.

Key takeaways

  • A direct GDS requires a contract, office ID, certification and usually IATA accreditation.
  • A flight booking API gives GDS, NDC and LCC content through one integration, often with the provider ticketing.
  • Confirm who is the ticketing entity, merchant of record and refund party.
  • Low-cost carriers are often missing from GDS-only strategies.
  • Self-service GDS developer access has narrowed; plan for enterprise or aggregator access.
  • Many businesses start on an API and add direct GDS as volume and accreditation allow.
  • Model costs at year-two volume, including people and maintenance.

FAQ

Frequently asked questions

Questions buyers ask about flight booking api vs direct gds.

Ask us anything
  • Can I sell flights through an API without IATA accreditation?

    Often yes, if the API provider or a consolidator behind it issues tickets on its own accreditation. You still need your local travel-agency licence and clear terms on who handles payment and refunds.

  • What is a GDS office ID or pseudo city code?

    It is the identifier a GDS assigns to your agency location. Bookings, private fares, queues and ticketing authority are attached to it, which is why moving from an API to your own GDS gives you more control.

  • Do flight booking APIs support refunds and reissues?

    Good ones do, but coverage varies by provider and by source, especially for NDC and low-cost carriers. Ask for documented servicing endpoints and test a real refund and reissue in the sandbox.

  • Is a flight booking API slower than a direct GDS connection?

    Not necessarily. An aggregator adds a hop, but it may call several sources in parallel and cache intelligently. Measure response times on your own routes rather than relying on assumptions.

  • Can I use my own negotiated fares through a flight booking API?

    Some providers let you load or attach your own private fares or office IDs; others only sell their own contracted content. If negotiated fares are central to your business, make this a selection criterion.

  • What happened to the Amadeus self-service APIs?

    Amadeus decommissioned the self-service section of its developer portal in July 2026 and disabled those API keys. Enterprise APIs continue for contracted customers. Developers who relied on the self-service tier need an enterprise agreement or an alternative provider.

Let’s build what comes next.

Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.

WhatsApp