Booking Search Hotels in a Map Area API

Search a viewport with ne_lat, ne_lon, sw_lat, and sw_lon plus a consistent stay and occupancy. Supply checkin_date and checkout_date explicitly: the documented omitted-date defaults are inconsistent for this route and must not define a reproducible stay. Optional price bounds, categories_filter, page, and sort refine the request. The bounding-area response and geographic edge behavior were not live-validated.

API Features

Four-corner viewport inputs Use the northeast and southwest latitude/longitude pairs for a selected map area.

Explicit stay avoids ambiguous defaults Set both dates instead of trusting this route's inconsistent omitted-date documentation.

Viewport budget and category selection Apply the chosen price and category constraints within the map-search context.

Map-edge behavior to verify Inspect actual property locations before claiming strict inclusion at viewport edges.

Live API Demo

GET /api/project/booking/search-by-coordinates-bounding

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/search-by-coordinates-bounding?key=<API_KEY>&ne_lat=52.81924284932163&ne_lon=13.675371073186398&sw_lat=52.17448088314293&sw_lon=13.06239478290081'

curl -X GET 'https://api.opendata-api.com/api/project/booking/search-by-coordinates-bounding?key=<API_KEY>&ne_lat=52.81924284932163&ne_lon=13.675371073186398&sw_lat=52.17448088314293&sw_lon=13.06239478290081'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Evaluate hotel discovery after a traveler pans or zooms an accommodation map.
Compare two neighborhood viewports for the same stay and guest configuration.
Inspect whether properties near viewport edges follow the intended geographic boundaries.
Build a bounded map-search experiment without relying on broken destination suggestions.

Frequently asked questions

Which coordinates define the requested map area?

Pass ne_lat/ne_lon for the northeast corner and sw_lat/sw_lon for the southwest corner. Do not substitute a center coordinate and radius.

Why should both dates be supplied here?

The omitted-date documentation is inconsistent for this route. Explicit check-in and check-out dates prevent an ambiguous stay; its live response was not validated.

Related operations

Guides

View Subscription Plans →