# Redfin Properties Scraper — Homes for Sale (`darknezz/redfin-properties-scraper`) Actor

Scrape Redfin homes for sale from any city, neighborhood or county search URL: prices, beds, baths, sqft, year built, days on market, remarks and location as clean JSON. No API key, login or proxy required.

- **URL**: https://apify.com/darknezz/redfin-properties-scraper.md
- **Developed by:** [Oaida Adrian](https://apify.com/darknezz) (community)
- **Categories:** Real estate, Lead generation
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 property scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{
  "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)

```json
{
  "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

```bash
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:**

```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 **$0.005 per property listing scraped** (primary charge event `property-scraped`), plus Apify's standard compute costs and a one-time **$0.01 actor-start fee**. A 100-listing comparable search costs about $0.50 in event fees. No subscription required — you pay only for what you pull.

### 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.

# Actor input Schema

## `startUrls` (type: `array`):

Redfin city, neighborhood or county search URLs, e.g. https://www.redfin.com/city/30818/TX/Austin. Copy them from your browser's address bar after searching on redfin.com (zipcode URLs are not supported - use the city URL instead).

## `maxListingsPerUrl` (type: `integer`):

Maximum number of listings to scrape per search URL (up to 350).

## Actor input object example

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

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://www.redfin.com/city/30818/TX/Austin"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("darknezz/redfin-properties-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": ["https://www.redfin.com/city/30818/TX/Austin"] }

# Run the Actor and wait for it to finish
run = client.actor("darknezz/redfin-properties-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://www.redfin.com/city/30818/TX/Austin"
  ]
}' |
apify call darknezz/redfin-properties-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,darknezz/redfin-properties-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/F1trZyPRsB98LSkIQ/builds/hQ0mDWhqUymjqKBgW/openapi.json