Listing Summary by Address
View all Redfin Property Data endpoints →Lightweight listing lookup by address slug or URL (e.g. 5065-Eloy-St-78521, or the full listing link). When several properties share an address, pass the optional propertyId to pin the exact one. Use this as a cheap existence and identity check before spending a full v2-details call: confirm the address maps to a listed property and capture its propertyId for the heavier detail, estimate and history endpoints.
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/redfin/details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/redfin/details?key=<API_KEY>&location=<location>'
Query Result
Use Cases
- Resolve a street address into a listing summary card for chat or voice assistants.
- Verify whether an address currently has an active listing before deeper detail calls.
- Disambiguate duplicate addresses using propertyId for precise detail retrieval.
- Validate user-submitted addresses in a lead form before enrichment.
Frequently asked questions
Can I look up a property knowing only the address, with no ID?
Yes — that is exactly what this endpoint is for: address slug or link in, summary plus propertyId out.
When should I use it instead of the v2 detail endpoint?
It is cheaper for existence checks and bulk pre-screening; once a target is confirmed, switch to the v2 detail endpoint for the complete document.
What if several properties share one address?
Pass the optional propertyId to pin the target; without an ID, run the address lookup once and confirm the exact record from the response.