Search hotels around latitude and longitude
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Search for Tripadvisor hotel listings around a coordinate pair for a specified stay. Required query inputs are latitude and longitude as strings plus checkIn and checkOut in YYYY-MM-DD format. Optional inputs cover adults, rooms, childrenAges, pageNumber, currencyCode, priceMin, priceMax, rating, sort and array-based hotel filters. The documented default pageNumber is 1; accepted filter identifiers, rating semantics, sort keys and distance units are not specified. Use coordinates, not a destination geoId, for latitude and longitude. This operation has no observed probe response in the supplied evidence. Its unverified, truncated source example shows hotel cards in data.data, including string id and title, boolean isSponsored and accentedLabel, bubbleRating with string count and numeric rating, and cardPhotos entries with a sizes object containing maxHeight, maxWidth and urlTemplate. It also shows badge, provider, secondaryInfo and nullable display fields. priceForDisplay, priceDetails, priceSummary, strikethroughPrice and primaryInfo are null in that example. The complete envelope is not established, and neither response compatibility with other hotel-search operations nor live prices, bookable inventory or a defined search radius is guaranteed.
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/tripadvisor-data/search-hotels-by-location API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-hotels-by-location?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&latitude=<latitude>&longitude=<longitude>&pageNumber=1'
Query Result
Use Cases
- Prototype a hotel map centered on an event venue, collecting coordinates and stay dates before the user explicitly runs a search.
- Compare hotel-search responses for the same map pin across different checkIn and checkOut values while preserving the coordinate pair.
- Build a configurable coordinate-search form that keeps undocumented filter identifiers unset until valid values have been established.
- Design hotel-card rendering that can handle the example rating and photo fields without assuming non-null prices or confirmed bookability.
- Evaluate distance-related inputs separately before offering a radius selector, since distFrom semantics and distFromMaxDistance units are not documented.
Frequently asked questions
Which inputs are required for a coordinate-based hotel search?
Provide latitude and longitude as coordinate strings, along with checkIn and checkOut in YYYY-MM-DD format. No destination geoId parameter is required by this operation.
Can I supply a destination geoId as latitude?
No. The coordinate examples and this operation's latitude/longitude pair identify a coordinate-based search. Keep destination geoId values separate and pass latitude and longitude coordinates instead.
How do pagination, currency and hotel filters work?
pageNumber is optional and has a documented default of 1. currencyCode can use a value from currency lookup, such as USD. Array filters, rating and sort are available, but their accepted identifiers, scales and ordering rules are not documented here.
Are distFromMaxDistance values measured in kilometers or miles?
The distance units and the meaning of distFrom are not documented in the supplied evidence. Do not assume either unit or offer a fixed-radius guarantee without verifying these inputs.
Has the hotel response format or price availability been verified?
No probe response was recorded for this operation. An unverified, incomplete source example shows data.data hotel cards with rating and photo metadata, but several price fields are null. Treat those fields as illustrative, not as confirmed live offers or a complete schema.