# Zillow Scraper - $0.80 per 1,000, Search & Details (`dami_studio/zillow-property-details-scraper`) Actor

Zillow scraper at $0.0008 per property ($0.80 per 1,000) plus a $0.001 run-start fee. Search results AND full listing details from one Actor: price, beds, baths, sqft, address, photos, price history, tax history and schools, at no surcharge. No login, no API key. Screen entire markets in seconds.

- **URL**: https://apify.com/dami\_studio/zillow-property-details-scraper.md
- **Developed by:** [Dami's Studio](https://apify.com/dami_studio) (community)
- **Categories:** Real estate, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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/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 Scraper — Search Results and Full Listing Details

**$0.80 per 1,000 properties** ($0.0008 each), plus $0.001 each time a run starts — a flat rate on
every plan, with search results *and* full listing details coming from this one Actor rather than
from two separate ones you have to stitch together.

**Scrape any Zillow search or listing URL and get the full picture** — price, beds, baths, sqft,
address, photos, price history, Zestimate and school ratings. 80 properties in under 20 seconds.

Feed it a city search and get every result; feed it a listing and get everything Zillow shows.
**No login, no API key, no browser to babysit.**

### Who uses this

- **Investors** screening entire markets in seconds instead of clicking through listings.
- **Agents** building comps for a valuation in one run.
- **PropTech teams** powering valuation and lead-scoring models.
- **Analysts** tracking price movements across a ZIP or metro over time.

### What you get for $0.0008 a property

| | This Actor |
|---|---|
| Price per property | **$0.0008**, flat — no volume tiers, no plan gates |
| Run-start fee | **$0.001** per run, whatever the run returns |
| Search **and** detail pages | **Both, one Actor** — search cards and `/homedetails/` records |
| Price history, tax history + schools | **Included**, no surcharge, via `includeHistory` / `includeSchools` |
| Photos | **Included**, via `includePhotoUrls` |
| Login or API key | **Never** |
| Charged on failure | **No** — blocked, not-found and no-result rows are uncharged |

### Frequently asked questions

**Do I need a Zillow account or API key?** No. Paste a public URL.

**Can I scrape a whole city?** Yes — pass a Zillow search URL and set `maxSearchResultsPerUrl`.

**Does it return price history and schools?** Yes, with `includeHistory` and `includeSchools`.

**Can I get photos?** Yes, via `includePhotoUrls`.

**Am I charged when a listing cannot be read?** Not the per-result fee — only the $0.001 run-start fee. Failures are returned as uncharged diagnostics.

**What does a run cost?** $0.0008 per property plus $0.001 per run start. 1,000 properties is
$0.80 in result fees; a single run of five search URLs at 50 cards each returns up to 250
properties for $0.201 all-in. Price history, tax history, schools and photos do not change the
per-property price.

The actor does **not** require a Zillow login, an API key, or a private data source. It reads the
public page over plain HTTP — no browser to launch, which is why runs are fast and cheap — and can
retry a blocked page once through a rotating United States datacenter proxy when you enable that option.

### Input

```json
{
  "searchUrls": ["https://www.zillow.com/austin-tx/"],
  "maxSearchResultsPerUrl": 10,
  "propertyUrls": [
    "https://www.zillow.com/homedetails/7300-Quicksilver-Cir-Austin-TX-78744/29508680_zpid/"
  ],
  "includePhotoUrls": true,
  "includeHistory": true,
  "includeSchools": true,
  "enableResidentialFallback": false
}
```

`searchUrls` accepts up to five public Zillow result pages. Choose the location and any
public filters in Zillow first, then paste the browser URL. Each page is loaded once and
the actor emits at most `maxSearchResultsPerUrl` (1-50, default 10) deduplicated listing
cards. It does not call undocumented or private Zillow APIs, expand maps, or paginate.

`propertyUrls` accepts up to 10 canonical public Zillow `/homedetails/` URLs. The actor
removes tracking parameters and deduplicates identical URLs. Supplying neither input
returns one clearly labelled `_sample: true` row and does not charge a result event.

### Output

Every genuine public property record has `ok: true` and includes:

- `zpid`, `url`, `address`, `streetAddress`, `city`, `state`, `zipcode`, and `county`
- `homeStatus`, `homeType`, `price`, `bedrooms`, `bathrooms`, `livingArea`, `lotSize`, and `yearBuilt`
- `zestimate`, `rentZestimate`, `daysOnZillow`, description, broker/agent attribution when public
- public `photos`, `priceHistory`, `taxHistory`, and `schools` when enabled and rendered by Zillow
- `transport` showing `direct_http` on the first pass, or `datacenter_http` / `customer_http` / `isp_http` when the optional retry produced the row

Zillow omits fields for some properties and statuses. Such fields are `null` or an empty
array; this does not make an otherwise public record invalid.

Search results have `type: "search_listing"` and include the public card fields Zillow
renders: `zpid`, `url`, `address`, price, beds, baths, living area, Zestimate, status,
photo URL when available, `searchUrl`, and `rank`. Search cards do not claim detail-only
fields such as history or school data.

### Charging and proxy behavior

The actor charges the `property` event only after it pushes a genuine `ok: true` property
or search-listing record. It never charges sample, invalid-input, blocked, rate-limited,
not-found, or no-results diagnostic rows.

Direct traffic is always attempted first. When `enableResidentialFallback` is
off, a Zillow block returns an uncharged `BLOCKED` row. When it is on, the actor performs
at most **one** proxy retry per blocked property or result page.

That retry never uses a metered proxy group. Apify Residential and SERP are billed per
gigabyte, so a request for either group is replaced with rotating datacenter addresses and
the substitution is reported back on the affected rows in a `proxyNotice` field. If you
supply your own proxy servers in `proxyConfiguration.proxyUrls` they are used exactly as
given, in the order given, and are never substituted.

### Responsible use

This actor reads public listing pages only. It does not use login credentials, CAPTCHA
solving, hidden endpoints, session cookies, or fingerprint masking. Use public data
responsibly and ensure your workflow complies with Zillow's terms and applicable privacy
and data-use laws.

### Billing

Two charges apply: a **$0.001 run-start fee** each time a run begins, and **$0.0008 per property returned** — $0.80 per 1,000. Flat rate, no volume tiers, no plan gates. Samples, diagnostics, duplicates, blocked look-ups and no-result runs **never incur the per-result fee** — a run that returns nothing costs only the $0.001 start fee.

# Actor input Schema

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

Public Zillow /homedetails/ listing URLs to enrich. Empty input returns one clearly labelled, uncharged sample row.

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

Public Zillow result-page URLs copied from your browser after selecting a location and any public filters. Each URL is fetched once; no hidden or private Zillow endpoint is used.

## `maxSearchResultsPerUrl` (type: `integer`):

Cap public listing rows emitted from each supplied result page. Lower limits reduce traffic and cost.

## `includePhotoUrls` (type: `boolean`):

Include public listing photo URLs when Zillow renders them in the current property data.

## `includeHistory` (type: `boolean`):

Include publicly rendered price and tax history when Zillow provides it for the property.

## `includeSchools` (type: `boolean`):

Include publicly rendered nearby-school summaries when Zillow provides them for the property.

## `enableResidentialFallback` (type: `boolean`):

The actor always attempts direct browser traffic first. Enable this to retry each blocked URL once through the proxy below. Metered proxy groups (Residential, SERP) are not offered by this actor and are replaced with rotating datacenter addresses; your own proxy servers are used exactly as supplied.

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

Used only after a direct browser block, when the retry option above is enabled. The default is a rotating United States Apify datacenter proxy. Requests for the Residential or SERP groups are replaced with datacenter addresses; a custom proxy server list is honoured verbatim.

## Actor input object example

```json
{
  "propertyUrls": [],
  "searchUrls": [],
  "maxSearchResultsPerUrl": 10,
  "includePhotoUrls": true,
  "includeHistory": true,
  "includeSchools": true,
  "enableResidentialFallback": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "BUYPROXIES94952"
    ],
    "countryCode": "US"
  }
}
```

# Actor output Schema

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

One dataset row per successfully extracted public Zillow property or result-page listing. Empty input and blocked or invalid URLs return uncharged labelled rows.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dami_studio/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 = {}

# Run the Actor and wait for it to finish
run = client.actor("dami_studio/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 '{}' |
apify call dami_studio/zillow-property-details-scraper --silent --output-dataset

```

## MCP server setup

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