Search Homes for Sale from Coordinates
View All Realtor Property Data APIs →Provide numeric latitude and longitude to evaluate the documented coordinate-based for-sale search. Optional inputs include expandSearchArea, price, rooms, propertyType, sizes, amenities, sort, page and pageSize. The coordinate examples are numeric source examples, not live-verified search locations for this route. No response fields or radius behavior were confirmed. Validate returned geography and each filter before labeling results nearby, and do not assume support for map polygons, bounding boxes or guaranteed distance coverage.
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/realtor/coordinates-search-buy API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realtor/coordinates-search-buy?key=<API_KEY>&latitude=29.27052&longitude=-95.74991'
Query Result
Use Cases
- Evaluate a mobile nearby-for-sale view centered on a user-selected point.
- Prepare a map-center acquisition shortlist and verify each returned property's geography.
- Test how sale-search expansion choices affect observed coverage around one coordinate pair.
- Compare coordinate and city-based sale discovery before choosing a map-search integration.
Frequently asked questions
Were the sample coordinates verified to return nearby sale listings?
No. They are documented numeric examples, not live-tested locations for this operation. Inspect actual addresses or coordinates before describing returned properties as nearby.
Is expandSearchArea a strict search radius?
That is unconfirmed. Expansion options are documented, but boundaries and distance behavior were not tested. Do not promise complete inventory within a specified radius.
Can I submit a map rectangle or polygon?
This contract exposes latitude, longitude and expansion or filter inputs, not a confirmed bounding-box or polygon input. Do not promise geographic query types that are not documented.