POST /api/hopper/hotels
Price: 5 credits
Get a Hopper hotel by its lodging id. Returns the hotel's name, type, star rating, description, coordinates, full address, phone, photos and amenities, plus check-in/check-out times, minimum age, hotel policies, and TripAdvisor guest review score, review count, per-category scores and recent guest reviews.
Get a hotel by lodging id (uuid, from hopper/hotels/search or locations search). Returns name, hotel_type, star_rating, description, coordinates, address, phone, image(s), amenities, check_in_from, check_out_time, minimum_age, policies, review_score, review_count, review_categories and reviews (recent guest comments).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)lodging string required — Hopper lodging id (uuid) (examples: "ea952236-a303-4cd5-ad05-0d9035fc66be"; minLength: 1)@type string (default: "HopperHotelDetail")id string requiredname string nullablehotel_type string nullablestar_rating integer nullabledescription string nullablelatitude number nullablelongitude number nullableformatted_address string nullablecity string nullablestate string nullablecountry string nullableimage string nullableimages array (default: [])amenities array (default: [])phone string nullablecheck_in_from string nullablecheck_out_time string nullableminimum_age integer nullablereview_score number nullablereview_count integer nullablereview_categories array (default: [])@type string (default: "HopperReviewCategory")name string nullablescore number nullablepolicies array (default: [])@type string (default: "HopperHotelPolicy")document_title string nullabletext string nullablereviews array (default: [])@type string (default: "HopperHotelReview")author string nullablescore number nullabledocument_title string nullabletext string nullablecreated_at integer nullable422 — 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 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.