/skyscanner/stays/search

POST /api/skyscanner/stays/search

Price: 10 credits

Search Skyscanner hotels for a destination (by place entity id) for a check-in/check-out date range, guest and room count. Returns ranked hotels with name, star rating, guest review score and count, the cheapest nightly and total price (with and without taxes and any discount), distance to a nearby landmark, full address, postcode, neighbourhood and exact coordinates, photos and a link to the hotel page. The destination is a Skyscanner place entity id (resolve it via the places autosuggest).

How to use it

Search hotels for a destination entity_id over a checkin_date..checkout_date range for adults, children_ages and rooms. Returns ranked hotels with id, name, stars, review_score, review_count, review_label, rating_provider, image(s), price (cheapest per night), price_total, price_with_taxes, price_without_discount, discount_percentage, currency, distance, address, postcode, location_text (neighbourhood), latitude, longitude and url. Resolve entity_id via the places autosuggest.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• entity_id string required — Destination place entity id (examples: "27544008"; pattern: ^\d+$)
• checkin_date string required — Check-in date (format: date; examples: "2026-08-15")
• checkout_date string required — Check-out date (format: date; examples: "2026-08-16")
• 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)
• count integer required — Max number of hotels to return (min: 1)

Response

• @type string (default: "SkyscannerStay")
• id string required
• name string nullable
• stars integer nullable
• review_score number nullable
• review_count integer nullable
• review_label string nullable
• rating_provider string nullable
• image string nullable
• images array (default: [])
• price number nullable
• price_total number nullable
• price_with_taxes number nullable
• price_without_discount number nullable
• discount_percentage integer nullable
• currency string nullable
• distance string nullable
• address string nullable
• postcode string nullable
• location_text string nullable
• latitude number nullable
• longitude number nullable
• url 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 — Destination not found or no hotels 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.

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.