# Zillow Property Details Scraper: Zestimate, History & Records (`scrapebench/zillow-property-details-scraper`) Actor

Zillow property details by address, Zillow URL, zpid or search URL: Zestimate, rent Zestimate, photos, price and tax history, schools, listing agent, plus APN, county FIPS, tax assessment and FEMA flood zone. No browser, pay per home found.

- **URL**: https://apify.com/scrapebench/zillow-property-details-scraper.md
- **Developed by:** [ScrapeBench](https://apify.com/scrapebench) (community)
- **Categories:** Real estate
- **Features:** Limited permissions
- **Stats:** 6 total users, 6 monthly users, 75.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.0028 / home found

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 Property Details Scraper: Zestimate, History & Records

### Pain points

- A Zillow home page shows the Zestimate, price history, tax history, schools and agent, but only to a person reading it; you need those facts as rows for a list of homes.
- Zillow's pages sit behind PerimeterX's "Press & Hold" wall, which refuses headless browsers and most plain clients.
- Zillow's record stops at the listing: the county parcel number and county FIPS are buried in it, and the FEMA flood zone is not on the page at all.

### What we solve

- Give it street addresses, Zillow home URLs or zpids, or a Zillow search URL; each home comes back as one flat row with about 50 fields.
- Reads Zillow's own structured data (the same data its pages load) with a Chrome-fingerprinted client over residential IPs, so no browser runs and a batch is fast.
- Adds public-record fields: the assessor's parcel number (APN), county FIPS, the latest county assessed value with its year, and the FEMA flood zone at the home's own point from FEMA's National Flood Hazard Layer.
- Charges only for homes it delivers; an address Zillow has no home for, or a lookup Zillow refused, is a free row that says which.

### Summary

Turn addresses, Zillow links or a Zillow search into full property records. For every home the actor returns Zillow's Zestimate and its range, the rent Zestimate, asking or last sale price and sale date, beds, baths, living area, lot size, year built, home type and status, days on Zillow, property tax rate and HOA fee, the listing description, the listing agent with phone, email and licence number, the brokerage, the buyer's agent and brokerage on a sale, the MLS number, the full photo gallery at the largest size, the price history (every listing, price change and sale with price per square foot and source), the tax history (tax paid and assessed value per year), assigned schools with GreatSchools ratings and sub-ratings, nearby homes, and Zillow's facts and features. On top it adds the public-record join keys and risk: the county assessor's parcel number (APN), county FIPS, latitude and longitude, the latest county assessed value with its year, and the FEMA flood zone at the home's point (zone, subtype, Special Flood Hazard Area flag, base flood elevation). It runs without a browser: Zillow's own data endpoints, read with a Chrome-fingerprinted client over residential IPs, five homes at a time. Built for investors, agents, lenders, insurers and proptech apps that need a Zillow record per address in bulk.

### Who it's for

- Real-estate investors and wholesalers pricing a list of addresses
- Agents and brokerages enriching a CRM with Zestimates, history and agent data
- Lenders, insurers and proptech apps that need a Zillow record plus APN and flood zone per address
- Analysts building comp and market datasets from Zillow searches

### How to use

Set the input, run the actor, and collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API). Example input:

```json
{
  "addresses": [
    "745 Garland Dr, Palo Alto, CA 94303",
    "827 Krenson Woods Ln, Lakeland, FL 33813"
  ]
}
```

See **Inputs** below for every available field.

### What you get

One row per record:

