Google Hotels puts stars, guest ratings, nightly prices and booking-site offers for a destination on one page. Travel products, rate-shopping tools and revenue managers want that data as rows: a list of hotels to compare, the full record for one property, and how its price moves across dates.
On 2026-11-17 SocQ launched the Google Hotels platform with three endpoints that do exactly that. They chain together through one field, the hotel id. This guide covers what each returns, the request, the price and when to use it.
Quick answer: Search a destination with
POST /v1/google-hotels/searchand keep each hotel'sid. Pass it ashotel_idtoPOST /v1/google-hotels/hotel-detailsfor amenities, review topics and booking-site offers, or toPOST /v1/google-hotels/hotel-pricesfor the lowest nightly price by check-in date. PollGET /v1/tasks/{task_id}for the results.
The New Google Hotels Endpoints
1 SocQ credit = $0.005.
| Endpoint | What it returns | Price |
|---|---|---|
| Google Hotels API | Hotels for a destination with stars, guest rating, review count, the lowest nightly price for your dates, location, photos and the hotel id | 0.15 credits ($0.00075) per hotel |
| Google Hotel Details API | One hotel's address, phone, website, amenities, location scores, rating breakdown, review topics, ratings on other sites and the offer from each booking site | 2 credits ($0.01) per call |
| Hotel Price Tracker API | One row per check-in date with the hotel's lowest price for one night, usually six to eight weeks of dates | 4 credits ($0.02) per call |
Authentication and the Async Task Flow
All SocQ requests authenticate with an API key, and the same header is used for submit, task status and result requests:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Every collection runs as a background task:
submit -> task_id -> queued -> running -> succeeded
\-> failed
The submit response contains data.task_id and data.status. Poll the task with that ID:
curl "https://api.socq.ai/v1/tasks/$TASK_ID?limit=50" \
-H "Authorization: Bearer $SOCQ_API_KEY"
When status is succeeded, the response includes the first page of normalized records in data.results.items. limit defaults to 50 and goes up to 500; if has_more is true, pass results.next_cursor as cursor to read the next page. While a task is queued, running or failed, the endpoint returns task metadata without results.
An optional callback_url in the submit body makes SocQ send one POST with a task summary when the task finishes; read the records with GET /v1/tasks/{task_id}. A client-side timeout does not cancel a task, so resume with the same task ID instead of paying for a duplicate. 402 means insufficient credits; 429 means the key hit a rate or credit limit.
Google Hotels API: Search a Destination
The Google Hotels API searches hotels the way travelers do on Google. Provide a destination or hotel search in query.
curl -X POST "https://api.socq.ai/v1/google-hotels/search" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "hotels in new york",
"currency": "USD",
"results_limit": 18
}'
Optional fields:
check_inandcheck_out(YYYY-MM-DD, given together, up to 30 nights) price a specific stay. Without them, prices are for one night from tomorrow.currency: a three-letter code such asUSDorEUR.sort_by:relevance,lowest_price,highest_ratingormost_reviewed.min_priceandmax_price: the nightly price range, in the chosen currency.location_code(default 2840, United States) andlanguage_code(defaulten).results_limit: 1 to 140, default 18.
Each hotel row has id, name, stars (1 to 5), rating (1 to 5), reviews_count, price (amount, currency, formatted), the check_in and check_out the price is for, is_sponsored, location with latitude and longitude, images, and rank in the results. The default 18 hotels cost 2.7 credits ($0.0135); the maximum of 140 costs 21 credits ($0.105). Docs: Google Hotels search.
Google Hotel Details API: Everything About One Property
The Google Hotel Details API returns one row with what Google Hotels knows about a property. Pass the id from a search result as hotel_id. Add check_in and check_out to get offers for those dates; otherwise offers are for one night from tomorrow.
curl -X POST "https://api.socq.ai/v1/google-hotels/hotel-details" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"hotel_id": "ChoIyKbJ6puqvPf8ARoNL2cvMTFqNHR2MjczeBAB",
"currency": "USD"
}'
On top of the search fields, the details row fills in:
address,phone,website,check_in_time,check_out_timeandamenities.location_scoresfrom 1 to 5 foroverall,things_to_do,restaurants,transitandairport_access.rating_distribution, the share of reviews at each star rating.review_topics, such as Location or Breakfast, with positive, negative and total mention counts.other_reviews, the hotel's rating and review count on other review sites.offers, one per booking site, withseller,price, bookingurl,is_official,is_sponsoredandfree_cancellation_until.
offers is what rate-parity checks need: compare the official offer with the online travel agencies for the same dates. Each request costs 2 credits ($0.01). An unknown hotel_id returns no rows and is still charged. Docs: Google Hotel Details.
Hotel Price Tracker API: Lowest Price by Check-in Date
The Hotel Price Tracker API returns the price calendar behind Google Hotels' date picker as rows. For one hotel you get the lowest price for each check-in night, usually six to eight weeks of dates starting from your check-in.
curl -X POST "https://api.socq.ai/v1/google-hotels/hotel-prices" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"hotel_id": "ChoIyKbJ6puqvPf8ARoNL2cvMTFqNHR2MjczeBAB",
"currency": "USD"
}'
check_in sets the first date of the calendar (tomorrow when omitted); give check_out with it. Each row has an id made of the hotel ID and date, hotel_id, name, check_in, check_out and price. Use it to spot the cheapest nights to travel, chart weekend against weekday pricing, or feed a rate-shopping report. Each request costs 4 credits ($0.02) whatever the number of dates. Docs: Hotel Price Tracker.
A Simple Competitive-Set Workflow
- Search the destination once with
sort_by: "most_reviewed"and pick your competitive set from the results. - Pull Hotel Details for each hotel to compare amenities, location scores, review topics and booking-site offers.
- Run Hotel Price Tracker for each hotel on a schedule and store every row with its
collected_at.
For a set of 10 hotels picked from a default 18-hotel search, one run is 2.7 credits for the search, 20 credits for details and 40 credits for price calendars: 62.7 credits, about $0.31. Prices change, so treat each run as a snapshot. For local business data such as places and reviews on Google Maps, see Google Maps scraper APIs.
FAQ
What is the Google Hotels API?
A set of SocQ endpoints that return Google Hotels data as structured rows: search results for a destination, full details for one hotel, and a nightly price calendar. They are SocQ endpoints, not an official Google product.
Where do I get a hotel_id?
From the id field of Google Hotels search results. The same value works for Hotel Details and Hotel Price Tracker.
Which dates are prices for?
If you send check_in and check_out (YYYY-MM-DD, up to 30 nights), prices are for that stay. Without them, search and details price one night from tomorrow, and the price tracker starts its calendar tomorrow.
Can I get prices in another currency?
Yes. Send a three-letter currency such as EUR. Every price object includes amount, currency and a formatted string such as USD 176.
Am I charged for an invalid hotel_id?
Yes. Hotel Details returns no rows for an unknown hotel_id and is still charged 2 credits, so validate IDs against a recent search first.
GOOGLE HOTELS API
Test the workflow with a public Google Hotels URL
Submit public inputs and receive normalized records with traceable source context.
Explore Google Hotels APIs