Search Recently Sold Homes by Location

View all Redfin Property Data endpoints →

Closed-sale comps around a free-form location (city, ZIP code, school district, address, regionId or Redfin URL). Combine a soldWithin window (7 days to 5 years) with price, size, lot, year-built, pool, financing, HOA, tax, school-rating and score filters to assemble a clean comp set. Results follow the shared homeData listing shape with propertyId, url, beds, baths, sqftInfo, lotSize and addressInfo, so sold rows join directly onto for-sale and detail data.

API Features

Address-anchored comps Center a comp search on a street address or ZIP instead of a pre-resolved region.
Adjustable recency soldWithin windows from 7 days to 5 years balance sample size against market drift.
Attribute-matched filtering Beds, baths, square feet, lot and year-built filters keep comps comparable to the subject home.
Join-friendly rows Sold results carry the same propertyId keys as search and detail endpoints for longitudinal analysis.

Live API Demo

GET /api/project/redfin/location-search-for-sold

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/redfin/location-search-for-sold?key=<API_KEY>&location=New+York%2C+NY%2C+USA'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

How do I look up recent sales near an address?

Pass the address or ZIP as location, pick a soldWithin of 90 or 180, then narrow by beds and size to assemble a comparable set.

How should I choose the soldWithin window?

90 days balances sample size and freshness; for thin markets or long-trend work, widen to 365 days or even 5 years.

Can sold data be aligned with live listings?

Yes. Both share the homeData structure and propertyId keys, so one parser covers both pipelines.

Related operations

Guides

View Subscription Plans →