# Zillow Property Listings Scraper (`neuro-scraper/zillow-property-listings-scraper`) Actor

Zillow Scraper SD - Zillow Scraper is a real estate data tool that extracts public Zillow listings for sale, for rent or sold by location or search URL: price, address, beds, baths, area, Zestimate, photos, broker, plus optional details and price history.

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

## Pricing

from $2.49 / 1,000 results

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 Scraper - homes for sale, rentals and sold homes from Zillow

The Zillow Scraper extracts public Zillow listings by location or by any Zillow search URL: price, address,
beds, baths, living area, Zestimate, rent Zestimate, days on Zillow, broker, coordinates and photos. Turn on
details to add the description, facts, year built, MLS attribution, HOA fee and (where Zillow shows it) the
price history. No Zillow account or login is used.

#### Input

| Field | Type | Default | Meaning |
|---|---|---|---|
| `searchTerms` | list | `Austin, TX` (prefill) | Locations as you would type them on Zillow: city + state, ZIP code, county, neighborhood |
| `listingType` | select | `for_sale` | `for_sale`, `for_rent` or `sold` - applies to `searchTerms` |
| `startUrls` | list | empty | Zillow search URLs with your own filters, or listing (`/homedetails/..._zpid/`) URLs |
| `maxItems` | integer | `50` | Total listings to return |
| `includeDetails` | boolean | `false` | Open each listing page for details (one extra request per listing) |
| `proxyConfiguration` | proxy | Apify RESIDENTIAL | Proxy used for Zillow |

#### Output (one row per listing)

| Field | Meaning |
|---|---|
| `zpid`, `url` | Zillow property id and listing URL |
| `statusType`, `statusText`, `homeStatus`, `homeType` | For sale / for rent / sold, Zillow status, home type |
| `price`, `priceMax`, `priceText`, `currency` | Price (rent buildings: lowest and highest rent), as shown, USD |
| `address`, `street`, `city`, `state`, `zipcode`, `latitude`, `longitude` | Location |
| `beds`, `baths`, `livingArea`, `lotAreaValue`, `lotAreaUnit` | Size |
| `daysOnZillow`, `zestimate`, `rentZestimate`, `taxAssessedValue` | Zillow estimates and tax value |
| `brokerName`, `isBuilding`, `buildingName`, `units` | Broker; apartment-building rows with their unit prices |
| `imageUrl`, `photos`, `hasVideo`, `has3DModel`, `isFeaturedListing`, `openHouse`, `flexText` | Media and badges |
| details: `description`, `yearBuilt`, `facts`, `atAGlanceFacts`, `priceHistory`, `mlsId`, `mlsName`, `listingAgentPhone`, `brokerageName`, `monthlyHoaFee`, `propertyTaxRate`, `datePosted`, `dateSold`, `lastSoldPrice`, `pageViewCount`, `favoriteCount`, `detailPhotos` ... | Only with `includeDetails` or listing URLs |
| `searchTotal`, `page`, `source`, `scrapedAt` | Result count Zillow reported, page number, the input that produced the row, time |

#### Measured limits (2026-10-03, local runs)

- 41 listings per page; about 1,000 listings per search (Zillow stops serving pages after ~24). Split a big
  city into ZIP codes, neighborhoods or price ranges (filters in a copied search URL) for more.
- 50 listings in 3 s, 150 rentals in 5 s (4 pages); with details about 1.5 s per listing.
- Price history is in the page only for some listings (Showcase listings); for-sale and sold pages without it
  return `priceHistory: null`.
- Tested without proxy from one residential IP; Zillow's PerimeterX did not challenge. A challenge is never
  solved: the Actor retries on a new IP, then skips the target with an error in the log.

#### Example

```json
{"searchTerms": ["Miami, FL", "90210"], "listingType": "for_rent", "maxItems": 200, "includeDetails": false}
```

# Actor input Schema

## `searchTerms` (type: `array`):

One per line: a city and state (Austin, TX), a ZIP code (90210), a county or a neighborhood - anything you would type into Zillow's search box.

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

Which Zillow tab to search for the locations above. URLs below keep their own filters.

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

Search URLs copied from Zillow with your filters (e.g. https://www.zillow.com/austin-tx/rentals/) or listing URLs (https://www.zillow.com/homedetails/.../29510997_zpid/).

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

Stops after this many listings in total. Zillow serves 41 listings per page and about 1,000 per search; split a big city into ZIP codes or price ranges for more.

## `includeDetails` (type: `boolean`):

Opens every listing page for the description, facts, year built, price and tax history, MLS attribution and all photos. One extra request per listing.

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

Residential proxies (the default) are recommended for Zillow. The Actor switches to a new IP when a request is blocked.

## Actor input object example

```json
{
  "searchTerms": [
    "Austin, TX"
  ],
  "listingType": "for_sale",
  "startUrls": [],
  "maxItems": 50,
  "includeDetails": 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 = {
    "searchTerms": [
        "Austin, TX"
    ],
    "startUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/zillow-property-listings-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 = {
    "searchTerms": ["Austin, TX"],
    "startUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/zillow-property-listings-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/96iTKuR32hrpvAe1n/builds/ZHDDlh4mkPKHTPVBZ/openapi.json