Redfin Sold Comps Scraper — ARV & Comp Analysis | $1.50/1K
Pricing
from $5.00 / 1,000 sold listings
Redfin Sold Comps Scraper — ARV & Comp Analysis | $1.50/1K
Pull only sold-listing comps from Redfin by city, ZIP, county, or URL — price, beds, baths, sqft, lot size, year built, and days-on-market for closed sales. Built for house-flippers, wholesalers, and appraisers doing ARV and comp analysis, not active listings.
Pricing
from $5.00 / 1,000 sold listings
Rating
0.0
(0)
Developer
Iakov Iudin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
12 hours ago
Last modified
Categories
Share
This is the sold-comps-only edition of the Redfin scraper: statusFilter is locked to sold closed sales for after-repair value (ARV) and comparable-property analysis. It accepts the same locations and direct Redfin URLs as the base actor and is built for real-estate investors, house flippers, wholesalers, and appraisers analyzing recently sold comps.
Redfin Sold Comps Scraper — ARV & Comp Analysis | $1.50/1K | No Proxy
For real-estate investors, house flippers, wholesalers, and appraisers who need Redfin's recently sold comps data for After-Repair-Value (ARV) and comparable-property analysis without spinning up proxies or parsing HTML.
Pay per property: $1.50 per 1,000 properties — charged only for results delivered.
Scrape Redfin recently sold listings by city, ZIP code, county, or neighborhood. Returns structured property data — closed price, beds, baths, square footage, lot size, year built, days on market, GPS coordinates, and more. Powered by Redfin's internal stingray JSON API for reliable, fast extraction.
Why use this actor?
- Built for ARV & Comps —
statusFilteris permanently locked to closed/sold sales; perfectly tuned for comparable-property analysis - No proxy required for most US regions — the API returns JSON directly
- Fast and reliable — structured JSON endpoint, no HTML parsing fragility
- Rich data — 20+ fields per property including remarks, closing status, and coordinates
- Flexible input — city, ZIP, county, neighborhood, or full Redfin search URL
- Pay per result — only pay for properties you actually receive
What data do you get?
| Field | Description |
|---|---|
property_id | Redfin property ID (stable) |
address | Street address |
city, state, zip | Location |
price | Closed/sold price in USD |
beds | Bedrooms |
baths | Bathrooms (supports half-baths) |
sqft | Interior square footage |
lot_size | Lot size in square feet |
year_built | Year of construction |
property_type | house / condo / townhouse / multi-family / land / other |
status | sold |
days_on_market | Days on market before closing |
latitude, longitude | GPS coordinates |
url | Direct Redfin listing URL |
parse_confidence | Data quality score (1.0 = perfect) |
How to use
- Go to redfin.com and navigate to a city, ZIP code, county, or neighborhood (locations and direct Redfin URLs work the same as the base Redfin scraper)
- Copy the URL from your browser's address bar
- Paste it into the Locations input field
Example URLs:
https://www.redfin.com/city/30818/TX/Austinhttps://www.redfin.com/zipcode/78701https://www.redfin.com/county/1361/TX/Travis-Countyhttps://www.redfin.com/neighborhood/48430/CA/San-Francisco/Noe-Valley
You can scrape multiple locations in one run by adding multiple URLs.
Output sample
{"property_id": "55823410","address": "2107 Nueces St","city": "Austin","state": "TX","zip": "78705","price": 625000,"beds": 3,"baths": 2.0,"sqft": 1850,"lot_size": 5400,"year_built": 1978,"property_type": "house","status": "sold","days_on_market": 12,"latitude": 30.2843,"longitude": -97.7407,"url": "https://www.redfin.com/TX/Austin/2107-Nueces-St-78705/home/55823410","parse_confidence": 1.0,"warnings": []}
Pricing example
| Run size | Cost |
|---|---|
| 100 properties | ~$0.15 |
| 1,000 properties | ~$1.50 |
| 10,000 properties | ~$15.00 |
FAQ
Do I need a Redfin account or proxy? No account. No proxy required for most US regions — the stingray JSON API is open. Configure Apify proxy in Advanced options only if you hit blocks.
What output formats are available? JSON, CSV, Excel, XML — all via Apify dataset download or API.
Do I need to filter for sold properties manually?
No — this actor is hardcoded to only pull closed/sold sales for ARV and comparable-property analysis. The statusFilter is permanently locked to sold.
What if a location returns empty results? The actor logs the error, skips the location, and continues. Empty locations push no records and charge nothing.
Why this actor vs. competitors
| Feature | This actor | epctex/redfin-scraper ($2/1K) | Typical Redfin HTML scraper |
|---|---|---|---|
| Internal stingray JSON API | Yes | No (HTML) | No |
| parse_confidence | Yes | No | No |
| Days on market field | Yes | Rarely | No |
| Multiple locations per run | Yes | Single URL | Single URL |
| Dedicated to Sold comps | Yes | No | No |
| Proxy required | No (most regions) | Yes | Often yes |
Key differentiators: lot_size, year_built, and days_on_market on every property. Designed specifically for investors and appraisers doing ARV analysis, ensuring only closed-sale data is extracted without extra configuration.
parse_confidence
Every record includes parse_confidence (1.0 = all fields present). Records with parse_confidence < 0.8 have degraded data — inspect the warnings array.
Use with AI agents (MCP)
Tag: MCP_SERVERS. Returns flat JSON — plug directly into LangChain agents, n8n nodes, or Make scenarios without transformation.
{"mcpServer": "https://mcp.apify.com/?tools=bovi/redfin-sold-comps-tracker"}
Proxy
No proxy required for most US regions. If you encounter blocks, configure an Apify proxy in the Advanced options section.
Cost
Pay-Per-Event (PPE) pricing:
| Event | Price |
|---|---|
property-item | $1.50 / 1,000 properties |
Default run fetches up to 500 properties.
Integrations
Built for real-estate investors, house flippers, wholesalers, and appraisers pulling structured property comps by city, ZIP, and neighborhood — the JSON/dataset output drops into the tools you already run, no glue code:
- n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
- Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
- MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
- API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.
See all Apify integrations.
Legal
This actor accesses publicly available real estate data from redfin.com. Use responsibly and in accordance with Redfin's Terms of Service. Do not use for mass harvesting or commercial redistribution of listing data.
More scrapers from our toolkit
Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:
- Dubai Property Scraper
- Onthemarket Properties Scraper
- Realtor Scraper
- Rightmove Listings
- Zillow Scraper
- Zoopla Properties Scraper
Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.