| Field | Description |
|---|---|
| `query` | The address, URL or zpid you gave, so a batch can be matched back |
| `found` | true when Zillow has the home; false rows are free and carry 'error' |
| `zpid / url` | Zillow's property id and the home's Zillow page |
| `address, city, state, zip, county` | The home's address as Zillow has it |
| `apn` | Assessor's parcel number: the join key for county assessor records |
| `fips` | 5-digit county FIPS code: the join key for census and county data |
| `latitude / longitude` | The home's own point |
| `zestimate, zestimateLowPercent, zestimateHighPercent` | Zillow's value estimate and its range in percent |
| `rentZestimate` | Zillow's monthly rent estimate (needs 'Include photos', the default) |
| `homeStatus / homeType` | FOR_SALE, SOLD, RECENTLY_SOLD, PENDING, FOR_RENT or OTHER (off market); SINGLE_FAMILY, CONDO, ... |
| `price` | Asking or sale price. Omitted off market, where Zillow's own price field is just the Zestimate |
| `lastSoldPrice / dateSold` | Most recent sale and its date (YYYY-MM-DD) |
| `bedrooms, bathrooms, livingArea, lotSizeSqft, yearBuilt` | Core facts; lot size converted to square feet |
| `daysOnZillow, propertyTaxRate, monthlyHoaFee` | Days on Zillow, property tax rate in percent, monthly HOA fee |
| `taxAssessedValue / taxAssessedYear` | The latest county assessed value and its year |
| `description` | The listing's description |
| `listingAgent, listingAgentPhone, listingAgentEmail, listingAgentLicense` | The listing agent as published on the listing |
| `listingBroker, listingBrokerPhone, buyerAgent, buyerBroker, mlsId, mlsName` | Brokerage, the buyer's side on a sale, and the MLS |
| `photos / photoCount` | The photo gallery, each {url, width, caption} at the largest size Zillow serves |
| `priceHistory` | Every listing, price change and sale: {date, event, price, pricePerSquareFoot, priceChangeRate, source, mlsNumber, buyerAgent, sellerAgent} |
| `taxHistory` | Per year: {year, taxPaid, assessedValue, taxIncreaseRate, valueIncreaseRate} |
| `schools` | Assigned schools: {name, rating, distanceMiles, level, grades, type, district, students, studentTeacherRatio, link} plus GreatSchools sub-ratings |
| `nearbyHomes` | Nearby homes Zillow lists: {zpid, address, price, bedrooms, bathrooms, livingArea, homeStatus, url} |
| `resoFacts / atAGlanceFacts` | Zillow's facts and features: parking, heating, cooling, appliances, HOA, construction, ... |
| `femaFloodZone, femaZoneSubtype, inSpecialFloodHazardArea, baseFloodElevationFt` | FEMA's flood zone at the home's point (National Flood Hazard Layer); omitted where FEMA has no digital map |

Sample:

```json
{
  "query": "827 Krenson Woods Ln, Lakeland, FL 33813",
  "found": true,
  "zpid": 119984411,
  "url": "https://www.zillow.com/homedetails/827-Krenson-Woods-Ln-Lakeland-FL-33813/119984411_zpid/",
  "address": "827 KRENSON WOODS LANE",
  "city": "Lakeland",
  "state": "FL",
  "zip": "33813",
  "county": "Polk County",
  "fips": "12105",
  "apn": "232912140174000660",
  "latitude": 27.969788,
  "longitude": -81.97075,
  "homeStatus": "SOLD",
  "homeType": "SINGLE_FAMILY",
  "price": 262500,
  "zestimate": 264200,
  "rentZestimate": 2100,
  "lastSoldPrice": 262500,
  "dateSold": "2024-05-06",
  "bedrooms": 3,
  "bathrooms": 2,
  "livingArea": 1356,
  "lotSizeSqft": 5497,
  "yearBuilt": 2013,
  "propertyTaxRate": 1.54,
  "monthlyHoaFee": 33,
  "taxAssessedValue": 235922,
  "taxAssessedYear": 2025,
  "listingAgent": "Aimee Millan",
  "listingAgentPhone": "813-766-6853",
  "listingBroker": "DALTON WADE INC",
  "buyerAgent": "Rochele Minerd",
  "mlsId": "U8230568",
  "priceHistory": [
    {
      "date": "2024-05-06",
      "event": "Sold",
      "price": 262500,
      "pricePerSquareFoot": 194,
      "source": "Stellar MLS"
    }
  ],
  "taxHistory": [
    {
      "year": 2025,
      "taxPaid": 3168.22,
      "assessedValue": 235922
    }
  ],
  "schools": [
    {
      "name": "Medulla Elementary School",
      "rating": 6,
      "distanceMiles": 0.2,
      "level": "Elementary",
      "grades": "PK-5"
    }
  ],
  "femaFloodZone": "X (unshaded)",
  "inSpecialFloodHazardArea": false
}
```

### Inputs

| Field | Required | Type | Default | Description |
|---|---|---|---|---|
| `addresses` | no | array | `["745 Garland Dr, Palo Alto, CA 94303", "827 Krenson Woods Ln, Lakeland, FL 33813"]` | Full US street addresses, one per line, e.g. '745 Garland Dr, Palo Alto, CA 94303'. Each is matched to Zillow's own record for that house number; an address Zillow has no home for comes back as a free not-found row. |
| `address` | no | string | — | One address, for callers that send a single string. Combined with 'Property addresses'. |
| `urls` | no | array | `[]` | Zillow home pages (e.g. https://www.zillow.com/homedetails/745-Garland-Dr-Palo-Alto-CA-94303/19470055_zpid/) or bare zpids (19470055). |
| `searchUrls` | no | array | `[]` | Zillow search pages (a city, ZIP or map search with your filters, copied from the browser address bar). Every home the search lists is looked up in full, up to 'Max homes per search'. |
| `maxItems` | no | integer | `50` | How many homes to take from each search URL (Zillow lists up to about 820 per search). Addresses and URLs are not limited by this. |
| `includePhotos` | no | boolean | `true` | The full photo gallery (largest size), the photo count and the rent Zestimate come from the home's page, one more request per home. Turn off for faster runs without photos. |
| `includeFloodZone` | no | boolean | `true` | The FEMA flood zone at the home's own point (FEMA's National Flood Hazard Layer): zone, subtype, whether it is in the Special Flood Hazard Area, and the base flood elevation where FEMA publishes one. FEMA's map service is the slow leg (about 10 s per group of 5 homes); turn this off for the fastest run. |

