Services · APIs
Multi-supplier travel API: aggregation done in the core, not your app
Two suppliers double your content and quadruple your edge cases. The same flight returns at two prices, one source times out, another changes its schema. A multi-supplier travel API moves aggregation, de-duplication and failure handling into one core so your product sees a single, consistent inventory.
Built for
- OTAs
- Super-apps
- Consolidators
- Tour operators
- Travel startups
In brief
What is a multi-supplier travel API?
A multi-supplier travel API is one interface that queries many travel content sources at once and returns merged, comparable results. Voraal's Avunzo aggregates Amadeus, Sabre and Travelport, NDC airlines, low-cost carriers, hotel aggregators, bedbanks, direct chains, transfers, car rental and activities through one schema, with parallel supplier calls, caching, and markups and filters set per channel.
By the Voraal team · Updated
Why aggregation belongs below your product
Every source added to a booking product brings a contract, a data format and a set of behaviours under load. If aggregation lives in your application, each new source touches search, pricing, booking and customer service code. A multi-supplier travel API puts the fan-out, merging and supplier-specific quirks in one place. Your product deals with one inventory.
In Voraal's architecture, suppliers connect to the core once and become available across Rezencia, Avunzo and Folio6. Avunzo is the API surface of that core. If your challenge is specifically airline content from several channels, airline content aggregation goes deeper on air.
How a multi-supplier request is processed
- 01
Pick the sources
Not every source is relevant to every request. Routing considers product, market and channel rules so you are not paying look-to-book on sources that cannot answer.
- 02
Call in parallel with a budget
Sources are queried at the same time. A response budget stops one slow supplier from holding the whole result back.
- 03
Normalise each response
Every supplier's answer is mapped into the same schema: one flight model, one property and rate model, one ground-service model.
- 04
De-duplicate and choose
Where the same flight or hotel arrives from more than one source, results are merged so customers compare offers for the same product.
- 05
Apply your rules
Markups and filters for the calling channel are applied, then results return in one response.
When the same product arrives from two sources
De-duplication decides what your customer sees. These are the questions an aggregation layer has to answer.
| Situation | Question to answer | Typical approach |
|---|---|---|
| Same flight via a GDS and via the airline's NDC | Are these the same fare and conditions? | Compare fare brand and conditions, not just flight number and price |
| Same hotel via two aggregators | Is this the same property and room? | Map to one property; keep rates separate so conditions stay visible |
| Same transfer route from two providers | Same vehicle class and inclusions? | Normalise vehicle class and waiting-time terms before comparing |
| One source times out | Show partial results or wait? | Return within budget; never show a booking path for a missing offer |
Key features
Many sources, one schema
Flights, hotels, cars, transfers, activities and packages in a single data model.
Parallel supplier calls
Caching and parallel calls tuned for search-heavy traffic.
Merged results
GDS, NDC and low-cost results come back in one response, sorted and priced the same way.
Channel rules
Markups and filters set per channel.
Your agreements or Voraal's
In many cases your own supplier credentials sit alongside Voraal-provided content.
Margin by supplier
Folio6 shows supplier cost and margin, with margin-leak detection by route, supplier and agent.
Business applications
A super-app wants flights, hotels and airport transfers without negotiating each one. A tour operator builds dynamic packages across air, stays and activities. A consolidator compares the same fare across its own GDS accounts and Voraal content; multi-GDS integration covers running Amadeus, Sabre and Travelport together. Teams evaluating several aggregators can use the travel API providers comparison to structure their evaluation.
Implementation process
- 01
Map your content needs
List products and markets. Supplier coverage per product is confirmed during discovery.
- 02
Decide on agreements
Choose which sources run on Voraal's agreements and which on your own credentials.
- 03
Configure channel rules
Set markups and filters for each channel or partner before testing.
- 04
Test across sources
In the sandbox, test results where the same product arrives from more than one source, as well as booking on each source type.
Common challenges
Hidden differences
Two offers with the same price can have different baggage, refund or change rules. Show conditions, not just price.
Uneven source performance
Supplier response times vary by hour and season. Response budgets protect the user experience.
Supplier change
Suppliers update protocols and retire versions. In a unified core, Voraal absorbs that change rather than your engineers.
Reconciliation across sources
More sources mean more statements. Supplier ledgers and reconciliation keep cost and booking in step.
How Voraal delivers this
The products behind it.
Which suppliers are behind the multi-supplier API?
For air: Amadeus, Sabre and Travelport GDS, NDC airline connections and low-cost carriers. For stays: hotel aggregators, bedbanks and direct chain connections. Ground and experiences: transfers, car rental, activities and tours. Coverage for your markets is confirmed during discovery.
Do we pay each supplier separately?
With Avunzo you have one commercial agreement, one data model and one support line, with usage-based pricing. If you connect your own supplier credentials, your existing commercial terms with that supplier continue.
What happens if one supplier is down?
Other sources still answer, because calls run in parallel within a response budget. Offers from the unavailable source are simply absent from that response rather than shown and failing at booking.
Can we exclude a supplier for one of our channels?
Yes. Filters and markups are set per channel, so a partner or app can see a different subset of content and pricing from the same account.
How do we know which supplier is most profitable?
Folio6 reports supplier cost and margin in real time and flags margin leaks by route, supplier and agent.
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.