/expedia/hotels/offers

POST /api/expedia/hotels/offers

Price: 1 credit

Get the room and rate grid for an Expedia hotel by hotel id (numeric, h-prefixed, or a hotel page URL) for a stay (check-in, check-out and number of adults; a near-future 2-night stay is used when no dates are given). Returns one item per room type with id, name, guest rating, features (size, bed type, occupancy), room images, and a list of rates with displayed price, nightly price, strikethrough price, price qualifier, currency, payment model, refundable flag, cancellation policy, included board/meal and remaining-availability message.

How to use it

Fetch the room/rate grid for one Expedia hotel and stay. Provide hotel (numeric id like 66525849, h-prefixed, or a hotel URL), optional check_in and check_out (YYYY-MM-DD; supply both or neither — the default is a near-future 2-night stay), optional adults, and count. Returns rooms with id, name, rating, features, images and rates (id, price, price_per_night, strikeout_price, price_qualifier, currency, payment_model, is_refundable, cancellation, board, scarcity). Prices are live and change over time.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• hotel string required — Expedia hotel id (numeric or h-prefixed) or a hotel page URL containing it (examples: "66525849", "h66525849", "https://www.expedia.com/x.h66525849.Hotel-Information"; minLength: 1)
• check_in string nullable — Check-in date in YYYY-MM-DD format (format: date; examples: "2026-07-15")
• check_out string nullable — Check-out date in YYYY-MM-DD format (format: date; examples: "2026-07-17")
• adults integer — Number of adult guests (default: 2; min: 1; max: 14)
• count integer required — Max number of rooms to return (min: 1)

Response

• @type string (default: "ExpediaRoom")
• id string required
• name string nullable
• rating number nullable
• features array (default: [])
• images array (default: [])
• rates array (default: [])
  • @type string (default: "ExpediaRoomRate")
  • id string required
  • price string nullable
  • price_per_night string nullable
  • strikeout_price string nullable
  • price_qualifier string nullable
  • currency string nullable
  • payment_model string nullable
  • is_refundable boolean nullable
  • cancellation string nullable
  • board string nullable
  • scarcity 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 or no rooms available for the given hotel id and stay 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.

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.