# Zillow Scraper: Search & Details, Zestimate, Price History (`arcadium/zillow-properties`) Actor

Zillow search and property details for locations, ZIP codes or URLs, $2.10 per 1,000 ($3.20 with details). For sale, rent or sold by city, ZIP or URL; maxcopell Zillow input works. Zestimate, days on market, price and tax history, schools. Splits big areas past the 820-home cap; no agent data.

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

## Pricing

from $1.20 / 1,000 properties

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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: Search & Details, Zestimate, Price History

Give it a city, ZIP code, county, Zillow search URL, property URL or zpid and it returns Zillow homes for sale, for rent or recently sold, one JSON row per property: price, Zestimate, rent Zestimate, beds, baths, square feet, lot, home type, days on market, price cut, brokerage, photos and coordinates. With details: description, year built, facts, price history, tax history and schools. $2.10 per 1,000 properties, $3.20 per 1,000 with details; paid plans pay less. You pay only for rows you get.

**Use case:** pull every listing in a city or ZIP with price, Zestimate and history in one run, for investors, agents' market reports and rent research, with no agent personal data.

**Why this actor**

- **Drop-in input.** Input written for `maxcopell/zillow-scraper` (`searchUrls`, `resultsLimit`), `maxcopell/zillow-zip-search` (`zipCodes`, `priceMin`, `priceMax`, `daysOnZillow`, `forRent`, `sold`) or `maxcopell/zillow-detail-scraper` (`startUrls`, `propertyStatus`) works as it is.
- Whole areas, not just 820 homes: big searches are split into map sections and de-duplicated.
- Any input you have: free-text places, search URLs with your filters, property URLs or zpids.
- No personal data: agents' names, phones, emails and licence numbers are never returned; the brokerage name is kept.
- Inputs that cannot be read give a free error row with a `code`.

Built by Arcadium Data: public data, dated and agent-ready, never personal data.

### Use with AI agents

Returns Zillow homes for sale, for rent or recently sold (price, Zestimate, beds, baths, area, photos, brokerage; optionally facts, price history, tax history, schools) for cities, ZIP codes, search URLs or property URLs. Agents can call it through the Apify MCP server (`https://mcp.apify.com`, open source as `apify/actors-mcp-server`) as `arcadium/zillow-properties`: the input schema is read from the actor, the result is a dataset of JSON rows.

**Input example** (minimal):

```json
{ "locations": ["Austin, TX"], "listingType": "for_sale", "maxResultsPerSearch": 50 }
```

What comes back: one `property` row per home (charged) and a free `error` row for an input that could not be read. Filter on the `rowType` field. The error row carries `rowType: "error"`, a `code` (`invalid_input`, `not_found`, `blocked`, `unavailable`), a `message` and the `input`. Retry on `blocked` and `unavailable` later; do not retry the other codes with the same input.

Cost of the call above on the Free plan: 50 properties at $2.10 per 1,000 plus the $0.001 start fee is about $0.11.

### Input examples

Homes for sale in a city, cheapest first:

```json
{ "locations": ["Austin, TX"], "listingType": "for_sale", "sortBy": "price_low", "maxResultsPerSearch": 500 }
```

Rentals from 2,000 USD/month with 3+ bedrooms in two ZIP codes:

```json
{ "locations": ["78704", "78745"], "listingType": "for_rent", "minPrice": 2000, "minBeds": 3 }
```

Recently sold houses with full details (price history, taxes, schools):

```json
{ "locations": ["Travis County, TX"], "listingType": "sold", "homeTypes": ["house"], "includeDetails": true, "maxResultsPerSearch": 200 }
```

A search URL copied from zillow.com (its filters and map area are kept):

```json
{ "searchUrls": ["https://www.zillow.com/austin-tx/"] }
```

Specific properties:

```json
{ "propertyUrls": ["https://www.zillow.com/homedetails/3207-Wickham-Ln-Austin-TX-78725/70345655_zpid/", "29478743"] }
```

These input field names are also accepted: `startUrls` (request-list objects), `zpids`, `zipCodes`, `searchUrls`, `propertyStatus` (`FOR_SALE`, `FOR_RENT`, `RECENTLY_SOLD`) and `maxItems`.

