Rate Parity Monitor
Parity leaks quietly and costs you the direct booking. This recipe reads what every channel charges for your hotel on Google Travel, night by night and next to your official website, so you can see the nights and channels where your rate is undercut.

What you'll build
A parity dashboard: a night-by-night list with your official-website rate, the cheapest channel selling your hotel on Google Travel and the gap, highlighted so a leak is obvious without reading numbers one by one.
Set this up first
RequiredThe endpoints don't take free text — they take your identifiers. This recipe assumes the things below already exist on your account; while one of them is missing, the call answers with an error or with less than you expect. Each point links to the recipe that walks it.
- 01
Register the hotel in your dashboard
Veetal resolves the property against Booking.com and assigns it a slug — and that slug, not the hotel name, is what every accommodation endpoint takes.
Guide: Add your hotel and the comp set you price against → - 02
Run one import on the hotel
A Feed dataset only contains what an import has written. Activate this API on the hotel, launch the first run by hand and read the credit estimate before you press — the cost grows with the comp set and, on multi-OTA datasets, with the OTAs too.
To see whether an import has already finished, list them:
curl "https://api.veetal.app/v3/account/imports" \
-H "veetal-api-key: YOUR_API_KEY"Feed reads are not billed per request. The credits go on the imports that collect the data, which is why the estimate appears before you launch and not after.
How it works
- 01
Get your API key
Create your account and copy your key. Start free with 1,000 API credits.
- 02
Pick your hotel
List the accommodations on your account and copy the slug of the hotel you want to monitor.
- 03
Import the parity, then read it
The hotel needs its Google Hotel Ads code, which Veetal usually finds when you add it. Launch a parity import with enough days of visibility for your window, then read it by night or by month: each night lists the rate of every channel on Google Travel, with your official website marked.
The call
One request returns, for every check-in night of the month, the rate each channel shows for your hotel on Google Travel, with your official website marked. Swap in your hotel slug and your key.
curl "https://api.veetal.app/v3/feed/accommodation/YOUR_HOTEL_SLUG/parity/v7/2027/03?adults=2" \
-H "veetal-api-key: YOUR_API_KEY"Build it with AI
Connect the MCP →Paste this prompt into an assistant with the Veetal MCP connected and it builds the whole app against your data — no front-end work.
Use my Veetal Connect data to build a rate parity monitor for my hotel,
covering next month.
I want to see where my direct rate is being undercut: for every check-in
night, how the rate on my official website compares with what every other
channel shows for my hotel on Google Travel. Read it from my most recent parity
import that covers next month (account_imports lists the nights each one
covered); if none does, tell me how many days of visibility it needs instead
of filling the gap.
Build it as a single self-contained HTML page, plain HTML and CSS:
- A night-by-night list, worst parity first, so the problems are at the top.
- For each night: my official-website rate, the cheapest other channel and
its name, the gap in money and in percent, and a clear flag when I am
undercut.
- A summary at the top: how many nights are out of parity, the channel that
undercuts me most often, and the worst night.
- Let me switch occupancy (number of adults) if the import has more than one.
- Never invent a rate — leave the night out when there is no data for it or
no official-website rate to compare with, and mark the nights where Google
did not list every channel.
Clean, scannable, works in light and dark.Questions
Which rate counts as mine?
The one Google Travel marks as your official website. Every other row is a channel selling your hotel, and a channel below your direct rate on the same night is a parity break. When Google shows no official website for a night there is nothing to compare against, so leave that night out.
Does it cover mobile rates?
No. The parity import reads Google Travel as a desktop search and has no device option. What it can split is occupancy: launch the import for several numbers of adults and read each one separately.
How fresh is the data?
It is the pre-processed Feed layer, refreshed on your account schedule, and each import is kept for 15 days. For a price at this exact second, use the real-time parity endpoint instead.
What date range should I ask for?
Read one check-in night or a whole month. The feed only holds the nights the last import covered, counted from the day it ran, so to cover all of next month launch the import with about 60 days of visibility.
What does it cost?
Reading the feed is not billed per request: the credits go on the import. Each run charges 0.5 credits per check-in night and per occupancy, so 60 nights for 2 adults is 30 credits a run, about 915 a month on a daily schedule. The dashboard shows the estimate before you launch.
Build your own
Start free with 1,000 API credits. No credit card, no sales call.
What do you want to build with disparities?
Say it in one line and we hand you back the prompt, the recipe if one already exists, and the APIs it runs on — starting with disparities.