A rate parity checker API, from the booking engine to every OTA
Put the rate a hotel sells on its own website next to Booking.com, Hotels.com, Agoda, Expedia and every seller Google Hotels shows for the same night, in one API.
Built for hotel groups, revenue managers, distribution teams, rate-intelligence vendors.
Every seller Google lists for one night, from one call to POST /v1/offers, measured against the official site. This is the check a parity monitor runs every morning.
Loading a real answer…
A week of parity at a glance
Every channel against the direct rate, night by night. Hover a cell or an alert to read the check.
Example · rate parity monitor
Which channel undercuts our direct rate this week?
POST /v1/official
POST /v1/ota/compare
your alert rule
Checks
28
Undercuts
3
Worst
-4.0%
Total price per night on each channel, against the direct rate
Apr 2027
Mon 19
Tue 20
Wed 21
Thu 22
Fri 23
Sat 24
Sun 25
Direct site
$189
$189
$199
$212
$239
$249
$179
Booking.com
Expedia
Hotels.com
Agoda
Alerts from your rule · below direct by 1% or more
Nights at or above direct
Booking.com
7/7
Expedia
6/7
Hotels.com
7/7
Agoda
5/7
Agoda · Sat 24 Apr · $239 vs $249 direct
undercut -4.0%
below direct at parity above direct totals incl. taxes & fees, 1 night, King room
Is an OTA undercutting our direct rate?
Parity breaks quietly. A wholesale rate leaks to an OTA, a metasearch seller shows a member price to everyone, or a promotion ends on one channel and not another. By the time a guest mentions it, the cheaper rate has been bookable for days.
Checking by hand stops working after a handful of dates. The direct rate is the anchor, so it has to come from the hotel's own booking engine, read the same way every day, next to each OTA's own number for the identical stay.
How teams build it
1 Resolve the property once
Turn the hotel name into its Google property token and its Booking.com, Hotels.com, Agoda and Expedia ids. Store them with the hotel record.
Compare the OTAs' own inventory in one call, with sources that run in parallel and fail independently, or read every seller Google displays from the property token.
It reads over 50 booking engines, with more added regularly, detected automatically from the hotel website, so you never choose the vendor.
Should I use the OTA comparison or Google offers?
Use the comparison when you need each OTA's own number from its own inventory. Use Google offers, 10 credits (14 with require_rooms), for a quick market view: it returns every seller Google displays for the night, from one property token and with no OTA ids. Failed calls cost 0.
What happens when an OTA does not answer?
Sources in a comparison run in parallel and fail independently, so the others still return. If none of them returns a price, the comparison is not charged.
Can it run every day without my own scheduler?
You schedule the calls. Most teams run a daily cron job and store each answer; every response says when it was collected.
Create an account and verify your email: your own API keys and a free trial of 50 calls or 14 days, whichever ends first, no card needed. Then buy a credit pack from $15 or pick a plan from $49 a month.