| Field | What it does |
|---|---|
| `locations` | Places as typed on Zillow: city + state, ZIP, county, neighborhood, state. |
| `searchUrls` | Zillow search URLs; the URL's filters are kept and the filters below are applied on top. |
| `propertyUrls` | Property URLs or zpids; one detail row each. |
| `listingType` | `for_sale` (default on Zillow), `for_rent`, `sold`. |
| `sortBy` | `relevance`, `newest`, `price_low`, `price_high`, `beds`, `baths`, `size`, `lot_size`. |
| `minPrice` / `maxPrice` | USD; monthly rent for rentals. |
| `minBeds` / `minBaths` | Minimum bedrooms / bathrooms. |
| `homeTypes` | Any of `house`, `townhouse`, `condo`, `apartment`, `multi_family`, `manufactured`, `lot_land`. |
| `daysOnZillow` | Only homes listed within `1`, `7`, `14`, `30`, `90` days or `6m`, `12m`, `24m`, `36m` (for sold: since the sale). |
| `maxResultsPerSearch` | Properties per location or search URL (default 200, up to 100,000). |
| `includeDetails` | Read each result's detail page too (charged as `property-details`). |
| `maxItems` | Cap on charged rows for the whole run. |

### Output

**Output example** (search row, abridged):

```json
{
  "rowType": "property",
  "platform": "zillow",
  "propertyId": "70345655",
  "url": "https://www.zillow.com/homedetails/3207-Wickham-Ln-Austin-TX-78725/70345655_zpid/",
  "status": "FOR_SALE",
  "price": 324900,
  "currency": "USD",
  "address": "3207 Wickham Ln, Austin, TX 78725",
  "city": "Austin", "state": "TX", "zipcode": "78725",
  "latitude": 30.232096, "longitude": -97.5937,
  "beds": 4, "baths": 3, "livingArea": 2575,
  "lotArea": 4800.312, "lotAreaUnit": "sqft",
  "homeType": "SINGLE_FAMILY",
  "daysOnMarket": 140,
  "zestimate": null, "rentZestimate": null,
  "taxAssessedValue": 365588,
  "priceChange": -15000, "priceChangeDate": "2026-10-14",
  "brokerName": "T J Lewis Real Estate",
  "photos": ["https://photos.zillowstatic.com/fp/...-p_e.jpg"],
  "detailed": false,
  "searchInput": "Austin, TX",
  "searchRank": 1,
  "scrapedAt": "2026-10-22T10:00:00.000Z"
}
```

Detail rows (`detailed: true`) add `yearBuilt`, `description`, `lastSoldPrice`, `monthlyHoaFee`, `propertyTaxRate`, `mlsId`, `listingDataSource`, `county`, `parcelId`, `facts` (object), `priceHistory` (`date`, `event`, `price`, `pricePerSquareFoot`, `priceChangeRate`, `source`), `taxHistory` (`date`, `taxPaid`, `value`), `schools` (`name`, `rating`, `distance`, `grades`), `pageViewCount`, `favoriteCount`.

Error row:

```json
{ "rowType": "error", "platform": "zillow", "input": "Nowhere", "code": "not_found", "message": "Zillow knows no place by this name; try \"City, ST\" or a ZIP code", "scrapedAt": "..." }
```

Error codes: `invalid_input` (not a Zillow URL or zpid), `not_found` (unknown place or removed property), `blocked` / `unavailable` (temporary; run again).

Dataset views: **overview** (address, price, Zestimate, beds, baths, size, brokerage), **details** (year built, lot, HOA, taxes, sale, history, schools), **errors**. The `STATS` record in the key-value store has requests, data volume, retries and cost per result.

### Pricing

Pay per result, with lower prices on higher Apify plans:

| Plan | `property` (search row) per 1,000 | `property-details` per 1,000 |
|---|---|---|
| Free | $2.10 | $3.20 |
| Bronze | $1.80 | $2.70 |
| Silver | $1.50 | $2.20 |
| Gold | $1.20 | $1.50 |
| Platinum | $1.20 | $1.50 |
| Diamond | $1.20 | $1.50 |

Plus $0.001 per run start. A detail row is charged instead of the search row, never both. A home found by two searches in one run is charged once. Error rows are free.

### Tips for AI agents and integrations

- Filter on `rowType` first; `propertyId` (zpid) is the stable key across runs.
- For price-drop monitoring, run the same `locations` daily with `sortBy: "newest"` and compare `price` / `priceChange` per `propertyId`.
- For a whole metro, set `maxResultsPerSearch` high (e.g. 20000); the map is split automatically. Per-ZIP `locations` give the same coverage with clearer `searchInput` labels.
- Sold prices: search rows of sold homes have `price: null` on many listings; use `includeDetails: true` and read `lastSoldPrice` and `priceHistory`.

