# Zillow Scraper — Listings, Prices, Agents (`yugenox/zillow-scraper`) Actor

Scrape Zillow for-sale / for-rent / sold listings by city: price, price history, Zestimate, beds/baths, sqft, address, coordinates, MLS id + broker, photos, and more.

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

## Pricing

from $0.80 / 1,000 results

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

## 🏡 Zillow Scraper — Listings, Prices, Zestimates & Agents

**Pull thousands of Zillow listings for a whole city in one run — with prices, Zestimates, beds/baths, addresses, coordinates, photos, brokers, and deep property details — no listing URLs required.**

Most Zillow tools make you feed in property URLs one by one (and run a *separate* search tool first just to collect them). This one is different: **give it a city and a listing type, and it finds and extracts every matching home for you** — for sale, for rent, or recently sold — and can enrich each one with full property detail. Discovery and detail, in a single actor.

***

### ⭐ Why this scraper

- 🔎 **Search by city, not URLs** — type `"Austin, TX"`, get every listing. No URL wrangling, no second tool.
- 💰 **Zestimate + Rent Zestimate on every home** — Zillow's own valuation, which most scrapers return empty.
- 📈 **Full‑market coverage** — it automatically sweeps a city in tiles to blow past Zillow's on‑screen result limit, so a single run returns **thousands of unique listings**, deduped.
- 🧾 **Rich fields out of the box** — price + price‑change, tax‑assessed value, beds/baths, sqft, lot, year built, exact coordinates, MLS id, broker, full photo galleries.
- 🔬 **Detailed mode** — flip one switch to add parking, heating/cooling, HOA, school districts, walk/bike scores, amenities, home‑insight highlights, and the full listing description per home.
- ⬇️ **Any format** — export to JSON, CSV, Excel, or XML, or pull straight from the API.

***

### 📦 What data you get

**Every listing (bulk):**

| Group | Fields |
|---|---|
| 💲 **Price & valuation** | `price`, `pricePerSqFt`, `priceChange` + `priceChangeDate`, **`zestimate`**, **`rentZestimate`**, `taxAssessedValue`, `taxAssessmentYear` |
| 🛏️ **Home facts** | `beds`, `baths` (`fullBaths`/`halfBaths`), `livingArea` (sqft), `lotSize`, `yearBuilt`, `homeType` |
| 📍 **Location** | `streetAddress`, `city`, `state`, `zipcode`, `country`, `latitude`, `longitude` |
| 🏷️ **Status & dates** | `listingStatus` (sale/rent/sold), `listingSubType` (FSBA/FSBO…), `listingDate`, `daysOnZillow`, `isZillowOwned` |
| 🧑‍💼 **Listing source** | `mlsId`, `mlsName`, `brokerName` |
| 🖼️ **Media** | `photoCount`, `coverPhoto`, `photos[]` (30+/home), `hasVideos`, `has3DTour` |
| 🔗 **Links** | `detailUrl`, `zpid` |

**🔬 With Detailed mode on, each home also gets:**

`description` · `parkingFeatures` + garage/covered capacity · `heating` · `cooling` · `hasPrivatePool` · `fireplaces` · `hoaFee` · **school districts** (elementary/middle/high) · **`walkScore` / `bikeScore` / `transitScore`** · `homeInsights` (highlight phrases) · `atAGlanceFacts` · `otherFacts` (water/sewer, security, community — when Zillow lists them) · `streetViewUrl` · high‑res photo keys · agent/broker attribution (when provided)

***

### 🔑 Getting a token

Zillow's mobile API is protected by PerimeterX, so the scraper needs a **token bundle** — the
request headers (including `x-px-authorization`) minted by a real Zillow app session. To capture one:

1. Run an HTTP proxy on your computer (mitmproxy, Charles, Proxyman) and point your phone's Wi‑Fi
   proxy at it, with the proxy's certificate trusted.
2. Open the Zillow app and run any search.
3. Find a request to `zm.zillow.com/api/public/v2/mobile-search/...` and copy its request headers
   as a JSON object.
4. Paste that JSON into the **tokenBundle** input field (stored encrypted).

Tokens expire after a while — if a run reports the token as expired/blocked, capture a fresh one
the same way. Without a token the run exits immediately with 0 listings and a pointer to this section.

***

### ⚙️ Input

| Field | Type | Default | Description |
|---|---|---|---|
| `locations` | array of strings | — (**required**) | Cities/areas to scrape, e.g. `["Austin, TX", "Phoenix, AZ"]`. Each is geolocated and swept for full coverage. |
| `tokenBundle` | string (secret) | — | Zillow token bundle as a JSON object of headers — see **Getting a token** above. |
| `status` | select | `forSale` | `forSale`, `forRent`, or `sold`. |
| `detailed` | boolean | `false` | Add the deep per‑home fields (parking, HVAC, schools, amenities, description…). Richer, but slower (one extra request per home). |
| `maxItems` | integer | *(all)* | Cap the total number of listings. |
| `proxyConfiguration` | proxy | Residential | Apify Proxy (residential recommended). |

**Example input:**

```json
{
  "locations": ["Austin, TX"],
  "status": "forSale",
  "detailed": true,
  "maxItems": 500
}
```

***

### 📤 Output

One row per listing. Here's a real for‑sale result (detailed mode on):

