Look Up Destination Hotels for Geographic Comparison
View all Skyscanner Flights & Travel Search endpoints →Request the documented destination hotel lookup intended for geographic display using entityId and ordered future checkIn/checkOut dates. Optional adults and currency supply stay context. Despite its name, this operation accepts no arbitrary latitude, longitude, radius or bounding-box parameter. Hotel search was observed to expose coordinates.lat/lng, but this separate operation's response fields and coverage have not been independently verified; confirm coordinate availability in its actual payload before using it. Calculate landmark or transit proximity in your own application when needed, and never interpret descriptive neighborhood distance strings as numeric meters. Returned candidates are not guaranteed to represent all nearby inventory.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/skyscanner/hotels-get-nearby-map API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/hotels-get-nearby-map?key=<API_KEY>&entityId=<entityId>&checkIn=<checkIn>&checkOut=<checkOut>¤cy=USD'
Query Result
Use Cases
- Prepare destination hotel coordinates for a geographic accommodation selector after validating the actual payload.
- Compare candidate hotel positions with independently sourced transit stops using application-side distance calculations.
- Keep stay dates attached to location-focused accommodation candidates instead of showing them as undated, universally available properties.
- Use separate geographic logic to shortlist hotels near a landmark without inventing a radius or bounding-box query parameter for this endpoint.
Frequently asked questions
Can I search nearby hotels using arbitrary coordinates and a radius?
No such inputs are exposed. This operation accepts destination entityId, stay dates and optional adults/currency, not latitude, longitude, radius or a bounding box. Select a hotel destination rather than assuming arbitrary coordinate search from the operation's name.
How do I obtain hotel coordinates and calculate landmark distance?
Hotel search was observed to provide coordinates.lat/lng, but this separate operation's actual fields remain unverified. Check its payload before using coordinates, then calculate distances to independently sourced landmark or transit coordinates in your application. Descriptive neighborhood distance text is not meters, and returned candidates are not necessarily all nearby hotels.