### Pricing (Pay Per Event)

You pay per result (`property-details`) — **no charge for empty runs**. Example: **1000 home found** at *$0.0028/result* ≈ **$2.80**.

Illustrative: 1,000 homes found at $0.0028 each. Not-found and refused lookups are free.

### Use cases

- Price a lead list: addresses in, Zestimate, rent Zestimate, last sale and tax history out.
- Pull every home in a Zillow search (a city, ZIP or map area with your filters) as full records.
- Join Zillow to county data: every row carries the APN and county FIPS.
- Flood screening: the FEMA zone and Special Flood Hazard Area flag on every home.
- Agent prospecting: the listing agent's phone, email and licence number on listed and recently sold homes.

### Why this actor

- Three ways in: street addresses, Zillow links or zpids, and Zillow search URLs, in one run.
- No browser: Zillow's own data, read directly, five homes at a time, so batches are quick and cheap to run.
- Public-record extras on every row: APN, county FIPS, county assessed value with its year, and the FEMA flood zone at the home's point.
- Honest rows: unknown fields are left out rather than guessed, an off-market home's 'price' (which on Zillow is just the Zestimate) is not passed off as a price, and misses are free.

### Limitations & updates

US homes on Zillow only. Zillow sits behind PerimeterX, so a lookup can be refused after three fresh residential IPs; it then comes back as a free row that says so. The photos, the rent Zestimate and the Zestimate range come from the home's page; when that page is refused, the row still carries the rest of the record without them. Fields Zillow does not have for a home are left out of its row. The FEMA flood zone is FEMA's mapped zone at the home's point, not a flood-insurance determination, and is absent where FEMA has no digital map. Zillow lists up to about 820 homes per search.

### FAQ

**What can I give it?**

Full US street addresses ('745 Garland Dr, Palo Alto, CA 94303'), Zillow home URLs or bare zpids, and Zillow search URLs. Mix them in one run. A search URL is any Zillow search page you would share from your browser: a city, a ZIP, a drawn map area, with your filters. 'Max homes per search' caps how many homes each search contributes (default 50).

**How am I charged?**

One 'Home found' event per home delivered with its record. An address Zillow has no home for, a link that is not a Zillow home, and a lookup Zillow refused are all free rows that say why. When your run's maximum charge is reached, the run stops and a free row lists what was not delivered.

**How is an address matched?**

Zillow's own address suggestions give the home; the actor keeps it only when its house number is the one you asked for, so a neighbouring house is never billed as your address. Give the full address with city, state and ZIP.

**Where do the flood zone and APN come from?**

The APN and county FIPS are in Zillow's record (from the county). The flood zone is looked up separately at the home's latitude and longitude in FEMA's National Flood Hazard Layer, the official effective flood map: zone (e.g. AE, or X shaded / unshaded), subtype, whether the point is in the Special Flood Hazard Area, and the base flood elevation where FEMA publishes one. Where FEMA has no digital map, those fields are left out. Turn it off with 'Include FEMA flood zone' for a faster run.

**Why is 'price' missing on some homes?**

For a home that is not listed and not recently sold, Zillow's own price field just repeats the Zestimate, so the actor leaves 'price' out there; the Zestimate is in 'zestimate' and the last sale in 'lastSoldPrice' and 'dateSold'.

**Does it return photos?**

Yes, by default: the full gallery at the largest size Zillow serves, with the photo count. The photos, the rent Zestimate and the Zestimate range come from the home's page, one more request per home; turn off 'Include photos' if you do not need them and want a faster run.

**Is there a Redfin version?**

Yes: Zillow & Redfin Property Data Scraper looks an address up on Redfin first (the Redfin Estimate, First Street climate-risk scores, MLS amenities, floor plans) and falls back to Zillow. This actor is Zillow's own record, by address, link or search.

**Is this personal data?**

It returns public property facts and the agent and brokerage contact details published on the listing, which are business contact information. There is no owner name, owner phone or occupant data.

### Which actor to choose

For the same homes on Redfin, or by parcel number:

- **Zillow & Redfin Property Data Scraper** — You want Redfin's record too: the Redfin Estimate, First Street climate-risk scores, MLS amenities and floor plans, with Zillow as the fallback.
- **US Property Lookup & Listing Scraper by APN/Parcel** — You start from a county parcel number instead of an address.

