/google/hotels

POST /api/google/hotels

Price: 5 credits

Get full Google Hotels details by hotel feature ID. Includes star class, rating, address, price.

How to use it

Get full details of a hotel by its feature_id (hex '0x..:0x..'). Returns name, address, coordinates, phone, star class, guest rating, review count, review aspects guests mention, description, photos, and starting nightly price.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• feature_id string required — Hotel feature ID in hex form '0x..:0x..' (examples: "0x89c28aad4f6a9ce5:0xa4793816b9bcb218"; minLength: 1)

Response

• @type string (default: "GoogleHotel")
• feature_id string required
• name string required
• token string nullable
• property_type string nullable
• hotel_class integer nullable
• latitude number nullable
• longitude number nullable
• address string nullable
• phone string nullable
• neighborhood string nullable
• rating number nullable
• review_count integer nullable
• review_summary string nullable
• review_aspects array (default: [])
  • @type string (default: "GoogleHotelReviewAspect")
  • name string required
  • sentiment number nullable
  • positive_count integer nullable
  • negative_count integer nullable
• description string nullable
• image string nullable
• images array (default: [])
• price_from number nullable
• currency string nullable
• place_id string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Hotel not found for the given feature_id. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.