Meet us at ATM Dubai | Booth TT2019
DWTC, Dubai
17 – 20 Aug 2026
DWTC, Dubai
17 – 20 Aug 2026
Table of Contents
2.5 million+ properties. The widest inventory of any single B2B supplier. Net rates with full markup control. And the fastest onboarding of any major hotel API — ZentrumHub already has it live inside Zentrum Connect.
RateHawk is the newest major hotel supplier API on this list — launched in 2018 — and it has grown faster than almost any other B2B inventory platform in the industry. While Expedia took decades to build its supplier network and Amadeus required decades of GDS infrastructure, RateHawk went from launch to 2.5 million properties in under six years by doing something different: instead of building a direct hotel supply network, it aggregated the ones that already existed. The RateHawk Hotel API is the programmatic interface to that aggregated inventory — and it offers the widest property coverage of any single B2B supplier available to OTAs today.
This guide covers exactly what the RateHawk hotel API delivers, how its unique multi-source aggregation model works, the net rate commercial structure, the HMAC authentication requirements, and how ZentrumHub activates RateHawk alongside 100+ other suppliers for OTAs that want full inventory coverage through a single connection.
RateHawk is a B2B-only hotel booking platform launched in 2018 by Emerging Travel Group (ETG) — a travel technology company that also operates Ostrovok.ru (a CIS-focused consumer OTA) and ZEN Hotels. Unlike every other supplier covered in this series, RateHawk has no consumer-facing website. Every booking on the platform is made by a travel professional — an agency, OTA, or tour operator. This B2B-only positioning means its commercial model, inventory strategy, and pricing structure are designed exclusively around travel business needs.
What makes the RateHawk hotel API architecturally different from other suppliers is its multi-source aggregation model. Rather than building a direct hotel contracting network from scratch, RateHawk connected to 200+ existing hotel suppliers — bedbanks, GDS feeds, and direct hotel connections — and aggregated their inventory behind a single API. When an OTA queries RateHawk for a hotel in Paris, RateHawk queries multiple sub-sources simultaneously and returns the best available rate from across its supplier network.
RateHawk Hotel API is a B2B-only RESTful API that gives OTAs and travel platforms programmatic access to 2.5M+ hotel properties aggregated from 200+ global suppliers — including Hotelbeds, WebBeds, GTA, Tourico, and direct ETG hotel contracts — through a single integration point with net rate pricing and full OTA markup control.
This aggregation model means RateHawk already functions as a mini-aggregator itself. An OTA integrating RateHawk alone gets exposure to inventory from dozens of underlying suppliers — without negotiating individual contracts with each one. This is a meaningful advantage that distinguishes RateHawk from pure direct bedbanks like Hotelbeds or Expedia.
With 2.5 million+ properties, RateHawk hotel inventory is the widest of any single B2B supplier API. RateHawk’s rapid growth has been driven by its aggregation of existing bedbank networks, giving it depth in markets where building direct hotel relationships would have taken years. Here is what the inventory actually covers:
Because RateHawk aggregates 200+ suppliers internally, an OTA integrating the RateHawk hotel API gets exposure to inventory from Hotelbeds, WebBeds, GTA, Tourico, and dozens of other suppliers in a single connection. This partially reduces — though does not eliminate — the need for multiple direct supplier integrations. For OTAs starting out or operating with limited engineering resources, RateHawk’s aggregated inventory is one of the fastest routes to broad hotel coverage with a single API call.
The RateHawk hotel API uses REST/JSON with API Key authentication for most endpoints, and HMAC signature verification for specific secure operations. Critically — always use API v3. Earlier versions (v1, v2) are still in circulation among legacy partners but are deprecated and should not be used for new integrations.
| Endpoint | Path (v3) | Function |
|---|---|---|
| Hotel Search | /api/b2b/v3/hotel/search | Search hotels by location, geo-coordinates, or hotel ID. Returns rates, rooms, availability from aggregated sources. |
| Hotel Content | /api/b2b/v3/hotel/info | Hotel static content — name, address, images, amenities, descriptions. Use for content database pre-loading. |
| Confirm & Book | /api/b2b/v3/hotel/finish_order | Confirms and creates hotel reservation. Returns order ID and booking confirmation number. |
| Retrieve Booking | /api/b2b/v3/hotel/order_info | Retrieves booking details, status, and voucher information for customer delivery. |
| Cancel Booking | /api/b2b/v3/hotel/order_cancel | Cancels booking per property cancellation policy. Free cancellation window varies by rate type. |
Some RateHawk API endpoints require HMAC (Hash-based Message Authentication Code) signature verification. This involves generating a request signature using your API Secret and the request parameters, then including that signature in the request header. It is more secure than plain API Key auth but adds a signing step to each request. Ensure your integration has a dedicated request signing utility — building HMAC inline with business logic creates maintenance problems as the API evolves.
RateHawk operates a net rate model exclusively — there is no commission option, no post-stay settlement, and no revenue share. You pay RateHawk the net rate at booking, you set your own markup, and you keep the difference. This is one of the cleanest commercial models in hotel B2B distribution:
RateHawk has the fastest onboarding of any major hotel supplier API. Compared to Expedia’s 12–20 week process or Amadeus’s 10–18 week enterprise agreement cycle, RateHawk’s streamlined onboarding is a significant advantage for OTAs needing inventory quickly:
Here is how the RateHawk hotel API compares against the other major hotel supplier APIs across all key dimensions:
| Factor | RateHawk | Expedia Rapid | Hotelbeds | Agoda | Priceline PPN |
|---|---|---|---|---|---|
| Properties | 2.5M+ — #1 globally | 700K+ | 250K+ | 2M+ | 800K+ |
| Rate Model | Net only — full markup control | Net + Commission | Net wholesale | Commission | Commission (8–15%) |
| Onboarding Speed | 1–2 weeks — fastest | 12–20 weeks | 8–16 weeks | 4–8 weeks | 6–12 weeks |
| Auth Method | API Key + HMAC | API Key + Secret | API Key | API Key | API Key + Secret |
| IATA Required | No | No | No | No | No |
| Inventory Type | Multi-source aggregated | OTA direct | Bedbank direct | OTA direct | Booking Holdings pool |
| Key Differentiator | Widest coverage + fastest access | Global + dual payment | Leisure rate depth | APAC exclusives | Express Deals + US depth |
Despite RateHawk’s advantages in speed and coverage, the RateHawk API integration has specific challenges that OTAs consistently encounter:
ZentrumHub is a hotel API integration provider and travel technology company. The RateHawk hotel API is already built, maintained, and live inside Zentrum Connect — alongside Expedia, Amadeus, Agoda, Priceline, and 95+ other suppliers. See the RateHawk hotel API with ZentrumHub page for full details on how supplier activation works.
OTAs that have a commercial agreement with RateHawk bring their contract to ZentrumHub. ZentrumHub activates it inside Zentrum Connect — and it immediately becomes part of your combined hotel inventory feed. The HMAC signing, v3 versioning, property ID normalisation, and cross-supplier deduplication are all handled inside Zentrum Connect. Your booking engine receives one clean, unified feed with RateHawk’s 2.5M+ properties included.
With this supplier series complete, the picture is clear: a competitive OTA in 2026 needs Expedia for global reach and dual payment flexibility, Amadeus for corporate chain rates, Agoda for APAC exclusives, Priceline for US depth and Express Deals, and RateHawk for the widest total coverage and CIS/MEA strength. Running all five through ZentrumHub’s Hotel Supplier Connect means one integration, one deduplicated feed, and one booking engine — instead of five separate technical projects totalling 2+ years of engineering time. See the RateHawk & ZentrumHub partnership case study for a real example.
ZentrumHub activates your RateHawk supplier agreement inside Zentrum Connect — combining it with Expedia, Amadeus, Agoda, Priceline and 95+ more suppliers in one deduplicated inventory feed.
Talk to Our Integration Team →ZentrumHub’s Zentrum Connect combines all five supplier APIs from this series — plus 95+ more — into one hotel inventory feed with real-time deduplication, sub-500ms response, and direct activation inside your booking engine. 3M+ room nights booked. $650M+ revenue generated for clients.
