Redfin Properties Scraper — Homes for Sale

Scrape Redfin homes for sale from any city, neighborhood or county search URL: prices, beds, baths, square footage, lot size, year built, days on market, listing remarks and exact coordinates as clean JSON. No API key, no login, no proxy required.

Why use this Actor?

• Real Redfin data, not a mirror — pulls from Redfin's own listing data (Stingray API) with the same fields you see on the site.
• No login or API key — works straight from Apify's datacenter IPs; no residential proxy budget needed.
• Deep listing detail — 25+ structured fields per property, including agent remarks, listing tags, HOA dues and new-construction flags.
• Market-scale — up to 350 listings per search URL; feed it a whole city or a portfolio of markets in one run.
• Portfolio-friendly — pass multiple city/neighborhood URLs in a single run and get one item per listing with the source search URL attached.

What you get per listing

Field	Description
price, pricePerSqFt	Listing price and price per square foot (USD)
hoaPerMonth	HOA dues per month
sqFt, lotSizeSqFt	Interior and lot area
beds, baths, yearBuilt	Core home facts
daysOnMarket, mlsStatus	Market signals (Active, Coming Soon, …)
propertyType	House, Condo, Townhouse, …
streetAddress, unitNumber, city, state, zip, neighborhood	Full location
latitude, longitude	Exact coordinates
listingRemarks, listingTags	Agent description and highlight tags
isNewConstruction, numPhotos	Listing extras
propertyUrl, propertyId, mlsId	Identifiers for de-duplication and lookups

Input

{
  "startUrls": [
    "https://www.redfin.com/city/30818/TX/Austin",
    "https://www.redfin.com/city/15914/OR/Portland"
  ],
  "maxListingsPerUrl": 100
}

Field	Type	Default	Description
startUrls	array of strings	—	Redfin city, neighborhood or county search URLs. Copy from your browser after searching on redfin.com. Required.
maxListingsPerUrl	integer	100	Max listings per URL (up to 350).

A note on URLs: use city (redfin.com/city/…), neighborhood (redfin.com/neighborhood/…) or county search pages. ZIP-code URLs are not supported — Redfin maps them through an internal region ID that the search page does not expose, so point the Actor at the city URL instead.

Output (one item per listing)

{
  "searchUrl": "https://www.redfin.com/city/30818/TX/Austin",
  "propertyId": "31246916",
  "mlsStatus": "Active",
  "propertyUrl": "https://www.redfin.com/TX/Austin/3501-Mount-Bonnell-Rd-78731/home/31246916",
  "price": 9925000,
  "pricePerSqFt": 1696,
  "hoaPerMonth": 0,
  "sqFt": 5851,
  "lotSizeSqFt": 43560,
  "beds": 5,
  "baths": 6,
  "yearBuilt": 2026,
  "daysOnMarket": 1,
  "propertyType": "House",
  "streetAddress": "3501 Mt Bonnell Rd",
  "city": "Austin",
  "state": "TX",
  "zip": "78731",
  "neighborhood": "Highland Park West",
  "latitude": 30.3173612,
  "longitude": -97.7738244,
  "isNewConstruction": false,
  "listingRemarks": "Lake Austin views from every level...",
  "listingTags": ["LAKE AUSTIN VIEWS", "COMPLETE PRIVACY"],
  "numPhotos": 42
}

A worked example: the Austin city URL above returns active homes in that market — each item carries the full address, live price, beds/baths, interior and lot square footage, days on market and the Redfin property URL for de-duplication.

Use cases

• Real-estate investing — screen markets by price per sqft, days on market and new-construction supply
• Lead generation — feed fresh listings into CRMs, alerts and buyer-match workflows
• Market analysis — track inventory, pricing trends and neighborhood mix across cities over time
• Data products — power dashboards, valuation models and reports with structured listing data
• Relocation research — compare what a budget buys across target cities in one run

Run it from the API

curl -X POST "https://api.apify.com/v2/acts/darknezz~redfin-properties-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":["https://www.redfin.com/city/30818/TX/Austin"],"maxListingsPerUrl":50}'

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("darknezz/redfin-properties-scraper").call(
    run_input={"startUrls": ["https://www.redfin.com/city/30818/TX/Austin"], "maxListingsPerUrl": 50}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["price"], item["beds"], item["address"])

Scheduling: run the Actor on a schedule to track a market's inventory over time — new listings, price cuts and days-on-market trends become a time series.

Pricing

Pay per event: you are charged a small fee per property listing scraped, plus Apify's standard compute costs. No subscription required.

FAQ

Does it need a login or residential proxy? No. The Actor uses Redfin's public search data from datacenter IPs, which works without a proxy budget.

Why isn't my ZIP-code URL returning results? ZIP codes aren't a Redfin search region — the site internally maps them to a region ID that isn't present in the URL. Use the corresponding city URL (find it by searching the city on redfin.com and copying the address-bar URL).

How many listings can I get? Up to 350 per search URL. For bigger markets, split the run across multiple city/neighborhood URLs or raise maxListingsPerUrl.

Are sold homes included? No — the Actor returns active listings from the search page. Set the search on redfin.com to "Sold" and use that URL if you need sold data.

What if a URL is invalid or a market has no listings? That URL is reported as skipped while the rest of the run continues — one bad link never wastes the batch.

Can I track price changes over time? Yes — run on a schedule and join items by propertyId; each run captures the current price, so price cuts show up as deltas between snapshots.

Limitations

• Active listings only — sold/off-market history is not returned (use Redfin's "Sold" search URL if you need it).
• ZIP-code URLs unsupported — Redfin does not expose a region ID for ZIP codes in the search URL; city/neighborhood/county URLs only.
• Feed depth — up to 350 listings per search URL; larger markets need multiple URLs.
• Redfin occasionally challenges search pages from datacenter IPs; the Actor retries and continues with the listings it can reach.