Google Hotels Prices
Pricing
from $1.70 / 1,000 property rows
Google Hotels Prices
Google Hotels prices for any destination and dates: one row per property with nightly price, stay total with taxes and fees, star class, rating, reviews, deal label, amenities, phone, and coordinates. Properties with no price and repeats are free.
Pricing
from $1.70 / 1,000 property rows
Rating
0.0
(0)
Developer
Mamba Labs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 minutes ago
Last modified
Categories
Features
Share
Give destinations and stay dates. The actor reads the Google Hotels result page for each destination and check in date and returns one row per property: nightly price, stay total with taxes and fees, star class, rating, review count, deal label, and amenities. You pay per priced property. Properties with no price for your dates, repeats, and summary rows are free.
Features
- One row per property with nightly price, stay total with taxes and fees, nights priced, star class, rating, review count, deal label, price compared with usual, amenities, address line, phone, and coordinates.
- Several destinations and several check in dates in one run. Each destination and date pair is one search, so you can track rates across dates.
- Each search is checked against the place and the dates Google applied. If Google did not recognize the destination, the search returns a free row and no properties from somewhere else.
- Each search is checked against the dates Google applied. If Google did not apply your dates, the search returns a free error row and no prices.
- Each search ends with a free summary row with the result count Google reports and what was returned or skipped.
- Number and on or off inputs are text, so Clay can send them as they are.
How the data is read
The actor sends one plain request per search to the public Google Hotels search page, google.com/travel/search, with the stay dates in the search text, through the Apify proxy default pool. It reads the server rendered result cards. No login, no browser, no API key, and no other developer's actor. A rate limit or bot check page from Google ends that search in a free blocked row; the actor does not retry it on other addresses.
Input
| Field | Type | Default | What it does |
|---|---|---|---|
destinations | array | Cities, areas, or landmarks, one per line, for example Miami, Paris 1st arrondissement, or near Times Square. The actor searches "hotels in | |
check_in | array | One or more check in dates, YYYY-MM-DD, up to 330 days ahead. Each date is its own search. Empty: 14 days from today. | |
nights | string | 2 | Length of each stay, 1 to 30. Default 2. Ignored when check_out is set. |
check_out | string | Optional. YYYY-MM-DD. Works with one check in date only; for several dates use nights. | |
max_hotels_per_search | string | 20 | 1 to 40. Default 20. Google Hotels shows about 18 to 20 properties on its first page, and this actor reads that page only. |
hotels_only | string | false | true: keep only properties Google gives a star class, and drop vacation rentals and unclassified properties (free). Default false. |
priced_only | string | false | true: leave out properties Google shows with no price for your dates. Default false, which returns them as free rows. |
dedupe | string | true | true (default): a property already returned for the same dates in this run is skipped and not charged. |
max_charge_usd | string | Optional. The run stops before a charge that would pass this amount. Summary rows are always returned. |
Example:
{"destinations": ["Miami", "Lisbon"],"check_in": ["2026-12-10", "2026-12-17"],"nights": "2","max_hotels_per_search": "20"}
That is 4 searches: each destination for each check in date.
Output
| Field | Type | What it holds |
|---|---|---|
row_type | string | One of: property, search_summary, run_summary. run_summary is the one free row written when the input is refused. |
input | string | The destination from your input. |
search_text | string | The exact text sent to Google Hotels, with the dates. |
check_in | string | Check in date, YYYY-MM-DD. |
check_out | string | Check out date, YYYY-MM-DD. |
resolved_location | string | The place Google resolved your destination to, for example Miami. |
rank | integer | Position in the Google Hotels list for this search, counting each property once. |
name | string | Property name as Google shows it. |
entity_id | string | Google Hotels property ID. Stable key for dedupe and for tracking one property across runs. |
google_hotels_url | string | Link to the property on Google Hotels. |
address_line | string | Street address or locality Google gives for the property. |
latitude | number | Property latitude. |
longitude | number | Property longitude. |
phone | string | Property phone as Google lists it. |
property_kind | string | hotel (Google gives a star class), vacation_rental, or unclassified. |
hotel_class | integer | Star class Google gives, 1 to 5. Null when Google gives none. |
price_nightly | number | Lowest nightly price Google shows for the stay, in the listed currency, before taxes and fees as Google displays it. |
price_total | number | Total for the whole stay with taxes and fees, as Google shows it. |
price_lead | number | The "prices starting from" figure on the card. |
currency | string | Currency of the prices. Google Hotels answers this route in USD. |
nights_priced | integer | Nights Google priced the total for. Matches your stay. |
deal_label | string | DEAL or GREAT DEAL when Google marks one. |
price_vs_usual | string | Google's comparison with the usual price, for example 44% less than usual. |
rating | number | Google review rating out of 5. |
review_count | integer | Number of Google reviews. |
amenities | array | Amenities listed on the card, up to about 9. |
eco_certified | boolean | True when Google shows the eco-certified badge. |
results_total | integer | On search_summary rows: the result count Google reports for the search. |
properties_found | integer | On search_summary rows: properties read from the page. |
properties_returned | integer | On search_summary rows: priced rows returned and charged. |
properties_skipped | integer | On search_summary rows: repeats and rows your filters removed. |
row_status | string | ok, or why this row carries no data: no_results, no_change, partial, blocked, or error. |
error_reason | string | Why the row is not ok. A refused input reads input_invalid: followed by what to fix. |
billable_events_json | string | What this row was billed as, for example {"property-row":1}. {} means free. |
scraped_at | string | When the row was written, UTC. |
Pricing
Pay per event. Summary rows, properties with no price, repeats, and a refused input are free.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
property-row, one priced property | $0.002 | $0.0019 | $0.0018 | $0.0017 |
apify-actor-start, once per run (one per GB of memory; the default 512 MB is one) | $0.005 | $0.005 | $0.005 | $0.005 |
Per 1,000 rows of property-row: $2.00 on the free plan, $1.70 on Gold.
Free plan cap: 1.50 USD of evaluation a month, about 750 rows. Any paid Apify plan removes the cap, and it resets on the 1st. The run stops before a charge that passes your maximum charge per run in Apify or your max_charge_usd input.
Mamba Labs pays the platform costs of your run, Apify proxy traffic included.
A search returns up to about 20 properties, so a full search costs up to 20 property rows plus the run start.
Usage examples
Clay. Number and on or off inputs are text fields, which is what Clay sends. A list input takes a JSON list, so put the column inside a one item list, for example a JSON list holding the city column for destinations.
Rate tracking. Run the same destinations every day with the same check in dates and compare price_nightly by entity_id.
MCP. The Mamba Labs MCP server @mambalabsdev/mcp-google-hotels-prices exposes this actor to Claude and other MCP clients.
Error handling
| Case | What you get |
|---|---|
| Missing or unreadable input | One free row, row_type run_summary, error_reason starting input_invalid: with what to fix. The run ends successfully and charges nothing but the run start |
| A check in date in the past, more than 330 days ahead, or a stay over 30 nights | Refused the same way, with the date named |
| Google applied different dates than you asked for | One free search_summary row with row_status error naming the dates Google applied. No property rows for that search |
| Google does not recognize the destination and shows properties near the requesting address instead | One free search_summary row with row_status no_results naming the place Google showed. No property rows for that search |
| Google shows a property with no price for your dates | A free property row with row_status no_results, or left out with priced_only set to true |
| Google answers with a rate limit or bot check | One free search_summary row with row_status blocked. After 2 blocked searches in a row the run stops |
| The run is close to its timeout | The actor stops starting new work 90 seconds before the timeout and delivers what it has |
Limitations
- One result page per search: about 18 to 20 properties. Google's further pages load through a script action, which this actor does not use. For more properties, search smaller areas, for example neighborhoods or landmarks.
- Prices are for 2 adults and in USD. Google Hotels ignored guest counts and currency settings on this route in tests on 2026-11-17.
- One lead price per property, as Google shows it on the result card. The price per booking site is not included.
- Google orders results differently by the requesting address, so
rankis the order on that request. - Google's terms and robots.txt (
Disallow: /travel/search) restrict automated access. Read them before you rely on this data.
Mamba Labs actor suite
Built by Mamba Labs.