Identify a property by name and address
Look up a hotel by name and place, confirm the exact property by its mailing address, then reuse the token.
Overview
You get | A Google Hotels property token confirmed by the property’s mailing address and phone — the two fields the search card omits, so you never target the wrong “Hilton” in a city with six of them. |
Calls | POST/v1/hotels/resolve (search + addresses in one call) or POST/v1/hotels/property for a token you already have |
Cost | 12 credits for resolve (one search page plus up to three address lookups); 3 credits for details |
Reuse | The token feeds /v1/calendar, /v1/offers, /v1/hotels/reviews and the SearchAPI routes |
The destination search (POST/v1/hotels/search) returns each property’s property_token but not its mailing address — Google omits it from the search card. These two calls close that gap.
Resolve with addresses
q is the hotel name plus a city, region or country (the gl market biases the search). The answer lists the top candidates, each with its token, name, rating, and — fetched from the details record — the mailing address and phone.
curl -X POST "https://api.scrapercompany.com/v1/hotels/resolve" \
-H "x-api-key: $SCRAPERCOMPANY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q":"Hilton Chicago","gl":"us","limit":3}'The answer:
{
"search_parameters": {
"q": "Hilton Chicago",
"gl": "us",
"hl": "en",
"currency": "USD",
"limit": 3
},
"location": "Chicago",
"next_page_token": null,
"properties": [
{
"property_token": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ",
"name": "Hilton Chicago",
"rating": 4.3,
"reviews": 10999,
"type": "hotel",
"address": "720 S Michigan Ave, Chicago, IL 60605, United States",
"phone": "+1 312-922-4400"
},
{
"property_token": "ChgImtDg_rW5k8iWARoLL2cvMXRzamQ4NncQAQ",
"name": "Hilton Chicago/Magnificent Mile Suites",
"rating": 4.2,
"reviews": 2808,
"type": "hotel",
"address": "540 N Michigan Ave, Chicago, IL 60611, United States",
"phone": "+1 312-661-0640"
}
]
}Details for one token
When you already hold a token — from a search, a stored mapping, or a colleague — this returns the same address-bearing record for it. Use it to confirm a match before pricing.
curl -X POST "https://api.scrapercompany.com/v1/hotels/property" \
-H "x-api-key: $SCRAPERCOMPANY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"property_token":"ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ","currency":"USD"}'{
"type": "hotel",
"property_token": "ChUIoben2Mv6-CYaCi9tLzA3czVwbjQQAQ",
"name": "Hilton Chicago",
"data_id": "0x880e2c99242c7a2f:0x4de3d4bb09dba1",
"description": "Modern lodging with a restaurant & an indoor pool, plus free WiFi & an airport shuttle.",
"gps_coordinates": {
"latitude": 41.8722592,
"longitude": -87.624696
},
"country": "US",
"address": "720 S Michigan Ave, Chicago, IL 60605, United States",
"phone": "+1 312-922-4400",
"check_in_time": "3:00 PM",
"check_out_time": "11:00 AM",
"hotel_class": "3-star hotel",
"extracted_hotel_class": 3,
"rating": 4.3,
"reviews": 10999,
"reviews_histogram": {
"1": 596,
"2": 428,
"3": 880,
"4": 2607,
"5": 6488
},
"amenities": [
"Breakfast ($)",
"Free Wi-Fi",
"Indoor pool",
"Parking ($)"
]
}Store the token
The token is stable: resolve once during onboarding, store the row (token, name, address, phone) and reuse the token for every later call. Feed it to:
Nightly rates, up to 330 nights per call | |
Per-seller offers for one night | |
Guest reviews, mixed by provider | |
One explicit stay window |