# /hopper/hotels/search

`POST /api/hopper/hotels/search`

Price: 20 credits

Search Hopper stays (hotels and vacation rentals) for a destination place id or a specific set of lodging ids over a check-in/check-out date range, for a given number of adults, children, rooms and pets. Optionally filter by property type, star rating, nightly price range, minimum guest score and free cancellation, and choose the result ordering. Returns each stay with its hotel details (name, type, star rating, description, coordinates, address, photos, amenities), nightly and total price (with any discount), currency, meal plan, cancellation and payment highlights, guest review score and count, and a shop token for room rates. Resolve place_id via the locations search (kind=stay).

## How to use it

Search stays by place_id (Google place id from locations search kind=stay) OR explicit lodging_ids, for check_in..check_out, adults/children_ages/rooms/pets. Filters: property_type, star_ratings, price_min/max, min_guest_score (0-1), free_cancellation, sort. Each result has hotel (nested), nightly_price, total_price, discount, currency, meal_plan, free_cancellation, review_score/count and shop_token (for hopper/hotels/rooms).

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `place_id` (string, nullable) — Google place id of the destination (resolve via locations search, kind=stay). Provide either place_id or lodging_ids (examples: "ChIJ0X31pIK3voARo3mz1ebVzDo")
- `lodging_ids` (array) — Specific Hopper lodging ids to price. Provide either place_id or lodging_ids (default: [])
- `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)
- `property_type` (string) — Restrict to hotels, vacation rentals (homes), or all stay types (default: "all"; one of: "all", "hotel", "vacation_rental")
- `star_ratings` (array) — Keep only these star ratings (1-5) (default: [])
- `price_min` (number, nullable) — Minimum nightly price (min: 0)
- `price_max` (number, nullable) — Maximum nightly price (min: 0)
- `min_guest_score` (number, nullable) — Minimum guest review score (0-1 scale, e.g. 0.8 = 8/10) (min: 0; max: 1)
- `free_cancellation` (boolean) — Keep only stays with free cancellation (default: false)
- `sort` (string) — Result ordering (default: "recommended"; one of: "recommended", "price_low", "price_high", "rating")
- `count` (integer, required) — Max number of stays to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "HopperHotelOffer")
- `hotel` (object, nullable)
  - `@type` (string) (default: "HopperHotel")
  - `id` (string, required)
  - `name` (string, nullable)
  - `hotel_type` (string, nullable)
  - `star_rating` (integer, nullable)
  - `description` (string, nullable)
  - `latitude` (number, nullable)
  - `longitude` (number, nullable)
  - `formatted_address` (string, nullable)
  - `city` (string, nullable)
  - `state` (string, nullable)
  - `country` (string, nullable)
  - `image` (string, nullable)
  - `images` (array) (default: [])
  - `amenities` (array) (default: [])
- `nightly_price` (number, nullable)
- `total_price` (number, nullable)
- `original_nightly_price` (number, nullable)
- `original_total_price` (number, nullable)
- `discount_percentage` (number, nullable)
- `currency` (string, nullable)
- `meal_plan` (string, nullable)
- `free_cancellation` (boolean, nullable)
- `pay_now` (boolean, nullable)
- `pay_at_check_in` (boolean, nullable)
- `is_preferred` (boolean, nullable)
- `review_score` (number, nullable)
- `review_count` (integer, nullable)
- `shop_token` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

Destination not found or no stays available for the given dates

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.