POST /api/hopper/hotels/rooms
Price: 20 credits
Get the available rooms and rates for a Hopper hotel over a check-in/check-out date range for a given number of adults, children, rooms and pets. Returns each room type with its name, description, photos, bed types, amenities and maximum occupancy, along with its bookable rates (meal plan, cancellation policy, nightly and total price and currency).
Get rooms and rates for a hotel by lodging id over check_in..check_out for adults/children_ages/rooms/pets. Each room has id, name, description, image(s), bed_types, amenities, max_adults and rates (meal_plan, cancellation_policy, nightly_price, total_price, currency, is_cheapest).
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: "86adcb69-dc28-4ef3-9d27-e50a451fc230"; minLength: 1)check_in string required — Check-in date (format: date; examples: "2026-08-15")check_out string required — Check-out date (format: date; examples: "2026-08-17")adults integer — Number of adult guests (default: 2; min: 1; max: 16)children_ages array — Ages of child guests (0-17) (default: [])rooms integer — Number of rooms (default: 1; min: 1; max: 8)pets integer — Number of pets (default: 0; min: 0; max: 8)@type string (default: "HopperRoom")id string nullablename string nullabledescription string nullablemax_adults integer nullablemax_children integer nullableimage string nullableimages array (default: [])bed_types array (default: [])amenities array (default: [])rates array (default: [])@type string (default: "HopperRoomRate")rate_id string nullablemeal_plan string nullablecancellation_policy string nullablepayment_schedule string nullableis_cheapest boolean nullablenightly_price number nullabletotal_price number nullablereference_price number nullablediscount_percentage number nullablecurrency string 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 or no rooms available for the given dates 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.