```json
{
  "zpid": 84380951,
  "price": 259900,
  "currency": "usd",
  "pricePerSqFt": 145,
  "zestimate": 253000,
  "rentZestimate": 1904,
  "taxAssessedValue": 252139,
  "taxAssessmentYear": 2025,
  "beds": 4,
  "baths": 3,
  "fullBaths": 2,
  "halfBaths": 1,
  "livingArea": 1794,
  "yearBuilt": 1992,
  "homeType": "singleFamily",
  "streetAddress": "112 Rock Point Dr",
  "city": "Del Valle",
  "state": "TX",
  "zipcode": "78617",
  "latitude": 30.133451,
  "longitude": -97.56978,
  "listingStatus": "forSale",
  "listingSubType": { "isFSBA": true },
  "listingDate": "2026-07-06",
  "daysOnZillow": 1,
  "brokerName": "Compass RE Texas, LLC",
  "photoCount": 15,
  "photos": ["https://photos.zillowstatic.com/fp/..."],
  "detailUrl": "https://www.zillow.com/homedetails/84380951_zpid/",
  "description": "Exceptional Investment Opportunity in the Heart of Del Valle!...",
  "parkingFeatures": ["Driveway", "Parking Lot"],
  "garageSpaces": 2,
  "heating": ["Electric", "Solar"],
  "cooling": ["Electric"],
  "fireplaces": 1,
  "hoaFee": null,
  "elementarySchoolDistrict": "Bastrop ISD",
  "highSchoolDistrict": "Bastrop ISD",
  "walkScore": 12,
  "bikeScore": 30,
  "homeInsights": ["Spacious lot", "Generously sized bedrooms", "Open-concept flow"],
  "atAGlanceFacts": { "Type": "Single Family Residence", "Parking": "2 Covered spaces", "Lot": "10,497 sqft", "Price/sqft": "$145" }
}
```

Export as **JSON, CSV, Excel, or XML** from the Storage tab, or via the Apify API.

***

### 🎯 Use cases

- **Lead generation** — build prospect lists of homes + brokers by city, filtered by price, beds, and days‑on‑market.
- **Market & pricing analysis** — track inventory, price cuts, days‑on‑market, and **Zestimate vs list price** across whole metros.
- **Investor sourcing** — surface `forSale` + `sold` comps with tax‑assessed value, lot size, and rent Zestimate for rental math.
- **Multi‑city research** — run the same query across many cities to compare markets and spot opportunities.
- **Feed your own app** — pipe fresh listing data into a CRM, dashboard, or ML pipeline via webhooks/integrations.

***

### ❓ FAQ

**Do I need to provide listing URLs?**
No — that's the whole point. Give it a **city**; it finds the listings. (Most Zillow tools require you to collect URLs with a separate search step first.)

**How many listings can I get per city?**
Thousands. It sweeps each city in tiles to get past the on‑screen result cap, and dedupes by property id. Use `maxItems` to cap.

**Does it include Zestimate?**
Yes — both `zestimate` and `rentZestimate` on every home.

**What's "Detailed mode"?**
An optional toggle that fetches each home's full detail page for the deep fields (parking, HVAC, HOA, school districts, walk/bike scores, amenities, description). It's richer but does one extra request per home, so it's slower — leave it off for fast bulk pulls, turn it on when you need depth.

**Can I scrape multiple cities and for‑sale/for‑rent/sold?**
Yes — pass several `locations`, and pick the `status`. Run per status if you want all three.

**What export formats and integrations are supported?**
JSON, CSV, Excel, XML — plus Make, Zapier, Google Sheets, Slack, webhooks, and the Apify API.

**Is it legal to scrape Zillow?**
This Actor only collects publicly available data: property listings that anyone can view on Zillow without an account. Collecting publicly available data is generally legal, but you're responsible for how you use it. Results can include listing brokers' names, and that counts as personal data. You must follow privacy laws such as GDPR, PIPEDA and CCPA, as well as Zillow's terms. If you're unsure, check with a lawyer. More on this: [Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/)

**Does it access any private data?**
No. Everything comes from pages Zillow shows to any visitor without logging in. It never uses a login, never touches private or restricted accounts, and never reaches password-protected areas.

# Actor input Schema

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

Cities / areas to scrape — e.g. \["Austin, TX", "Phoenix, AZ", "Miami, FL"]. Each is geolocated and swept (auto-tiled) for full coverage.

## `tokenBundle` (type: `string`):

A Zillow mobile token bundle as a JSON object of headers (must include x-px-authorization) — see README → "Getting a token". Without one the run exits immediately with 0 listings. Stored encrypted.

## `status` (type: `string`):

Which listings to pull.

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

Cap listings PER location (each location gets its own budget). E.g. 20 with 4 locations = up to 80 total. Leave empty for everything found in each.

## `detailed` (type: `boolean`):

Fetch full per-listing detail: parking, HVAC, amenities, school districts, HOA, description, walk/bike scores, agent/attribution, water/sewer & more. Much richer, but one extra request per listing (slower).

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

Apify Proxy (residential recommended).

## Actor input object example

```json
{
  "locations": [
    "Austin, TX"
  ],
  "status": "forSale",
  "detailed": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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("yugenox/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("yugenox/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 yugenox/zillow-scraper --silent --output-dataset

```

## MCP server setup

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