# Zillow Search Scraper — Listings and Details (`crawloop/zillow-search-scraper`) Actor

Zillow scraper for US homes for sale, for rent, and sold. Search results plus listing details: price, beds, baths, sqft, Zestimate, price history, and brokerage.

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

## Pricing

from $1.70 / 1,000 listings

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Search Scraper — Listings and Details

> **Disclaimer:** Unofficial tool — not affiliated with, sponsored by, or endorsed by Zillow, Inc. or its affiliates. Data is read from publicly accessible search results and listing pages only. No login. You are responsible for complying with applicable law (including GDPR where personal data appears) and the site’s terms. No warranty on accuracy or availability. Provided for informational and research use.

**Zillow scraper** for US homes **for sale**, **for rent**, and **sold**. Each row is one listing: price, beds, baths, sqft, days on market, and brokerage from the search card, plus description, year built, Zestimate, price history, and the public listing contact from the listing page. Use it as a **Zillow API alternative** from **Python**, **Node.js**, **cURL**, or **Apify MCP**.

**Best for:** city or ZIP pulls, CMA worksheets, and a scheduled monitor that emits only new zpids.

| Actor | Role |
| :--- | :--- |
| Zillow Search Scraper ◄── you are here | US for-sale, rent, and sold search plus listing details |
| [Realtor.com Scraper](https://apify.com/crawloop/realtor-com-scraper) | US sold comps, ZIP, and monitor on Realtor.com |
| [LoopNet Scraper](https://apify.com/crawloop/loopnet-scraper) | US commercial sale and lease |
| [Furnished Finder Scraper](https://apify.com/crawloop/furnished-finder-scraper) | US mid-term rentals |

### When to use this Actor

- **City or ZIP search** — `Austin, TX` or `78717`, for sale, for rent, or sold.
- **A saved search URL** — Paste a results URL. Page numbers are applied on top of that path.
- **One listing** — Paste a listing URL (`/homedetails/`) to fetch that property.
- **Scheduled monitoring** — Re-run the same search and save only zpids that were not stored last time.
- **Comps with history** — Keep **Fetch listing details** on to add Zestimate, year built, and price history on the same row.

### When not to use this Actor

- **Agent directories or skip tracing** — This Actor reads the public listing page. It does not open agent profiles or enrich emails.
- **Commercial listings** — Use LoopNet for sale and lease inventory.
- **A second US portal** — For sold comps on Realtor.com, run that Actor next.

### Key features

- **HTTP pages** — Search cards and listing details come from the public HTML. No browser. Default memory is 256 MB.
- **Search plus details** — One dataset row per home. Price history stays on that row.
- **For sale, rent, and sold** — Set the status, or paste a results URL that already has filters.
- **Monitor mode** — A named key-value store remembers zpids per search. A quiet tick writes zero rows.
- **Residential US proxy** — Datacenter IPs are denied. The default proxy is Apify residential in the US. No extra homepage request.

### Input

| Field | What it does |
| :--- | :--- |
| **Location** | City and state, or a ZIP. Ignored when Start URLs is set. |
| **Listing status** | `for_sale` (default), `for_rent`, or `sold`. |
| **Start URLs** | Search results or one listing URL. |
| **Fetch listing details** | On by default. Adds description, Zestimate, price history, year built, and the public listing phone when the page shows one. |
| **Max listings** | Cap across all searches. One results page is about 41 cards. |
| **Monitor mode** | Save only new zpids for this search. |
| **Proxy** | Apify residential in the US. Required on the platform. |

```json
{
  "location": "78717",
  "listingStatus": "for_sale",
  "fetchDetails": true,
  "maxItems": 25,
  "monitorMode": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}
```

### Output

One dataset row per listing.

| Field | Meaning |
| :--- | :--- |
| `zpid` / `url` | Property id and public listing URL |
| `address`, `city`, `state`, `zip` | Address from the search card |
| `price` / `status` | List price or rent, and `FOR_SALE`, `FOR_RENT`, or `SOLD` |
| `beds`, `baths`, `sqft` | Size |
| `daysOnZillow` | Days on market from the search card |
| `zestimate`, `rentZestimate` | Estimates when the listing page includes them |
| `yearBuilt`, `description`, `priceHistory` | Listing-page fields |
| `brokerName`, `listingPhone`, `mlsId` | Brokerage, public listing phone, and MLS id when shown |
| `latitude`, `longitude`, `image` | Map point and primary photo |
| `scrapedAt` | UTC timestamp |

```json
{
  "zpid": "52830624",
  "url": "https://www.zillow.com/homedetails/15120-Thatcher-Dr-Austin-TX-78717/52830624_zpid/",
  "address": "15120 Thatcher Dr, Austin, TX",
  "city": "Austin",
  "state": "TX",
  "zip": "78717",
  "price": 565000,
  "status": "FOR_SALE",
  "beds": 3,
  "baths": 2,
  "sqft": 2537,
  "yearBuilt": 2000,
  "zestimate": 570000,
  "brokerName": "LPT Realty, LLC",
  "daysOnZillow": 5
}
```

### Use cases

- Pull for-sale homes in a ZIP and compare price, sqft, and days on market.
- Schedule a morning monitor and export only new zpids.
- Attach price history and year built for a CMA worksheet.
- For the same ZIP on another US portal, continue with [Realtor.com Scraper](https://apify.com/crawloop/realtor-com-scraper).

### Integration examples

Replace `APIFY_TOKEN`. The slug below is the Store name.

#### Node.js

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("crawloop/zillow-search-scraper").call({
  location: "78717",
  listingStatus: "for_sale",
  fetchDetails: true,
  maxItems: 25,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("crawloop/zillow-search-scraper").call(run_input={
    "location": "Austin, TX",
    "listingStatus": "sold",
    "fetchDetails": True,
    "maxItems": 25,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(len(items))
```

#### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/crawloop~zillow-search-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"location":"78717","listingStatus":"for_sale","fetchDetails":true,"maxItems":10}'
```

### MCP and AI assistants

Use this Actor from AI tools via [Apify MCP](https://docs.apify.com/platform/integrations/mcp).
Connect your Apify account, then call this Actor by its Store name `crawloop/zillow-search-scraper`.

Example prompts:

- "Run Zillow Search Scraper for ZIP 78717 for-sale listings and return the top 20 rows as JSON"
- "Scrape Zillow sold listings in Austin, TX and summarize price, sqft, and days on market"
- "Run Zillow Search Scraper for 78717, then run Realtor.com Scraper for sold comps in the same ZIP"

### Suite next step

This Actor covers Zillow search and listing details. For sold comps on the other national portal, run [Realtor.com Scraper](https://apify.com/crawloop/realtor-com-scraper). For commercial sale and lease, run [LoopNet Scraper](https://apify.com/crawloop/loopnet-scraper).

### FAQ

**Does each row include the listing page?**
Yes, when **Fetch listing details** is on (the default). Description, year built, Zestimate, and price history are added to the same row. Turn it off to keep search cards only.

**Is a proxy required?**
Yes on Apify. Datacenter IPs are denied. The default is residential in the US. The Actor does not open an extra homepage request.

**What does monitor mode skip?**
Zpids already stored for that same search. A different city, status, or URL is a new cursor. A run with no new ids writes zero rows.

**Which locations work?**
A city and state such as `Austin, TX`, or a ZIP such as `78717`. A pasted results URL keeps the filters already in that address.

# Actor input Schema

## `location` (type: `string`):

US city and state or ZIP, for example Austin, TX or 78717. Ignored when Start URLs is set.

## `listingStatus` (type: `string`):

Search type used with Location. Ignored when Start URLs is set.

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

Zillow search URLs or a single listing URL. When this list is set, Location and Listing status are ignored.

## `fetchDetails` (type: `boolean`):

Open each listing page and add description, Zestimate, price history, year built, and the public listing contact.

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

Maximum listing rows across all searches. One search page is about 41 cards.

## `monitorMode` (type: `boolean`):

Save only listing ids that were not saved for this search on a previous run. A quiet tick writes zero rows.

## `monitorStateStore` (type: `string`):

Named key-value store for listing ids already seen. Used only when monitor mode is on.

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

Apify residential proxy in the United States. Datacenter IPs are denied before the page loads.

## Actor input object example

```json
{
  "location": "Austin, TX",
  "listingStatus": "for_sale",
  "fetchDetails": true,
  "maxItems": 25,
  "monitorMode": false,
  "monitorStateStore": "zillow-search-monitor",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

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

Default dataset items — one listing per row.

# 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 = {
    "location": "Austin, TX",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "US"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawloop/zillow-search-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 = {
    "location": "Austin, TX",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "US",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("crawloop/zillow-search-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 '{
  "location": "Austin, TX",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}' |
apify call crawloop/zillow-search-scraper --silent --output-dataset

```

## MCP server setup

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