Google Hotels API: What It Actually Is, Who It's For, and How to Get the Data
Google Hotels shows the one thing no single booking site can: every seller's price for the same room, side by side. This guide explains why Google's official hotel APIs won't give you that data, who those APIs actually serve, and the working route to the per-partner price list as JSON.
Table of contents

The Google Hotels API exists, but it flows in the opposite direction from what most people searching for it expect.
Google's hotel APIs let hotels and booking sites push their prices into Google's results.
Pulling Google Hotels data out has no official API at all.
That one inversion resolves most of the confusion around this search.
The official surfaces (Hotel Prices feeds, the Travel Partner API) serve advertising partners: businesses that own bookable inventory and bid to appear in Google's hotel results.
If that's you, you already have an account manager.
Everyone else wants the data they can see on the page: the list of booking sites and prices per hotel, the direct rate, the reviews.
If you just want alerts for one trip, Google's built-in price tracking feature covers that without any API.
For the data itself, there's a working route, covered below.
Key Takeaways
- Google has no public API for Google Hotels data. The official hotel APIs exist for advertisers pushing rates into Google's results.
- The Hotel Prices and Travel Partner APIs serve inventory owners. Hotels and OTAs feed rates in and manage campaigns. Access comes through partner onboarding.
- Places API is the closest self-serve option, and it's capped. Place details, photos, and about 5 reviews per property, with zero pricing data.
- The valuable data is the per-partner price list. Google shows every booking site's rate for the same room, including the hotel's own site.
- Third-party data APIs return that list as JSON. Each partner, its price, and a booking link per property, available on signup.
What Google's Hotel APIs Actually Are

Google's official hotel surfaces split into three products, and none of them hands data to developers.
| Surface | Direction | Who it serves | Data out? |
|---|---|---|---|
| Hotel Prices feeds (Hotel Ads) | Push rates in | Hotels and OTAs with bookable inventory | No |
| Travel Partner API | Manage your ads | Existing Hotel Ads participants | Only your own reporting |
| Places API | Pull, limited | App developers | Metadata and ~5 reviews, no prices |
Hotel Prices feeds are the pipe behind Google's hotel ads: accommodation providers and OTAs feed rates and availability into Google's hotel search, through approved integration partners, with feed specs and bidding attached.
Google's own Hotel Prices documentation is written for exactly this audience.
It's an advertising product with an API attached, and qualifying for it requires owning inventory you can sell.
The Travel Partner API manages campaigns for businesses already inside that program: budgets, bids, participation reporting.
It reads your own advertising account, and nothing about the wider market.
The Places API is the one hotel-adjacent Google API any developer can self-serve.
It returns place details, photos, ratings, and a capped set of reviews (typically 5 per property, with no pagination, per the Place Details documentation).
Pricing and availability are entirely absent.
If you searched "google hotel reviews api", this is where you land, and 5 reviews per property is a teaser rather than a dataset.
Some searchers still call all of this the Google Hotel Finder API, after the product name Google retired years ago; the surfaces above are what replaced it.
The shape mirrors what we've documented for the Booking.com API programs and the Marriott API: official APIs serve the platform's business model, which here is advertising in rather than data out.
The Pricing and Access Questions, Answered
Is the Google Hotel API free?
The Hotel Ads integration has no API fee, because you pay through the advertising model: cost-per-click or commission on bookings.
"Free" is the wrong frame for an ad product.
Places API bills per request with a monthly credit; check Google's current pricing page for the numbers.
How do I get a Google Hotels API key?
There's no self-serve key for hotel prices data.
Hotel Ads access goes through partner onboarding for inventory owners.
The only self-serve key that touches hotel content is Places API, with the data limits above.
Can Places API give me hotel prices?
No.
It covers names, photos, ratings, and a handful of reviews, and it's genuinely useful for enrichment.
Rates, availability, and multi-site price comparison sit outside its scope entirely.
What People Actually Want: Google Hotels Data

Three jobs sit behind most "google hotels api" searches, and naming yours picks your tooling.
Job 1: the aggregated price view.
Google Hotels shows every booking site's rate for the same hotel and dates in one list.
That multi-channel snapshot is the whole value of the surface, and the job is getting it as data.
Job 2: the direct rate.
Google is the one place where the hotel's own-website rate appears next to the OTA rates.
That makes it the natural input for rate parity checks and direct-versus-OTA comparison.
Job 3: monitoring over time.
Today's Google Hotels prices are a snapshot.
Logged daily, they become price history and market movement; our hotel price tracker guide owns that build.
How to Actually Get Google Hotels Data