### Guides & use cases

Written up on **[scrapebench.dev](https://scrapebench.dev)** — the bench that runs and verifies this actor against the live source every night:

- **How-to:** [How to run Zillow Property Details Scraper: Zestimate, History & Records](https://scrapebench.dev/guides/how-to-zillow-property-details-scraper/)
- **Use case:** [Price a Lead List with Zillow: Zestimate, Rent and Flood Zone per Address](https://scrapebench.dev/use-cases/zillow-lead-list-zestimate-flood-zone/)

More actors, coverage and nightly verification results: **[scrapebench.dev](https://scrapebench.dev)**

### Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the [MCP tab](https://apify.com/scrapebench/zillow-property-details-scraper/api/mcp) on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

> "Get the Zillow details for 827 Krenson Woods Ln, Lakeland, FL 33813: Zestimate, rent estimate, price history and flood zone."

Give the full street address with ZIP; the home is matched by house number, so a partial address comes back as not found rather than a neighbour. Runs started this way bill exactly like any other run.

### Data & lawful use

This actor collects publicly available information that Zillow Group, plus the Federal Emergency Management Agency (FEMA) for flood zones publishes for public
lookup — licence records, business listings and the contact details professionals list there.
Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any
names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the
controller of that data and we act only as your processor (Apify Standard Actor Contract).
You need a lawful basis for your use, must honour opt-out and deletion requests, and must
follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar).
Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or
for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and
don't sell or share them.

### Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by
Zillow Group, plus the Federal Emergency Management Agency (FEMA) for flood zones. Names and marks are used only to describe the data source. Records are
provided as published by the source and may be out of date or incomplete. For anything
consequential (hiring, a permit, a legal decision), confirm the record with the issuing
agency. You are responsible for making sure your use complies with applicable law and the
source's terms.

### Need help?

Open an issue on this actor's **Issues** tab and we'll respond there. Bug reports, missing
fields and feature requests are all welcome. Guides and examples: [scrapebench.dev](https://scrapebench.dev).

If you are a person named in this data and want your record removed from our copy, email
apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: [Apify Console → Settings → Security → Share run data with developers](https://console.apify.com/settings/security). It lets us see exactly what went wrong and keep improving the actor.

If this actor saved you time, a short review on its Store page helps other buyers find it.

# Actor input Schema

## `addresses` (type: `array`):

Full US street addresses, one per line, e.g. '745 Garland Dr, Palo Alto, CA 94303'. Each is matched to Zillow's own record for that house number; an address Zillow has no home for comes back as a free not-found row.

## `address` (type: `string`):

One address, for callers that send a single string. Combined with 'Property addresses'.

## `urls` (type: `array`):

Zillow home pages (e.g. https://www.zillow.com/homedetails/745-Garland-Dr-Palo-Alto-CA-94303/19470055_zpid/) or bare zpids (19470055).

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

Zillow search pages (a city, ZIP or map search with your filters, copied from the browser address bar). Every home the search lists is looked up in full, up to 'Max homes per search'.

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

How many homes to take from each search URL (Zillow lists up to about 820 per search). Addresses and URLs are not limited by this.

## `includePhotos` (type: `boolean`):

The full photo gallery (largest size), the photo count and the rent Zestimate come from the home's page, one more request per home. Turn off for faster runs without photos.

## `includeFloodZone` (type: `boolean`):

The FEMA flood zone at the home's own point (FEMA's National Flood Hazard Layer): zone, subtype, whether it is in the Special Flood Hazard Area, and the base flood elevation where FEMA publishes one. FEMA's map service is the slow leg (about 10 s per group of 5 homes); turn this off for the fastest run.

## Actor input object example

```json
{
  "addresses": [
    "745 Garland Dr, Palo Alto, CA 94303",
    "827 Krenson Woods Ln, Lakeland, FL 33813"
  ],
  "urls": [],
  "searchUrls": [],
  "maxItems": 50,
  "includePhotos": true,
  "includeFloodZone": true
}
```

# Actor output Schema

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

Each row is one home you asked for (or one home from a search).

# 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 = {
    "addresses": [
        "745 Garland Dr, Palo Alto, CA 94303",
        "827 Krenson Woods Ln, Lakeland, FL 33813"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapebench/zillow-property-details-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 = { "addresses": [
        "745 Garland Dr, Palo Alto, CA 94303",
        "827 Krenson Woods Ln, Lakeland, FL 33813",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("scrapebench/zillow-property-details-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 '{
  "addresses": [
    "745 Garland Dr, Palo Alto, CA 94303",
    "827 Krenson Woods Ln, Lakeland, FL 33813"
  ]
}' |
apify call scrapebench/zillow-property-details-scraper --silent --output-dataset

```

## MCP server setup

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