Redfin Scraper — Real Estate Listings by City & ZIP | $1.50/1K | No Proxy

For investors, agents, and data teams who need Redfin's clean JSON API data without spinning up proxies or parsing HTML.

Pay per property: $1.50 per 1,000 properties — charged only for results delivered.

Scrape Redfin real estate listings by city, ZIP code, county, or neighborhood. Returns structured property data — 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?

• 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, 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	Listing 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	active / coming_soon / pending / sold / etc.
days_on_market	Days listed (DOM)
latitude, longitude	GPS coordinates
url	Direct Redfin listing URL
parse_confidence	Data quality score (1.0 = perfect)

How to use

1. Go to redfin.com and navigate to a city, ZIP code, county, or neighborhood
2. Copy the URL from your browser's address bar
3. Paste it into the Locations input field

Example URLs:

https://www.redfin.com/city/30818/TX/Austin
https://www.redfin.com/zipcode/78701
https://www.redfin.com/county/1361/TX/Travis-County
https://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": 649000,
  "beds": 3,
  "baths": 2.0,
  "sqft": 1850,
  "lot_size": 5400,
  "year_built": 1978,
  "property_type": "house",
  "status": "active",
  "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
+ sold comp (ARV)	+$1.00/1K

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.

Can I pull sold comps for ARV analysis? Yes — set statusFilter to sold to get recently closed sales. Sold comps charge both the base event and the sold-listing premium event.

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
Sold comps (statusFilter=sold)	Yes	No	No
Proxy required	No (most regions)	Yes	Often yes

Key differentiators: lot_size, year_built, and days_on_market on every property. Sold comps via statusFilter=sold return closed-sale data that Zillow charges for — investors use this for ARV analysis.

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-scraper"
}

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 (primary)	$1.50 / 1,000 properties
sold-listing (premium)	$1.00 / 1,000 sold comps

Sold comps (statusFilter=sold) charge both events — the base listing event plus the sold-comp premium. Default run fetches up to 500 properties.

Integrations

Built for real-estate investors and data teams pulling structured property listings 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.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.