Redfin Property Details API - Full Listing JSON by ID or URL

One call for the complete property payload. The location parameter accepts a propertyId (verified: 40775351), a short path (/NY/Brooklyn/8707-Avenue-B-11236/home/40775351), a full Redfin URL, a street address or an address slug. Verified responses return message 'Successful' and a large data object: initialInfo (propertyId, listingId, marketId, latLong, hasAvm, preloadImageUrls), aboveTheFold.addressSectionInfo.priceInfo (current price amount) and the remaining detail sections in a single ~267 KB document. This is the fastest way to resolve a pasted link into propertyId/listingId keys for the focused detail endpoints. A nonexistent propertyId currently surfaces as a bare HTTP 500, so treat 5xx as the not-found signal for this route.

API Features

Five input forms propertyId, short path, full URL, street address or address slug all resolve through one parameter.

Everything in one payload initialInfo, aboveTheFold and the remaining detail sections arrive together, saving a dozen focused calls.

ID resolution Returns canonical propertyId and listingId that key every other detail endpoint in this project.

Verified price context Observed responses include the current priceInfo amount plus latLong and AVM availability flags.

Live API Demo

GET /api/project/redfin/v2-details

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/redfin/v2-details?key=<API_KEY>&location=40775351'

curl -X GET 'https://api.opendata-api.com/api/project/redfin/v2-details?key=<API_KEY>&location=40775351'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Render complete property detail pages in your own app from a single call.
Enrich a lead list of addresses with beds, baths, price, latLong and status in one pass.
Snapshot full property payloads for a longitudinal listing-archive research dataset.
Resolve a pasted Redfin link into propertyId and listingId keys for downstream detail endpoints.

Frequently asked questions

Which endpoints does an investment-analysis pipeline need?

A common chain is: search for candidates, this endpoint for the full property file, the estimate endpoint for the model value, sold search for comps, and the climate and schools endpoints for risk and district context. All share propertyId/listingId keys.

Which has fuller data, a Zillow API or a Redfin API?

Neither platform runs a public official API. On the Redfin side, for-sale, rent and sold search plus estimate, climate-risk and tour-heat signals give broad coverage; validate your target fields empirically — this endpoint returns the whole document in one call, which makes coverage easy to assess first.

What happens if I pass a nonexistent ID?

This route currently returns a bare HTTP 500 for an unknown propertyId instead of a structured 404. Handle 5xx separately from gateway business statuses and treat it as the not-found signal.

Related operations

Guides

View Subscription Plans →

Full Property Details (Address, URL or ID)