Search Listings by Market Status
View All Realtor Property Data APIs →Submit location with an optional single status value: for_sale, for_rent or sold. page and pageSize are optional string-valued request inputs on this route; the status default is for_sale. The documented purpose is a shared listing search across these market states, but this endpoint was not live-tested and no response field names were confirmed. Validate each chosen status, returned geography and pagination before unifying production calls behind it. For verified examples, use the dedicated sale, rental and sold searches instead of assuming their contracts are identical to this route.
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/property-search-consumer API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realtor/property-search-consumer?key=<API_KEY>&location=New+York%2C+NY&status=for_sale'
Query Result
Use Cases
- Prototype sale, rent and sold tabs backed by a common search interface only after validating each state.
- Compare candidate identifiers with dedicated search responses for the same location.
- Check whether shared search results retain the fields needed by an existing property-discovery UI.
- Evaluate how market-state changes affect returned counts without combining asking and transaction prices.
Frequently asked questions
Can status contain both for_sale and for_rent?
This contract documents one status value: for_sale, for_rent or sold. Do not transfer comma-separated combinations from a different operation into this input.
Does the shared search return exactly the same fields as dedicated searches?
That is unconfirmed. No response fields were live-verified for this operation. Check each market status independently against dedicated searches before sharing a field mapping.
Are page and pageSize numeric or string inputs here?
This operation preserves the documented string types for page and pageSize. Other searches can use numeric parameters; keep route-specific types and verify actual page transitions.