# Zillow Property Detail Scraper (`usestring/zillow-detail`) Actor

Collect full Zillow property detail by URL or ZPID - facts, status, coordinates.

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

## Pricing

from $1.25 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Property Scraper — full detail by ZPID or URL

This Actor scrapes Zillow property detail pages. Give it a ZPID or a Zillow `/homedetails/` URL and
it returns that home's own record: **numeric** price, beds, baths, living area, lot size in square
feet, year built, home type, listing status, exact coordinates and the full listing description.

No Zillow account, login or cookies are used — this reads what a logged-out visitor sees. One Zillow
request per property, up to **200 properties per run**.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `zpid` | string | Zillow's own property ID — stable across runs, use it to de-duplicate |
| `address` | string | One line: street, city, state and ZIP |
| `city`, `state`, `zipcode` | string | Split out as well |
| `price` | number | `675000`, not `"$675,000"` |
| `beds`, `baths` | number | |
| `areaSqft` | number | Living area |
| `lotSizeSqft` | number | Always square feet — an acre-quoted lot is converted |
| `yearBuilt` | number | |
| `homeType` | string | e.g. `SINGLE_FAMILY`, `CONDO`, `TOWNHOUSE` |
| `homeStatus` | string | e.g. `FOR_SALE`, `FOR_RENT`, `SOLD`, `PENDING` |
| `latitude`, `longitude` | number | Exact coordinates, ready to map |
| `description` | string | The listing's own description text |
| `sourceUrl`, `collectedAt` | string | Provenance for every row |

### Input

```json
{
  "properties": ["29502073", "https://www.zillow.com/homedetails/6310-Needham-Ln-Austin-TX-78739/29502073_zpid/"],
  "concurrency": 5
}
```

| Field | Description |
| --- | --- |
| `properties` | Bare ZPIDs or Zillow `/homedetails/` URLs. Required, 1–200. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Properties fetched in parallel. Default 5, maximum 10. |

A ZPID and the full detail URL for the same home resolve to one Zillow request, so a mixed list is
never billed twice.

### Use cases

- Comparable-sales and valuation work that needs lot size, year built and living area together
- Enriching a portfolio or CRM of addresses with current price, status and property facts
- Training and back-testing an automated valuation model on real property records
- Following the listings a search Actor found, to get facts the search page does not carry
- Watching status changes — `FOR_SALE` to `PENDING` to `SOLD` — by re-running on a schedule

### Reliability

The Zillow Property Scraper reads each property from Zillow's own page data rather than from
rendered text, so a value is either present and exact or `null` — prices and areas never arrive as
display strings to clean up.

A detail page that loads but carries no property facts — a building shell, or an interstitial served
under the detail route — is recorded as a failed target rather than emitted as an all-`null` row.
Failures are listed in the run's `SUMMARY` under `failures`, and a run where every property failed
exits with an error.

There are no retries by design: the String Unblocker owns proxy rotation and anti-bot solver
selection, so a retry loop here would only re-roll the same block.

### Frequently asked questions

**Do I need a Zillow account, API key or cookies?** No. The Zillow Property Scraper reads the public
detail page a logged-out visitor sees, and never signs in.

**What input does the Zillow Property Scraper accept?** A bare ZPID such as `29502073`, or a Zillow
`/homedetails/` URL whose final segment is the `_zpid` part. URLs that address something other than a
property record — a building page under `/apartments/` — are reported under `failures`.

**Does it return the listing description?** Yes. The `description` field carries the listing's own
description text, with HTML entities decoded.

**Is lot size in acres or square feet?** Always square feet, in `lotSizeSqft`. A listing quoted in
acres is converted, so a rural and a suburban lot compare directly.

**How many properties can one run collect?** Up to 200, the maximum length of the `properties` input.
Each property costs one Zillow request.

**Does it include photos, price history, tax history or the Zestimate?** No. Those are out of scope;
this Actor returns the property fact set listed in the table above.

### Limitations

One detail page per property, and only `zillow.com` — US properties only. Photos, price and tax
history, Zestimate detail, schools, and agent or broker contact details are not collected. Search and
discovery are out of scope: you supply the ZPIDs, and the Zillow Property Listings Scraper is the
Actor that finds them by city.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

## `properties` (type: `array`):

Zillow detail URLs or bare ZPIDs.

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

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

## `concurrency` (type: `integer`):

Targets fetched in parallel.

## Actor input object example

```json
{
  "properties": [
    "https://www.zillow.com/homedetails/12345678_zpid/"
  ],
  "maxItems": 1000,
  "concurrency": 5
}
```

# Actor output Schema

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

Collect full Zillow property detail by URL or ZPID - facts, status, coordinates.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

# 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 = {
    "properties": [
        "https://www.zillow.com/homedetails/12345678_zpid/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usestring/zillow-detail").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 = { "properties": ["https://www.zillow.com/homedetails/12345678_zpid/"] }

# Run the Actor and wait for it to finish
run = client.actor("usestring/zillow-detail").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 '{
  "properties": [
    "https://www.zillow.com/homedetails/12345678_zpid/"
  ]
}' |
apify call usestring/zillow-detail --silent --output-dataset

```

## MCP server setup

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

```

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/fbjFgxk13RtewmRtE/builds/EYblgxL1rai7xjSmJ/openapi.json