/expedia/hotels/search

POST /api/expedia/hotels/search

Price: 1 credit

Search Expedia hotels in a destination region by numeric region id and stay dates. Returns hotel cards with id, name, neighborhood, hotel page url, VIP Access flag, hero image and gallery, guest rating with label and review count, and pricing (stay total, nightly price and strikethrough price).

How to use it

Search hotels in an Expedia region. Provide region_id (numeric destination id like 2621 for New York), optional check_in and check_out dates (YYYY-MM-DD; default is a near-future 2-night stay), optional adults, and count. Returns hotel cards with id, name, neighborhood, url, is_vip, image, images, guest_rating, guest_rating_label, review_count, price_total, price_per_night and strikeout_price.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region_id string required — Numeric Expedia region id to search hotels in (a city, neighborhood or area destination) (examples: "2621"; minLength: 1)
• check_in string nullable — Check-in date in YYYY-MM-DD format (examples: "2026-07-10")
• check_out string nullable — Check-out date in YYYY-MM-DD format (examples: "2026-07-12")
• adults integer — Number of adult guests (default: 2; min: 1; max: 14)
• count integer required — Max number of hotels to return (min: 1)

Response

• @type string (default: "ExpediaSearchHotel")
• id string required
• name string nullable
• neighborhood string nullable
• url string nullable
• is_vip boolean (default: false)
• image string nullable
• images array (default: [])
• guest_rating number nullable
• guest_rating_label string nullable
• review_count integer nullable
• price_total string nullable
• price_per_night string nullable
• strikeout_price 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 — The entity was not found, or a precondition failed 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.