Search Properties Within a Map Bounding Box
View all Zillow Real Estate Data API endpoints →Supply north, south, east and west as decimal-degree bounds for a rectangular search area. Although the schema marks these fields optional individually, a meaningful bounded search needs all four. This endpoint uses bounds, not latitude/longitude plus a radius. zoom defaults to 13. status, price, beds, baths, home_type and the documented amenity and affordability filters refine the area; page or cursor controls continuation. The documented result is a property-search collection for the supplied map bounds, with list or map output selected by result_type. No saved live response exists for this route, so exact collection fields, filter enforcement and continuation results are not verified here. Inspect the returned business result and resource identity before importing it. Deduplicate overlapping areas by returned property ID when available, and do not interpret a bounded result set as complete coverage of every home.
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/zillow-real-estate/search-by-coordinates API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/zillow-real-estate/search-by-coordinates?key=<API_KEY>&zoom=13&status=for_sale&page=1&page_size=40&result_type=list&sort=relevance'
Query Result
Use Cases
- Explicit map-area search: request a visible rectangle only after the user chooses to search that area.
- Service-territory inventory study: apply consistent listing filters to a set of bounded geographic areas.
- Adjacent-area comparison: retain each rectangle with its results before deduplicating properties that appear in overlapping bounds.
- Map filter prototyping: evaluate listing density for chosen status and home-type inputs without substituting unsupported radius parameters.
Frequently asked questions
Can I pass a center coordinate and radius?
No radius input is defined. Use north, south, east and west bounds, with zoom if needed. Do not replace the documented rectangle with a diameter or radius request.
Why should I fill all four bounds if they are optional fields?
The schema does not express their joint requirement. All four edges are needed to describe your intended rectangle. Incomplete-bound behavior was not verified.
Was this map-search route live-tested?
No saved live response is available for this route. Its inputs and intended result are documentation-based; verify response shape and filter behavior before production use.