Third-party data APIs read Google's hotel results and return them as structured JSON, which makes them the literal answer to this search.
StayAPI's Google Travel endpoints work in two steps: resolve the hotel once, then pull whatever data you need with the token.
Step 1 resolves a hotel name to a durable entity_token:
curl -G "https://api.stayapi.com/v1/google_travel/resolve" \
-H "x-api-key: YOUR_API_KEY" \
--data-urlencode "query=JW Marriott Hotel Bangkok"
Step 2 calls the prices endpoint with that token:
curl -G "https://api.stayapi.com/v1/google_travel/prices" \
-H "x-api-key: YOUR_API_KEY" \
-d "entity_token=ChcI34eltpWZyPQNGgsvZy8xMjFxOHpoZhAB" \
-d "currency=USD"
The response is the per-partner price list as Google surfaces it, truncated here to the fields that matter:
{
"success": true,
"check_in": "2026-07-23",
"check_out": "2026-07-24",
"currency": "USD",
"price": { "formatted": "US$256", "value": 256.04 },
"offers": [
{ "partner": "JW Marriott Hotel Bangkok", "price": "US$279", "booking_link": "https://www.google.com/travel/lodging/clk?..." },
{ "partner": "HOPEGOO", "price": "US$256", "booking_link": "..." },
{ "partner": "Booking.com", "price": "US$279", "booking_link": "..." },
{ "partner": "Expedia.com", "price": "US$279", "booking_link": "..." }
]
}
Notice the first partner: it's the hotel itself.
When the property advertises its direct rate on Google, it arrives in the same offers array as the OTAs, which is the direct-versus-OTA comparison in a single call.
| Field | Example | What it is |
|---|---|---|
offers[].partner |
"Booking.com" | The seller: an OTA or the hotel's own site |
offers[].price |
"US$279" | That seller's nightly rate |
offers[].booking_link |
"https://www.google.com/travel/..." | Click-through to that seller's checkout |
price.value |
256.04 |
Lowest available rate as a number |
check_in / check_out |
"2026-07-23" | The dates the rates apply to |
One tradeoff to know: the prices endpoint returns rates for Google's default near-term dates (echoed back as check_in and check_out) rather than dates you choose.
For a specific stay, the Google Hotels info endpoint accepts query, check_in, and check_out and returns the lowest nightly rate for those dates.
Here's how the three routes compare for hotel data:
| Hotel Ads / Prices feeds | Places API | StayAPI Google Travel | |
|---|---|---|---|
| Direction | Push your rates in | Pull, limited | Pull |
| Prices | Yours only, inbound | None | All partners incl. direct rate |
| Reviews | None | ~5 per property | Summary, sub-scores, source breakdown |
| Access bar | Partner onboarding | Self-serve key | Signup, 50 free requests |
| Built for | Inventory owners | App developers | Data and intelligence work |
A daily loop that appends each response to a sheet turns these snapshots into the price history Google never shows; the tracker guide linked above walks through that build.
Getting Started
- Sign up at stayapi.com: 50 free requests, no credit card, enough to test a handful of properties.
- Preview the data without code using the free Google hotel search tool.
- Resolve your first property and call the prices endpoint, as shown above. Cache the
entity_token; it's durable. - Automate: an N8N or Make.com schedule can log the
offersarray daily and alert on changes, no code required. For teams monitoring a portfolio or comp set, book a demo.
FAQ
Does Google Hotels have a public API?
No.
Google's hotel APIs (Hotel Prices feeds, the Travel Partner API) exist for advertisers pushing rates into Google's results.
No official API pulls Google Hotels data out; third-party data APIs are the working route.
What is the Google Hotel Ads API?
It's the integration surface for properties and OTAs participating in Google's hotel ads: rate feeds, availability, bidding, and campaign management.
It serves businesses selling rooms, and it provides no market data.
Can I get hotel reviews from Google's API?
Places API returns a small capped set of reviews per property, typically 5 with no pagination.
That's enough for display enrichment and far short of analysis; for review data at scale, OTA review endpoints are the working route, and StayAPI's Google Travel summary endpoint adds the rating histogram and topic sub-scores.
How do I get the prices Google Hotels shows, as data?
Through a third-party data API.
StayAPI's Google Travel prices endpoint returns the per-partner list (each booking site, its rate, and a booking link, including the hotel's direct rate when advertised) as structured JSON.
Is Google Hotels data free to access?
Google offers no data access at any price.
Third-party access typically starts free: StayAPI includes 50 requests on signup, no credit card required.
Ready to simplify your hotel data?
Join other developers using StayAPI to build the next generation of travel applications. Get started for free today.