Meet us at ATM Dubai | Booth TT2019
DWTC, Dubai
17 – 20 Aug 2026
DWTC, Dubai
17 – 20 Aug 2026
Table of Contents
2 million+ properties. Exclusive APAC inventory. The supplier your competitors are using to win Asian travel markets — and ZentrumHub already has it live inside Zentrum Connect.
If your OTA serves — or wants to serve — travellers booking hotels in Asia, Agoda is not optional. It is the dominant hotel booking platform across Southeast Asia, East Asia, and South Asia, and its B2B inventory contains properties, rate types, and local content that simply do not appear in any Western bedbank feed. The Agoda Hotel API is how OTAs and travel platforms access that inventory programmatically — and the gap it fills in your supplier stack is significant.
This guide covers exactly what Agoda’s B2B API delivers, what makes its APAC inventory genuinely different, how the commission model works, the real access requirements — and precisely how ZentrumHub activates Agoda inside a single hotel inventory feed for OTAs.
Agoda is a leading online travel agency headquartered in Bangkok, Thailand, founded in 2005 and acquired by Booking Holdings (formerly Priceline Group) in 2007. It operates as the dominant hotel booking platform across Southeast Asia, East Asia, and South Asia — and unlike Expedia or Booking.com, Agoda’s inventory depth in APAC markets is genuinely unmatched. Properties that exist in Agoda’s database simply do not appear in most Western bedbank feeds.
What makes Agoda Hotel API strategically important is not just volume — it is exclusivity. Agoda has direct contracts with hundreds of thousands of APAC properties that have never listed on Hotelbeds, Expedia, or RateHawk. Agoda processes tens of millions of hotel bookings annually across Asia, giving it rate leverage and property relationships no other supplier can replicate in that region.
Agoda Hotel API is the B2B programmatic interface that gives approved travel businesses — OTAs, booking portals, travel agencies — access to Agoda’s 2M+ property database for hotel search, availability checking, booking, and cancellation. It is operated by Agoda Company Pte. Ltd., a subsidiary of Booking Holdings (NASDAQ: BKNG).
One important nuance: Agoda is simultaneously your competitor (it sells hotels to consumers on agoda.com) and your supplier (it gives OTAs access to its inventory via B2B API). This dual role is common in travel distribution — Expedia operates the same way. Understanding it matters because Agoda’s consumer rates sometimes undercut what B2B partners can offer, which has direct implications for your pricing strategy.
With 2 million+ properties, Agoda hotel inventory is one of the largest in the world by raw count. But the number that matters more is the proportion of that inventory that is genuinely exclusive — properties with Agoda-direct contracts that don’t appear in any other supplier feed your OTA is likely already using.
If a traveller searches for a budget guesthouse in Chiang Mai, a traditional Ryokan in Kyoto, or a villa in Seminyak — and your OTA doesn’t have Agoda hotel API connected — your search results will be visibly thinner than competitors who do. This is not a marginal difference. In APAC leisure travel, Agoda’s exclusive inventory is often the deciding factor in whether a traveller books with you or goes elsewhere.
Agoda operates three distinct B2B programmes. OTAs need to understand which one applies to them — because the Agoda YCS system that hotels use to manage their own distribution is frequently confused with the OTA-facing API:
The B2B API for OTAs and travel agencies wanting to resell Agoda inventory. Standard hotel search, availability, book, and cancel flows. Commission-based model. This is what OTAs integrate.
Agoda’s “Your Channel Manager System” — used by hotels to manage their rates and availability distributed TO Agoda. This is a supply-side tool for hoteliers, not relevant for OTA API buyers.
Corporate travel programme with negotiated rates for SME and enterprise business travel. Relevant for TMCs and corporate travel platforms targeting Asian business traveller segments.
The Agoda hotel API uses a standard REST/JSON architecture with API Key authentication — simpler than Amadeus OAuth but requires direct partner approval before credentials are issued. Here are the core technical details:
| Endpoint Group | Function | Notes |
|---|---|---|
| Hotel Search | Search by location, geo-coordinates, or property ID | Returns availability, rates, room types for given dates |
| Property Details | Hotel static content — name, address, images, amenities | Separate content feed available for bulk pre-loading |
| Availability Check | Real-time rate and room availability confirmation | Required step before booking to confirm current price |
| Booking | Creates hotel reservation, returns booking reference | Requires guest details, payment token, rate token |
| Cancellation | Cancels booking per property cancellation policy | Free cancellation window varies by property and rate |
| Content Feed | Bulk hotel content download for local database caching | Recommended for performance — avoids real-time content calls |
Agoda’s B2B API access is not self-serve — unlike Amadeus’s developer portal or Expedia’s partner application form, Agoda requires direct engagement with its business development team. Here is how the access and commercial model works:
Like Expedia Collect, Agoda’s commission is paid post-stay. For a hotel booking made 2 months in advance, your commission arrives 2+ months after the guest checks out — potentially 3–4 months from when the booking was made. For OTAs with significant APAC volume, this creates a substantial working capital gap. Factor this into your financial model before scaling Agoda bookings aggressively.
Agoda’s value proposition is clear — but so are its limitations outside APAC. Here is how it compares against the other major hotel supplier APIs across the dimensions that matter for OTA decision-making:
| Factor | Agoda | Expedia Rapid | Hotelbeds | Amadeus | RateHawk |
|---|---|---|---|---|---|
| Properties | 2M+ | 700K+ | 250K+ | 150K+ | 2.5M+ |
| Rate Model | Commission (12–18%) | Net + Commission | Net wholesale | GDS + corporate | Net only |
| APAC Coverage | Dominant — #1 | Moderate | Limited | Chain hotels only | Growing |
| Auth Method | API Key | API Key + Secret | API Key | OAuth 2.0 | API Key + HMAC |
| Exclusive Inventory | High — APAC exclusives | Moderate | Moderate | Corporate rates | Low |
| Self-Serve Access | No — BD required | No — apply online | No — apply online | Yes — developer portal | No — apply online |
| Key Differentiator | APAC exclusives + volume | Global + dual payment | Leisure rate depth | Corporate rates | Widest coverage |
The Agoda hotel API integration has specific challenges that OTAs consistently encounter. Here are the most common — and the practical fixes:
ZentrumHub is a hotel API integration provider and travel technology company. The Agoda hotel API is already built, tested, and maintained inside Zentrum Connect — alongside 100+ other hotel suppliers including Expedia, Amadeus, Hotelbeds, RateHawk, and Priceline. See the Agoda API integration with ZentrumHub for full details on how activation works.
The model is direct: OTAs that have a commercial agreement with Agoda bring their supplier contract to ZentrumHub. ZentrumHub activates it inside Zentrum Connect — and it immediately becomes part of your combined hotel inventory feed. No separate Agoda integration build. No property ID mapping work on your side. No deduplication engineering. Your booking engine receives one unified, normalised feed — Agoda’s 2M+ APAC properties combined with every other supplier you have enabled.
OTAs that don’t yet have a direct commercial agreement with Agoda can still access Agoda inventory through ZentrumHub’s existing supplier relationships — subject to commercial terms. This is particularly useful for smaller OTAs and startups that don’t yet meet Agoda’s direct partner volume thresholds. Connect via Hotel Supplier Connect or view the full list of hotel suppliers available via ZentrumHub.
ZentrumHub activates your Agoda supplier agreement inside Zentrum Connect — combining it with 100+ other hotel suppliers in one deduplicated inventory feed.
Talk to Our Integration Team →ZentrumHub combines Agoda, Expedia, Amadeus, Hotelbeds, RateHawk and 95+ more suppliers into one hotel inventory feed — with real-time deduplication, sub-500ms response, and direct activation inside your booking engine. 3M+ room nights booked. $650M+ in revenue generated for clients.
