Search Properties in a Viewport
View all Booking.com Hotel & Travel Data endpoints →Search the documented property workflow with required northeast/southwest coordinates and both stay dates. Optional bed_rooms, bath_rooms, adults, children_age, rooms, currency, language, price bounds, page, page_size, sort, and categories-filter refine the request. Note this route uses bed_rooms/bath_rooms rather than the location list's min_bedrooms/min_bathrooms. Its viewport response, filter behavior, and page-size enforcement were not live-validated.
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/booking/properties-list-search-by-geo API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-list-search-by-geo?key=<API_KEY>&checkin_date=<checkin_date>&checkout_date=<checkout_date>&ne_lat=40.92914125945875&ne_lon=-73.78078299183483&sw_lat=40.60515465622656&sw_lon=-74.0320952476942'
Query Result
Use Cases
- Evaluate neighborhood property discovery inside a traveler-selected map viewport.
- Compare accommodation coverage in adjacent map areas for a fixed family stay.
- Test bedroom and bathroom inputs in the geo-oriented property family.
- Validate map paging behavior before implementing a bounded property collector.
Frequently asked questions
Are bed_rooms and min_bedrooms interchangeable?
No alias is documented. This route exposes bed_rooms and bath_rooms, while other property lists expose min_bedrooms and min_bathrooms. Preserve the exact names.
Can I omit the viewport or dates?
No. ne_lat, ne_lon, sw_lat, sw_lon, checkin_date, and checkout_date are required. The actual result schema and geographic behavior were not live-validated.