Redfin Detail Scraper

Scrape publicly available property details from Redfin.com at scale: list price, Redfin Estimate, beds, baths, lot size, listing status, comparables, and nearby points of interest, all as structured JSON. Feed in property URLs, plain addresses, or a whole dataset from Redfin Search Scraper, and get real estate data ready for market research, valuation models, and portfolio tracking. Runs on the Apify platform with scheduling, webhooks, proxy rotation, and integrations included.

What data can you get?

Field group	What you get
🏠 Main house info	Address, listing URL, MLS ID, listing type, primary photo, coordinates, listing broker
💰 Price and Redfin Estimate	List price, last sold price, Redfin Estimate (AVM), price per sqft
📐 Property attributes	Beds, baths, sqft, lot size, year built, listing status, days on market
🛋️ Amenities	Interior, exterior, HOA, utilities, and school info
🏘️ Comparables	Nearby recently sold homes
📍 Points of interest	Nearby restaurants, shops, transit, parks
🧾 Listing history	Listing events and prior sale records

You can pass in Redfin property detail URLs, plain-text addresses, or a dataset ID produced by Redfin Search Scraper, and combine all three in a single run.

Use cases

• Real estate market research: build a view of listed pricing, inventory, and days on market across ZIPs, cities, or states.
• Address enrichment: attach property attributes (beds, baths, sqft, year built, Redfin Estimate) to a list of addresses.
• Investor workflows: collect comparables and Redfin Estimates in bulk.
• Valuation models: feed structured property features into pricing or ML models.
• Portfolio tracking: snapshot properties on a schedule and diff over time.
• Chained runs: pipe Redfin Search Scraper output straight into this Actor via searchResultsDatasetId.

Pricing

Redfin Detail Scraper uses pay-per-event pricing. You pay per event, not per compute unit: each scraped listing, each address lookup, and the run start are charged as separate events.

Event	Description
Extracted listing details	One charge per scraped listing
Processed address	One charge per address resolved via Redfin's address lookup
Actor start	Flat charge for starting the run
Addon: Residential proxies	Extra per-result charge when useResidentialProxies is enabled

See the Actor's Pricing tab in Apify Console for current per-event prices.

How to use

1. Click Try for free.
2. Add one or more sources: Redfin Detail URLs, plain Addresses, or a Dataset ID with search scraper results.
3. Optionally enable residential proxies to cut retries on tough runs. The addon adds a fee per result.
4. Click Save & Start.
5. When the run finishes, download results from the Storage tab or pull them via the Apify API.

Input

At least one source is required. You can combine all sources in a single run.

Field	Type	Description
detailUrls	array	Redfin property detail URLs to scrape.
addresses	array	Plain-text US addresses. Each address is resolved via Redfin's address lookup and, if matched, the listing page is processed.
searchResultsDatasetId	string	Dataset ID from a Redfin Search Scraper run. Every URL in that dataset is processed. Default: "".
useResidentialProxies	boolean	Enables residential proxies to reduce retries. Charged separately as an addon event per result. Default: false.

Minimal example input:

{
  "detailUrls": [
    {
      "url": "https://www.redfin.com/AL/Huntsville/4113-Toftoy-Dr-SW-35805/home/125779794"
    }
  ]
}

Output

Each property becomes one dataset item with nested sections that mirror Redfin's listing page. Simplified example:

[
  {
    "mainHouseInfo": {
      "fullStreetAddress": "4113 Toftoy Dr SW, Huntsville, AL 35805",
      "url": "/AL/Huntsville/4113-Toftoy-Dr-SW-35805/home/125779794"
    },
    "avmInfo": {
      "sectionPreviewText": "$186,177 (+$16K since last sold)",
      "priceInfo": { "label": "Last Sold Price" }
    },
    "addressSectionInfo": {
      "homeStatusLabel": "Off Market",
      "yearBuilt": 1958,
      "lotSize": 10018,
      "sqFt": { "value": 1171 },
      "beds": 3
    },
    "scraperInput": "https://www.redfin.com/AL/Huntsville/4113-Toftoy-Dr-SW-35805/home/125779794"
  }
]

The Overview view in the Output tab flattens the most-used fields into a table. Switch to All fields to see the full record. Export the dataset as JSON, CSV, Excel, HTML, or XML.

Tips

• Chain with Redfin Search Scraper: run Redfin Search Scraper over a set of Redfin search URLs, then pass its dataset ID as searchResultsDatasetId here.
• Prefer URLs over addresses: URLs are more reliable. Use addresses only when you don't have URLs; ambiguous addresses can fail to resolve.
• Residential proxies: leave the addon off for a first run. Enable it only if you see elevated retries; it adds a per-result fee.
• Overview vs All fields: the Overview table shows the most-used fields. If a field you need isn't there, switch to All fields or export the full JSON.

Is it legal to scrape Redfin?

Web scraping of publicly available data such as property prices, availability, and street addresses is generally permitted. You're responsible for complying with Redfin's Terms of Use and applicable law in your jurisdiction. Read our blog post on the legality of web scraping to learn more.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Redfin or any of its subsidiaries.

FAQ

Can I run this on a schedule?

Yes. Every Apify Actor supports Schedules, webhooks, and integrations with Zapier, Make, Slack, Google Sheets, LangChain, Airbyte, and more.

What happens if an address can't be resolved?

If Redfin's address lookup finds no exact match, the Actor writes a stub record to the dataset ({ "ok": false, "scraperInput": "<your address>", "error": "..." }) and charges one Processed address event for the lookup. No Extracted listing details charge applies, since no listing page is processed.

Something's broken or missing

Open an issue on the Actor's Issues tab in Apify Console. Custom extraction and enrichment work is available through Apify's custom solutions team.