One call, every channel's price
The only source that returns a hotel's price across all OTAs at once — the basis of any parity or comparison product.
Every OTA in one response
One request per hotel and stay returns a row for each channel selling it, with a deep link. Adding a channel to your comparison costs no extra integration.
Parity without the join
All the prices arrive together, so detecting where a channel undercuts your direct rate is a comparison inside one payload rather than a reconciliation across sources.
Aggregated reviews, tagged by origin
Reviews come back with category scores and the source each one came from, so you can analyse Google's own or everything it aggregates.
Who uses the data from Google Hotels?
Focus on your applications. We provide the data.
What market do you need?
We create infrastructure tailored to your needs
340 markets at your disposal
We’ll extract the data from the locations you need. The main markets are available.
570 currencies
Choose the currency of the data
24 languages
Choose the language of the data

What do our data get used for?
Real builds already running on the API. Pick one and you get the exact endpoints behind it.

- Accommodation parityFeed APIDocs ↗
GET /feed/accommodation/{accommodation_slug}/parity - Accommodation ratesFeed APIDocs ↗
GET /feed/accommodation/{accommodation_slug}/rate
Frequently asked questions
What is the Google Hotels API used for?
Mainly rate comparison and parity. One request returns a hotel's live price on every OTA advertising a given stay, one row per channel with a deep link, which is the foundation of any price comparison or parity monitoring product.
Can I get a hotel's price on every OTA in one call?
Yes. That is what makes this source different from querying each OTA separately: every channel selling the stay arrives in the same response, so adding a channel to your comparison costs no extra integration.
Are Google hotel review dates exact?
Not to the day. Google publishes a relative age rather than the date a review was written, so the date is derived from it: the month is reliable but the exact day is not. Bucket Google-sourced review sentiment by month rather than by day.
What do you want to build with Google Hotels?
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 Google Hotels.
