Comparison · Travel APIs
Comparing travel API providers: GDS, aggregators, wholesalers and unified APIs
Developers building a travel product have more API options than ever, and fewer of them do the same thing than their marketing suggests. Some provide airline content through a GDS, some aggregate low-cost and NDC carriers, some sell hotel and ground inventory, and some put several of these behind one schema. This comparison helps a product or engineering team decide which type to integrate, using only published facts about named providers.
Built for
- CTOs and engineering leads
- Product managers at OTAs
- Fintech and super-app teams
- Corporate booking tool builders
- Travel startups
Short answer
How do travel API providers compare?
Travel API providers differ by type: GDS APIs give airline content but need commercial agreements and certification; flight aggregators bundle low-cost and NDC airlines; hotel and activity wholesalers supply ground inventory; unified APIs normalise several sources in one schema. Compare content, pricing model, ticketing authority, sandbox access and post-booking coverage. Voraal's Avunzo is a unified REST API for flights, hotels, transfers, cars, activities and packages, priced on usage.
By the Voraal team · Updated · 6 min read
Four types of travel API provider
GDS APIs. Amadeus, Sabre and Travelport offer airline shopping, booking and ticketing to agencies and technology partners under commercial agreements. Access usually involves a contract, a pseudo city or office set-up, and certification of your integration. The differences between GDS and airline-direct NDC distribution are explained in our GDS vs NDC guide.
Flight aggregators. These companies connect many airlines, often including low-cost and NDC carriers, and expose them through one flight API. Some include ticketing on their own accreditation.
Hotel, activity and transfer wholesalers. Bedbanks and wholesalers provide accommodation and ground services through their own APIs, usually with an evaluation or certification process before live bookings.
Unified APIs. These place several content types and suppliers behind one schema, so a developer integrates once for flights, stays and ground services.
Named providers, as published
Each description below is drawn from the provider's own pages, as published, checked November 2026, except where a news source is cited for a change of service. These are examples, not a ranking, and figures are the providers' own statements.
Duffel (flight aggregator with published pricing)
Duffel's pricing page lists, for flights, USD 3.00 per confirmed order, 1% of order value for managed content, USD 2.00 per paid ancillary and USD 0.005 per excess search beyond a 1,500:1 search-to-book ratio, plus a 2% charge on the exchange rate where currency conversion is needed. Its pay-as-you-go plan states no up-front fees; an enterprise plan offers bespoke pricing and the option to use your own IATA accreditation. Stays are priced on a profit-share basis.
Travelfusion (content aggregator)
Travelfusion describes itself as a travel content aggregator serving OTAs, TMCs and online booking tools, and reports more than 400 low-cost carriers and over 70 NDC carrier integrations, along with rail and hotel content. Its named APIs include tfFlight, tfRail and tfHotel. Pricing is not published on its corporate site.
Hotelbeds (hotel and ground wholesaler)
Hotelbeds' developer portal presents an API Suite for hotels, activities, transfers and car rental. Its stated process is to register for a free API key with access to an evaluation plan, complete a profile so commercial needs can be assessed, test in a sandbox and get the XML integration certified with its API team.
Amadeus Self-Service APIs (discontinued)
Amadeus ran a self-service developer portal for smaller teams. PhocusWire reported in early 2026 that Amadeus would pause new registrations and fully decommission the self-service portal on 17 July 2026, with API keys disabled, while its Enterprise APIs continue through the Amadeus Enterprise portal. Teams that built on the self-service tier have had to migrate to an enterprise agreement or another provider.
Comparison criteria for travel APIs
Score each candidate on these criteria with your engineers after a sandbox trial.
| Criterion | What to verify | Common trap |
|---|---|---|
| Content coverage | Exact airlines, hotel sources and ground services for your markets | Global supplier counts that say little about your routes |
| Normalisation | One schema across suppliers for offers, orders, fare rules and baggage | Each supplier's quirks leaking into your code |
| Ticketing authority | Whose accreditation issues tickets: yours or the provider's | Discovering late that you need your own arrangement |
| Post-booking coverage | Changes, cancellations, refunds and reissues via API, not by email | APIs that stop at 'book' |
| Pricing model | Per order, per segment, percentage, search fees, FX charges | Search-to-book penalties at scale |
| Developer experience | Sandbox, OpenAPI specification, webhooks, versioning, scoped keys | Test data that bears no resemblance to production |
| Settlement currency | Ability to settle and invoice in your currency, including PKR | Silent FX margins on every order |
| Support and continuity | Named integration engineer; notice periods for changes | Self-service tiers withdrawn at short notice |
Pricing models you will meet
This describes structures, not any provider's figures beyond those quoted above.
| Model | How it is charged | Watch for |
|---|---|---|
| Per order or per booking | Fixed fee per confirmed booking | Separate fees for ancillaries or changes |
| Percentage of value | Share of the order value | Cost rising with fares rather than effort |
| Search fees | Charges above a look-to-book threshold | Metasearch or price-alert traffic |
| Profit share or net rates | Margin built into the rate (common for hotels) | Rate parity and markup limits |
| Usage tiers | Volume bands with lower unit prices | Minimum commitments |
| Subscription or licence | Fixed monthly or annual fee | What happens if usage falls |
Where Avunzo fits
Avunzo, Voraal's unified travel API, is a single REST/JSON integration for flights from Amadeus, Sabre, Travelport, NDC airlines and low-cost carriers, together with hotels, transfers, car rental, activities and dynamic packages. Approved teams get sandbox keys, test data and an OpenAPI specification; the API supports webhooks, versioning and scoped credentials, and uses caching and parallel supplier calls. Pricing is usage-based with volume tiers, quoted on the products and traffic you expect. Depending on supplier and commercial set-up, it can run on Voraal's agreements or on your own credentials.
Two things set it apart in this list. It runs on the same supplier connections as Rezencia, so a business can launch a ready-made platform and an API-driven app on one core. And because Folio6 reads the same bookings, revenue and margin by supplier are visible without building a reporting pipeline. Developers can start with the travel API for developers page or the flight booking API service.
Which provider type suits which builder
A starting point for the shortlist; your own volumes and contracts may change the answer.
| You are building | Usually start with | Add later if needed |
|---|---|---|
| A flight-only OTA or metasearch-to-book site | A flight aggregator or unified API | Direct GDS agreement at scale |
| A hotel and holiday site | Hotel wholesaler APIs or a unified API | Direct chain connections |
| A corporate booking tool | A unified API with policy filtering | Your own GDS credentials for negotiated fares |
| Travel inside a wallet or super-app | A unified API covering flights, hotels and ground | Packages and ancillaries |
| A B2B network for agents | A ready platform rather than a raw API | An API for your largest partners |
For corporate and fintech use cases, see the corporate travel and fintech pages in the related links.
Sandbox test plan before you sign
- Search, price, book and cancel one flight on a low-cost carrier and one via GDS.
- Request a fare rule and baggage allowance and check they are structured, not free text only.
- Change a booked flight and confirm the API returns the fare difference and penalty.
- Book and cancel a hotel and check the cancellation policy returned at search matches the one at booking.
- Subscribe to a webhook and trigger a schedule change in test.
- Model your monthly cost at today's volume and at three times today's searches.
How Voraal delivers this
The product behind it.
FAQ
Frequently asked questions
Questions buyers ask about travel api providers comparison.
Ask us anythingIs a flight aggregator API cheaper than a direct GDS connection?
It depends on volume and set-up. Aggregators often reduce up-front work and contracts, while direct GDS agreements can suit high-volume sellers with their own accreditation. Model both on your expected bookings and searches.
Do I need IATA accreditation to use a travel API?
Not always. Some providers issue tickets on their own accreditation; others require yours. Hotels and ground services generally do not need IATA accreditation. Confirm whose authority issues tickets before you design your payment flow.
What replaced the Amadeus self-service APIs?
Amadeus said Enterprise APIs continue through its Enterprise portal. Teams on the closed self-service tier have moved to enterprise agreements, flight aggregators or unified APIs, depending on volume and needs.
Should I integrate several APIs or one unified API?
Several direct APIs give control but multiply mapping, certification and maintenance work. A unified API reduces integration work in exchange for depending on one provider. Many teams start unified and add a direct connection where volume justifies it.
How long should we budget to switch travel API providers?
A focused flight search-to-ticket integration can take a few weeks with a good sandbox; adding hotels, changes and refunds takes longer. Certification steps set by suppliers often decide the final date.
Sources and further reading
- Duffel pricing (as published, checked November 2026)
- Travelfusion corporate site (as published, checked November 2026)
- Hotelbeds developer portal (as published, checked November 2026)
- PhocusWire: Amadeus to shut down self-service APIs portal
Regulations, airline programmes and supplier terms change. Confirm requirements with the relevant authority or supplier before acting. Contact [email protected] if you spot something out of date.
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.