### Limitations

- Zillow lists at most 820 homes per query; larger areas are split into map sections automatically.
- Sold homes often have `price: null` in search rows; use `includeDetails` for `lastSoldPrice`.

Public data only, read without login. Zillow blocks datacenter IPs, so the actor uses US residential proxies; this is included in the price.

# Actor input Schema

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

Places to search, as you would type them on Zillow: for example a city ("Austin, TX"), ZIP code ("78704"), county ("Travis County, TX"), neighborhood or state. Each location is searched on its own with the filters below; every row keeps the location and its position in the results. Also accepted as `zipCodes`, `search`, `searchTerms`, `queries` or `addresses` (maxcopell actors).

## `searchUrls` (type: `array`):

Search result URLs copied from zillow.com, e.g. https://www.zillow.com/austin-tx/ or a URL with your own filters and map area (searchQueryState). The URL's filters are kept; filters set below are applied on top.

## `propertyUrls` (type: `array`):

Property pages (https://www.zillow.com/homedetails/.../70345655_zpid/) or bare Zillow property ids (zpid, e.g. 70345655). Each gives one row with full details (facts, price and tax history, schools).

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

Which homes to search: for_sale (Zillow's default), for_rent or sold (recently sold). Empty keeps the type of a search URL. Also accepted as `status`, `propertyStatus` (RECENTLY_SOLD...) or maxcopell's `forRent` / `sold` switches.

## `sortBy` (type: `string`):

Order of the results. Empty keeps Zillow's default (relevance) or the sort of a search URL.

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

Lowest price in USD, e.g. 300000. For rentals this is the monthly rent, e.g. 2000.

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

Highest price in USD, e.g. 900000. For rentals this is the monthly rent.

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

Only homes with at least this many bedrooms, e.g. 3.

## `minBaths` (type: `integer`):

Only homes with at least this many bathrooms, e.g. 2.

## `homeTypes` (type: `array`):

Only these home types. Empty means all. Values: house, townhouse, condo, apartment, multi_family, manufactured, lot_land.

## `daysOnZillow` (type: `string`):

Only homes listed on Zillow within this period, e.g. 7 for new listings this week. For sold searches it is the time since the sale. Empty means any. maxcopell/zillow-zip-search's `daysOnZillow` uses the same values.

## `maxResultsPerSearch` (type: `integer`):

Properties per location or search URL, e.g. 200 (the default). Zillow lists at most 820 homes per query; larger areas are split into map sections automatically, so whole metros can be read. Also accepted as `resultsLimit` or `maxResults`.

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

Also read each search result's detail page: description, year built, facts (heating, cooling, parking, appliances, HOA...), price history, tax history, schools. Detail rows are charged as 'property-details' instead of 'property'. Off by default.

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

Optional cap on charged rows for the whole run, e.g. 1000. Empty means no cap beyond the per-search limit.

## `includeErrorRows` (type: `boolean`):

Add a free row with rowType 'error', a code (invalid_input, not_found, blocked, unavailable) and a message for every input that could not be read.

## `maxRetries` (type: `integer`):

Retries per request after a temporary error, each on a new IP (default 4).

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

Leave empty: the actor uses US residential proxies, which Zillow needs. Set your own proxies only if you know they pass Zillow's bot check.

## Actor input object example

```json
{
  "locations": [
    "Austin, TX"
  ],
  "maxResultsPerSearch": 50,
  "includeErrorRows": true,
  "maxRetries": 4
}
```

# Actor output Schema

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

All rows of this run in the default dataset.

## `view_overview` (type: `string`):

No description

## `view_details` (type: `string`):

No description

## `view_errors` (type: `string`):

No description

## `record_stats` (type: `string`):

Requests, data volume, retries and cost per result for this run.

# 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"
    ],
    "maxResultsPerSearch": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("arcadium/zillow-properties").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"],
    "maxResultsPerSearch": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("arcadium/zillow-properties").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"
  ],
  "maxResultsPerSearch": 50
}' |
apify call arcadium/zillow-properties --silent --output-dataset

```

## MCP server setup

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

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/P53VTMKzCzhlSnw4S/builds/hGumpglbc1DlBwjG1/openapi.json