# Zillow Real Estate Scraper (`muhammad4hmed/zillow-scraper`) Actor

Scrape Zillow for-sale, for-rent and recently-sold listings: prices, beds, baths, square footage, home type, days on market, Zestimates and GPS coordinates for any US city or ZIP code.

- **URL**: https://apify.com/muhammad4hmed/zillow-scraper.md
- **Developed by:** [Muhammad Ahmed](https://apify.com/muhammad4hmed) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Zillow Real Estate Scraper

Pull Zillow listings into a clean dataset. Give it a city or ZIP code and get every matching property with price, beds, baths, square footage, home type, days on market, GPS coordinates and the Zestimate — for **homes for sale, rentals, and recently sold properties**.

No browser, no rendering, no waiting: it reads Zillow's own structured search data directly, which is why a 240-listing run finishes in about 25 seconds.

### What you get

Every property becomes one row:

| Field | Description |
|---|---|
| `zpid` | Zillow's property ID — a stable key for joins and de-duplication |
| `url` | Link to the Zillow listing |
| `address` | Full address, plus `street`, `city`, `state`, `zipcode` separately |
| `price` | Numeric price (monthly rent for rentals), with `priceText` and `currency` |
| `beds`, `baths` | Bedroom and bathroom counts |
| `livingArea` | Interior square footage |
| `lotArea`, `lotAreaUnit` | Lot size and its unit |
| `homeType` | `SINGLE_FAMILY`, `CONDO`, `TOWNHOUSE`, `APARTMENT`, `LOT`, … |
| `homeStatus` | `FOR_SALE`, `FOR_RENT`, `RECENTLY_SOLD`, … |
| `statusText` | Zillow's own label, e.g. "Active", "Coming soon" |
| `daysOnZillow` | How long the listing has been up |
| `latitude`, `longitude` | GPS coordinates |
| `zestimate`, `rentZestimate` | Zillow's estimated value and rent, when published |
| `taxAssessedValue` | Assessed value for tax purposes |
| `priceChange`, `datePriceChanged` | Size and date of the most recent price change |
| `brokerName` | Listing broker |
| `imageUrl` | Main listing photo |
| `listingType`, `searchLocation`, `page`, `scrapedAt` | What produced the row, and when |

### Example

```json
{
  "zpid": "29329029",
  "url": "https://www.zillow.com/homedetails/1406-W-13th-St-Austin-TX-78703/29329029_zpid/",
  "address": "1406 W 13th St, Austin, TX 78703",
  "city": "Austin",
  "state": "TX",
  "zipcode": "78703",
  "price": 1299000,
  "beds": 3,
  "baths": 2,
  "livingArea": 1578,
  "homeType": "SINGLE_FAMILY",
  "homeStatus": "FOR_SALE",
  "daysOnZillow": 3,
  "latitude": 30.280336,
  "longitude": -97.75638
}
```

### Input

| Option | Description |
|---|---|
| **Locations** | US cities, neighborhoods or ZIP codes: `Austin, TX`, `Brooklyn, NY`, `90210`. Required. |
| **Listing type** | For sale, for rent, or recently sold. |
| **Max results per location** | Up to 820 per location (see the limit note below). |
| **Minimum / maximum price** | Filter by price, or by monthly rent for rentals. |
| **Minimum bedrooms** | Skip anything smaller. |
| **Max items** | Hard cap across the whole run. |
| **Proxy configuration** | Residential proxy, required and on by default. |

### Use it for

- **Market analysis** — median price per ZIP, price-per-square-foot trends, inventory counts
- **Investment screening** — filter by price, beds and `rentZestimate` to find rental yield
- **Comparable sales** — pull recently sold properties near a target address
- **Rental pricing** — see what comparable units actually ask in a neighborhood
- **Lead generation** — listings with a long `daysOnZillow` and a recent `priceChange`

### Honest notes

- **Zillow caps every search at 20 pages — 820 listings** — no matter how many results it reports. A city with 5,000 listings will only ever return the first 820 for a single search. To get full coverage, search by ZIP code instead of by city; the Actor reports Zillow's total count in the log so you can see what you're missing.
- **Zestimates aren't published for every property.** Roughly a quarter of for-sale listings carry one; `zestimate` is `null` for the rest. That's Zillow's data, not a scraping gap.
- **Residential proxy is required.** Zillow blocks datacenter IPs outright and rate-limits hard by address. The Actor gives each request a fresh proxy session and retries refusals automatically, but changing the proxy setting away from residential will cause runs to fail.
- **Price filters are applied to what Zillow returns**, so a filtered run reads the same number of pages as an unfiltered one. Narrow filters mean fewer results, not a cheaper run — the log shows how many were filtered out.

### Pricing

Pay per listing actually extracted. Blocked or failed pages cost you nothing, and there is no charge per page or per hour — a run that returns 500 listings costs the same whether Zillow served them in one page or twenty.

# Actor input Schema

## `locations` (type: `array`):

US cities, neighborhoods or ZIP codes to search, e.g. "Austin, TX", "Brooklyn, NY" or "90210".

## `listingType` (type: `string`):

Which Zillow search to scrape: homes for sale, rentals, or recently sold properties.

## `maxResultsPerLocation` (type: `integer`):

How many listings to collect per location. Zillow returns 41 per page and caps every search at 20 pages (820 listings), so split large cities by ZIP code to go deeper.

## `minPrice` (type: `integer`):

Skip listings below this price. For rentals this is monthly rent. 0 means no minimum.

## `maxPrice` (type: `integer`):

Skip listings above this price. For rentals this is monthly rent. 0 means no maximum.

## `minBeds` (type: `integer`):

Skip listings with fewer bedrooms than this. 0 means no minimum.

## `maxItems` (type: `integer`):

Hard cap on total listings across all locations. 0 means no cap.

## `proxyConfiguration` (type: `object`):

Zillow blocks datacenter IPs and rate-limits hard by address, so residential proxy is required. Leave this as it is unless you know what you are changing.

## Actor input object example

```json
{
  "locations": [
    "Austin, TX",
    "90210"
  ],
  "listingType": "for_sale",
  "maxResultsPerLocation": 200,
  "minPrice": 0,
  "maxPrice": 0,
  "minBeds": 0,
  "maxItems": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `listings` (type: `string`):

Every property scraped from the Zillow search results, one row each.

## `csv` (type: `string`):

The same listings as a spreadsheet-ready CSV file.

# 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 = {
    "locations": [
        "Austin, TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammad4hmed/zillow-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 = { "locations": ["Austin, TX"] }

# Run the Actor and wait for it to finish
run = client.actor("muhammad4hmed/zillow-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 '{
  "locations": [
    "Austin, TX"
  ]
}' |
apify call muhammad4hmed/zillow-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muhammad4hmed/zillow-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/a9e3fagmWk5Sb3PLH/builds/m4IdwEBj9Xofn3E96/openapi.json