Hotels · Integration
RateHawk API integration
RateHawk, from Emerging Travel Group, has become a strong second or third bedbank for agencies who find their primary source thin on particular regions. Adding it is often the cheapest way to fix a coverage gap.
Live in 3–7 working days from credentialsWhat RateHawk brings you
- Broad global hotel inventory with useful depth in Europe and Central Asia
- Competitive rates that frequently undercut a single-source setup
- Static content and hotel mapping data
- Clear cancellation policy handling per rate
- B2B-oriented terms suited to agency and sub-agent distribution
- Rate types clearly distinguished by board and refundability
What we connect
- Availability search merged with your other hotel sources
- Rate revalidation before payment
- Booking with guest detail and special-request pass-through
- Cancellation with charges calculated and shown up front
- Content ingestion and mapping against your existing hotel records
- Per-supplier markup so a second bedbank can carry a different margin
Where it plugs in
- Your B2B agent portal, with tier-based markups
- Your B2C consumer site, at retail pricing
- Your corporate self-booking tool
- Your iOS and Android apps, with no separate setup
- The back office — one ledger, one reconciliation
- Turned on or off per market, channel and agent tier
The point of a second bedbank is not to replace the first — it is to win the searches where the first returns nothing or returns an uncompetitive rate. Once both are live, the platform reports which source is actually winning bookings by region, which tells you whether the second one is earning its keep.
Timeline
Three to seven working days.#
Send test credentials, the API documentation and a contact at RateHawk. We map search, book, cancel and refund, run certification if it is required, and switch to production once you have signed off on UAT.
RateHawk integration questions#
Why would I add a second hotel supplier?
Coverage and price. Any single bedbank has regions where its inventory is thin or its rates are beaten. A second source fills those gaps, and the reporting shows you exactly which regions and how often, so the decision is evidenced rather than assumed.
Will the same hotel show twice?
No. Content mapping links the same property across suppliers to one record, and your rule decides which rate is displayed — usually the best net rate after your markup, though you can prioritise a supplier for commercial reasons.
Does adding a supplier slow down search?
Slightly, since more sources are queried. The platform runs them in parallel and applies a timeout, so a slow supplier degrades rather than blocks the result. You can also restrict a source to specific regions where it actually adds value.
Keep reading
Related integrations#
Start selling next week.
Take the trial on your own routes and fares, on whichever model suits you. Nothing to install, nothing to sign.