# Zillow Property Scraper (`mina_safwat/zillow-scraper`) Actor

Scrapes Zillow listings — prices, beds, baths, size, Zestimate, coordinates, and days on market.

- **URL**: https://apify.com/mina_safwat/zillow-scraper.md
- **Developed by:** [Mina](https://apify.com/mina_safwat) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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.

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

Scrape **Zillow property listings**: prices, bedrooms, bathrooms, square footage, lot size, coordinates, days on market, and the Zestimate when Zillow shows one. No Zillow account or API key is needed.

### What does Zillow Property Scraper do?

Give it a city and state, or a ZIP code, and it returns the [Zillow](https://www.zillow.com) listings there as **structured data**: address, price, beds and baths, living area and lot size, home type, days on Zillow, exact coordinates, listing broker, photo, and a link to the listing. When Zillow shows a **Zestimate** or **rent Zestimate** on the card, you get those too.

It covers homes **for sale**, homes **for rent**, and **recently sold** properties, with the sale date on sold homes.

Running it on Apify adds an API, scheduling, integrations (Google Sheets, Slack, Zapier, Make, S3), proxy rotation, and run monitoring.

### Why use Zillow Property Scraper?

- **Investment analysis**: pull a market's listings with price, size, and location to spot value.
- **Comparative market analysis**: gather comparable listings and recent sales for a valuation.
- **Rental research**: see what comparable homes and apartments rent for in a neighbourhood.
- **Lead generation for agents**: track new listings and price cuts as they appear.
- **Market monitoring**: schedule it and watch inventory and pricing move over time.

### How to scrape Zillow listings

1. Enter one or more **Locations**, such as `Austin, TX` or `78704`.
2. Choose a **Listing type**: for sale, for rent, or sold.
3. Set **Max results per location**, add any filters, and click **Start**.
4. Watch results appear in the **Output** tab, then download or connect them by API.

### Input

Everything is set on the **Input** tab. Only `locations` is required.

| Field | Description |
| --- | --- |
| `locations` | Places to search, one per line. Use `City, ST` or a ZIP code. |
| `listing_type` | `For sale` (default), `For rent`, or `Sold`. |
| `max_results_per_location` | Cap for each location, 1 to 800 (default 100). |
| `price_min` / `price_max` | Price range. For a rent search, the monthly rent. |
| `min_beds` / `min_baths` | Fewest bedrooms and bathrooms. For apartment buildings, see the note below. |
| `home_types` | Single family, condo, townhouse, multi-family, apartment, manufactured, or lot. Leave empty for all. Apartment buildings count as `APARTMENT`. |
| `proxy_type` | `Apify residential` (default), `Apify datacenter`, or `No proxy`. |
| `custom_proxy_urls` | Optional proxies of your own, as `http://user:pass@host:port`. They are used instead of Apify's. |
| `proxy_country` | Comma-separated country codes for Apify's proxies (default `US`). |

```json
{
  "locations": ["Austin, TX", "78704"],
  "listing_type": "For sale",
  "max_results_per_location": 100,
  "price_max": 600000,
  "min_beds": 3,
  "home_types": ["SINGLE_FAMILY", "TOWNHOUSE"],
  "proxy_type": "Apify residential"
}
```

**Filters on apartment buildings.** Rent searches mostly return whole buildings, each with several floor plans. A building is kept when at least one floor plan fits both your price range and `min_beds`. The row still lists all its floor plans. Floor plans show no bathroom count, so `min_baths` doesn't remove buildings.

### Output

Each listing is one row:

```json
{
  "zpid": "251032876",
  "url": "https://www.zillow.com/homedetails/5700-Bell-Tower-Ln-Austin-TX-78747/251032876_zpid/",
  "status": "FOR_SALE",
  "status_text": "Active",
  "price": 330000,
  "price_label": "$330,000",
  "currency": "USD",
  "zestimate": 322600,
  "rent_zestimate": 2385,
  "beds": 4,
  "baths": 4,
  "living_area": 2302,
  "lot_area": 0.15,
  "lot_area_unit": "acres",
  "home_type": "SINGLE_FAMILY",
  "days_on_zillow": 3,
  "address": "5700 Bell Tower Ln, Austin, TX 78747",
  "street": "5700 Bell Tower Ln",
  "city": "Austin",
  "state": "TX",
  "zipcode": "78747",
  "latitude": 30.137547,
  "longitude": -97.770775,
  "is_building": false,
  "broker": "Example Realty",
  "image": "https://photos.zillowstatic.com/fp/example-p_e.jpg",
  "listing_note": "Showcase",
  "location_searched": "Austin, TX"
}
```

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

#### Data fields

| Field | Description |
| --- | --- |
| `zpid`, `url` | Zillow's listing ID (as text) and the link to the listing. |
| `status`, `status_text` | Market status, such as `FOR_SALE`, and the label Zillow shows. |
| `price`, `price_label`, `currency` | Price as a number, as displayed, and its currency (`USD`). |
| `zestimate`, `rent_zestimate` | Zillow's valuation and rent estimate, when Zillow shows one. Roughly 1 in 5 listings in a typical search has them. |
| `beds`, `baths`, `living_area` | Bedrooms, bathrooms, and living area in square feet. |
| `lot_area`, `lot_area_unit` | Lot size and its unit (`sqft` or `acres`). |
| `home_type`, `days_on_zillow` | Property type and time on the market. |
| `address`, `street`, `city`, `state`, `zipcode` | Address, whole and in parts. |
| `latitude`, `longitude` | Exact position. |
| `broker`, `image`, `is_zillow_owned`, `listing_note` | Listing brokerage, main photo, Zillow-owned flag, and any badge Zillow shows. |
| `is_building`, `location_searched` | Whether the row is an apartment building, and which of your locations found it. |

**Rental searches.** Most rows are apartment buildings, returned as one row with `is_building: true` and `home_type: "APARTMENT"`. Their `price` is the cheapest floor plan, and a `units` list gives each floor plan's price and bedrooms. A building has no single bed, bath, or size figure, and no `days_on_zillow`, `broker`, lot size, or Zestimate.

**Sold searches.** Each row adds `date_sold` (as `YYYY-MM-DD`), and `price` is the sale price. Some states, including **Texas**, don't disclose sale prices. Sold homes there come back with no `price`, `price_label`, or `currency`, and any price filter removes every row. Sold searches in Seattle or Denver, for example, have prices on every row.

### How much does it cost to scrape Zillow?

The Actor uses pay-per-event pricing, with no separate charge for compute or proxies:

- **$0.00005** per run start, charged per GB of memory, so once at the default 1 GB
- **$0.002** per listing saved to the dataset

That comes to **about $2.00 per 1,000 results**. A 100-listing run costs about $0.20. Apify's free plan includes $5 of monthly credit, enough for roughly 2,500 listings.

You are only charged for listings in the dataset. Locations that return nothing are listed in the `FAILED_INPUTS` record and are not billed.

### Tips for scraping Zillow at scale

- **Zillow limits search depth.** A search pages only about 20 deep, roughly 800 listings, however many match. A city reporting 5,000 results still returns only part of them. To cover a whole market, run several narrower searches by ZIP code. The run log tells you the ceiling for each search.
- **Filters are applied to the results, not the search.** Zillow's own URL filters are unreliable, so the Actor reads listings and then filters them. A narrow filter can return fewer rows than your limit, and the log reports how many were filtered out. On rent searches, buildings are matched floor plan by floor plan (see **Input**).
- **Compare `price` with `zestimate`** on listings that have one to spot homes listed below Zillow's own valuation.
- **`days_on_zillow` finds stale listings**, which are often the negotiable ones.
- **Schedule it** on the same searches to build an inventory and pricing history.

### FAQ, disclaimers, and support

**Does it need a Zillow account or API key?** No. It reads publicly visible search results.

**A location returned nothing. Why?** Check the `FAILED_INPUTS` record in the run's key-value store and the run's status message. They name each location that gave no listings, or stopped early, and why. Zillow may have no page for that place (check the spelling or use a ZIP code). The search may have no listings, or none matched your filters. Zillow may have refused every attempt, or the proxy couldn't connect. A refusal is never reported as "no results".

If nothing was collected and Zillow refused every search, the run is marked as failed. A mistyped place doesn't change that. Retry, or switch the proxy type. If refusals keep happening, set **Your own proxy URLs**. A run with no `locations` also fails, with a status message saying what to enter.

**Why are some fields empty?** Not every listing publishes every figure. Most listings have no Zestimate on the search card, and new construction often has none. Apartment buildings and sold homes in non-disclosure states leave the fields described above empty. Missing values come back empty rather than guessed.

**Is scraping Zillow legal?** This Actor collects publicly visible listing data. It does not collect personal information beyond the listing brokerage's business name. Zillow's terms of use prohibit automated collection, and Zillow has pursued scrapers before. You are responsible for how you use the data, including complying with Zillow's terms and local law. If you plan to use it commercially, check with a lawyer first.

Found a bug or need a field that is missing? Open an issue on the Actor's **Issues** tab. Custom scraping solutions are available on request.

# Actor input Schema

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

Places to search, one per line. Use "City, ST" (e.g. "Austin, TX") or a ZIP code (e.g. "78704").

## `listing_type` (type: `string`):

Which market to search.

## `max_results_per_location` (type: `integer`):

Stops after this many listings for each location. Zillow pages a search only about 20 deep (roughly 800 listings), so that is the most one location can return.

## `price_min` (type: `integer`):

Lowest price to include.

## `price_max` (type: `integer`):

Highest price to include.

## `min_beds` (type: `integer`):

Fewest bedrooms to include.

## `min_baths` (type: `integer`):

Fewest bathrooms to include.

## `home_types` (type: `array`):

Restrict to certain property types. Leave empty for all.

## `proxy_type` (type: `string`):

Which addresses to send requests from. Residential is the default and works; switch only if you hit repeated refusals.

## `custom_proxy_urls` (type: `array`):

Proxy URLs as http://user:pass@host:port, one per line. Optional — the Actor works on Apify’s own proxies. Use this if you have proxies you would rather run from, or if you hit repeated refusals on a large job.

## `proxy_country` (type: `string`):

Comma-separated 2-letter codes, used when you are not supplying your own proxies. US addresses look most natural to Zillow.

## Actor input object example

```json
{
  "locations": [
    "Austin, TX"
  ],
  "listing_type": "For sale",
  "max_results_per_location": 100,
  "home_types": [],
  "proxy_type": "Apify residential",
  "custom_proxy_urls": [],
  "proxy_country": "US"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# 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("mina_safwat/zillow-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 = { "locations": ["Austin, TX"] }

# Run the Actor and wait for it to finish
run = client.actor("mina_safwat/zillow-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 '{
  "locations": [
    "Austin, TX"
  ]
}' |
apify call mina_safwat/zillow-scraper --silent --output-dataset

```

## MCP server setup

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