Search Hotels by Destination and Stay Dates

View all Skyscanner Flights & Travel Search endpoints →

Search accommodation using entityId from hotel destination autocomplete and future checkIn/checkOut dates in YYYY-MM-DD format, with checkOut later than checkIn. Optional adults, rooms, currency and market define the stay context. The observed Paris response contains destinationName, total and hotels; each hotel includes hotelId, name, stars, numeric rating, reviewCount, price.amount/currency, images as URL strings, amenities, url, coordinates.lat/lng and distance as a descriptive neighborhood string. Do not treat rating as a nested score object, image strings as caption objects or distance as numeric meters. The returned list can be only a subset of total, and this operation exposes no pagination parameter. The search price's nightly-versus-total basis, taxes and room terms are not established by these fields alone; verify them before comparing final costs or directing users to a booking link.

API Features

Destination-and-stay search Required destination entityId and ordered checkIn/checkOut dates anchor a stay-specific hotel query rather than a free-text property directory.
Numeric guest-rating fields The tested hotels have a numeric rating, separate reviewCount and stars; preserve their distinct meanings in comparison cards.
Image strings and amenity lists Observed images are URL strings and amenities are list values, allowing a property shortlist without assuming a nested photo schema.
Coordinates with descriptive distance coordinates.lat/lng support geographic context, while distance contains neighborhood text rather than a measurable distance in meters.
Finite hotel-result subset The tested list contained fewer properties than total; it is not a complete inventory export and has no exposed page parameter.

Live API Demo

GET /api/project/skyscanner/hotels-search-hotels

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/hotels-search-hotels?key=<API_KEY>&entityId=<entityId>&checkIn=<checkIn>&checkOut=<checkOut>&adults=2&rooms=1&currency=USD&market=US'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

How do I search hotels by destination, stay dates, adults and rooms?

Select a destination with hotel autocomplete and use its entityId, then supply future checkIn and checkOut dates with checkout later than check-in. Optionally set adults, rooms, currency and market. A destination entityId is not hotelId; property-specific follow-ups use hotelId from the returned hotels.

How should hotel ratings, images, distance and prices be interpreted?

In the tested response, rating is numeric, images are URL strings, distance is neighborhood text rather than meters, and coordinates use lat/lng. price.amount alone does not establish nightly versus whole-stay pricing, taxes or terms; verify these before comparing final costs. The list can be a subset of total, and no search pagination input is exposed.

Related operations

Guides

View Subscription Plans →