Listing Detail from a Shared URL
View all Redfin Property Data endpoints →Turn a shared Redfin listing link into structured property data. Pass the full URL exactly as copied from a browser, email or message and receive the listing's detail record. Useful whenever a user supplies the property as a link rather than an address or ID: bots, bookmark importers and watchlist tools can unfurl links into price, beds, baths and photo previews without parsing the URL themselves.
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/detail-by-url API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/redfin/detail-by-url?key=<API_KEY>&url=https%3A%2F%2Fwww.redfin.com%2FNY%2FBrooklyn%2F8707-Avenue-B-11236%2Fhome%2F40775351'
Query Result
Use Cases
- Turn links pasted by users into structured listing data inside a messaging bot.
- Build a bookmark importer that converts saved listing URLs into a tracked watchlist.
- Unfurl listing URLs in a team chat tool with price, beds and photo previews.
- Ingest agent newsletters' listing links into a comparison spreadsheet automatically.
Frequently asked questions
How do I turn a Redfin listing link into structured JSON?
Pass the full link as-is in the url parameter to get that listing's structured detail; for the complete file, take the resolved propertyId to the v2 detail endpoint.
Do links with tracking parameters work?
Prefer the canonical link copied from the browser address bar; heavily tracked links may be normalized, so retry with the canonical form on failure.
How is this different from the search-URL replay endpoint?
This endpoint resolves a single-listing detail link; for search-results page links use the search-by-URL endpoint.