# Zillow Property Listings Scraper (`usestring/zillow-listings`) Actor

Collect for-sale, for-rent and sold property listings from Zillow search results.

- **URL**: https://apify.com/usestring/zillow-listings.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.00 / 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 Scraper — for-sale, for-rent and sold listings

This Actor scrapes Zillow property listings for any US city or region. Give it a location such as
`Austin, TX` and it returns every listing on that Zillow search with **numeric** price, bedrooms,
bathrooms, square footage and coordinates — not display strings you have to clean up afterwards.

No Zillow account, login or cookies are used — this reads what a logged-out visitor sees. Around
**41 listings per location**, one Zillow request each.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `zpid` | string | Zillow's own listing ID — stable across runs, use it to de-duplicate |
| `price` | number | `500000`, not `"$500,000"` |
| `priceText` | string | The formatted price as shown |
| `beds`, `baths` | number | |
| `areaSqft` | number | |
| `address`, `street`, `city`, `state`, `zipcode` | string | Split, not one blob |
| `status` | string | `FOR_SALE`, `FOR_RENT`, `SOLD` |
| `latitude`, `longitude` | number | Exact coordinates, ready to map |
| `brokerName` | string | Listing broker where shown |
| `detailUrl`, `imageUrl` | string | |
| `searchLocation`, `listingType`, `sourceUrl`, `collectedAt` | string | Provenance for every row |

### Input

```json
{ "locations": ["Austin, TX", "Denver, CO"], "listingType": "for_sale", "maxItems": 1000 }
```

| Field | Description |
| --- | --- |
| `locations` | Cities or regions, e.g. `"Austin, TX"`. Required, 1–100. |
| `listingType` | `for_sale` (default), `for_rent` or `sold`. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Locations fetched in parallel. Default 2, maximum 5. |

### Use cases

- Comparable-sales and pricing analysis for a market
- Rental yield and inventory tracking across cities
- Lead lists for agents, brokers and iBuyers
- Feeding a map or dashboard with geocoded inventory
- Monitoring days-on-market and price changes by re-running on a schedule

### Reliability

Measured across 30 US cities in one run: **30/30 locations succeeded, 1,230 listings collected**, and
every field in the schema was populated by at least some rows — no columns that are always empty.

A location that cannot be read is recorded in the run's `SUMMARY` under `failures` rather than
silently returning fewer rows, and a run where every location 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 Scraper reads public Zillow search
pages as a logged-out visitor, and never signs in.

**How many listings does the Zillow Scraper return per location?** Around 41 — one Zillow search page
per location. Ten locations therefore return roughly 410 rows for ten requests.

**Is the price a number or a string?** A number (`price`), with the formatted version alongside
(`priceText`). Beds, baths, square footage and coordinates are numbers too.

**Can I get rentals and sold homes?** Yes. Set `listingType` to `for_rent` or `sold`; the default is
`for_sale`.

**How do I de-duplicate across runs?** Use `zpid`, Zillow's stable listing identifier, which is also
the key the Zillow Property Detail Scraper takes as input.

**Does the Zillow Scraper work outside the US?** No. It targets `zillow.com`, so US listings only.

### Limitations

One search page per location — this is not a full-market crawler, and it does not open individual
listing detail pages for tax history, price history or Zestimate detail. Listings reflect what Zillow
shows publicly at collection time, stamped in `collectedAt`.

### 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

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

Search locations, e.g. "Austin, TX".

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

for\_sale, for\_rent or sold.

## `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
{
  "locations": [
    "Austin, TX"
  ],
  "listingType": "for_sale",
  "maxItems": 1000,
  "concurrency": 2
}
```

# Actor output Schema

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

Collect for-sale, for-rent and sold property listings from Zillow search results.

## `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 = {
    "locations": [
        "Austin, TX"
    ]
};

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

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

```

## MCP server setup

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

```

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/LB5B8CCfCMhcIvq3u/builds/OtGeTS8pZgVs8Rl6J/openapi.json