# Zillow Search Scraper: Homes for Sale, Rent and Sold (`v0iddo/mint-zillow-scraper`) Actor

Scrape Zillow search results for homes for sale, rentals and recently sold properties: price, address, beds, baths, living area, lot size, home type, days on Zillow, coordinates and listing brokerage. Search by city, ZIP code or a pasted Zillow URL.

- **URL**: https://apify.com/v0iddo/mint-zillow-scraper.md
- **Developed by:** [vøiddo](https://apify.com/v0iddo) (community)
- **Categories:** Real estate, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.05 / 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/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 Search Scraper: Homes for Sale, Rent and Sold

Scrape Zillow search results for homes for sale, rentals and recently sold properties: price, address, beds, baths, living area, lot size, home type, days on Zillow, coordinates and listing brokerage. Search by city, ZIP code or a pasted Zillow URL.

### What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API. The main fields:

| Field | Meaning |
|---|---|
| `address` | Address |
| `priceText` | Price |
| `beds` | Beds |
| `baths` | Baths |
| `livingArea` | Living area (sq ft) |
| `homeType` | Home type |
| `status` | Status |
| `daysOnZillow` | Days on Zillow |
| `brokerName` | Brokerage |
| `url` | Listing |

Example row:

```json
{
  "zpid": "70345655",
  "address": "3207 Wickham Ln, Austin, TX 78725",
  "street": "3207 Wickham Ln",
  "city": "Austin",
  "state": "TX",
  "zipcode": "78725",
  "price": 324900,
  "priceText": "$324,900",
  "beds": 4,
  "baths": 3,
  "livingArea": 2575,
  "lotArea": 4800,
  "homeType": "SINGLE_FAMILY",
  "status": "FOR_SALE",
  "daysOnZillow": 136,
  "latitude": 30.232096,
  "longitude": -97.5937,
  "brokerName": "T J Lewis Real Estate",
  "soldDate": null,
  "imgSrc": "https://photos.zillowstatic.com/fp/b02454094c9c6df9b223215e728c4bef-p_e.jpg",
  "url": "https://www.zillow.com/homedetails/3207-Wickham-Ln-Austin-TX-78725/70345655_zpid/"
}
```

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `locations` | array | no | Cities, ZIP codes or neighborhoods such as Austin, TX or 78701. One search is run per entry. |
| `listingType` | select | no | Which Zillow listings to read for the locations above. Allowed: for_sale, for_rent, sold. Default: `"for_sale"`. |
| `searchUrls` | array | no | Search result pages copied from your browser, for example https://www.zillow.com/austin-tx/ or a filtered search. Filters in the URL are kept. |
| `maxItems` | integer | no | The run stops after this many result rows. It also caps what one run can cost. Default: `100`. |
| `proxyConfiguration` | object | no | Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network. |

Example input:

```json
{
  "locations": [
    "Austin, TX"
  ],
  "listingType": "for_sale",
  "maxItems": 20
}
```

### Pricing

You pay per result row in the dataset (the current price per 1,000 results is on the Pricing tab). A run that finds nothing produces no rows and no result charges. Set **Maximum results** to cap what a single run can cost.

### Limits and notes

- Zillow shows at most about 820 listings (20 pages) per search. For a bigger area, run several ZIP codes or neighborhoods instead of one city.
- Rental searches mostly return apartment buildings: those rows have a price range, the building name and a list of unit types in units, and no beds or baths of their own.
- Sold prices are hidden by Zillow in states that do not disclose them (for example Texas); price is empty there.
- lotArea is in square feet. Rows are unique by Zillow property ID across all searches of a run.
- Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
- The actor reads only pages that the site's robots.txt leaves open to automated access.
- Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
- Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem") and whether the account is on a paid Apify plan. It contains nothing from your input or results.

### Use it from your code or agent

Run it from the Apify Console, on a schedule, through the Apify API and client libraries, from Make, Zapier or n8n, or as a tool through the Apify MCP server. The dataset of each run stays available for download.

# Actor input Schema

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

Cities, ZIP codes or neighborhoods such as Austin, TX or 78701. One search is run per entry.

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

Which Zillow listings to read for the locations above.

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

Search result pages copied from your browser, for example https://www.zillow.com/austin-tx/ or a filtered search. Filters in the URL are kept.

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

The run stops after this many result rows. It also caps what one run can cost.

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

Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

## Actor input object example

```json
{
  "locations": [
    "Austin, TX"
  ],
  "listingType": "for_sale",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

One dataset row per processed item.

# 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"
    ],
    "listingType": "for_sale",
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("v0iddo/mint-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"],
    "listingType": "for_sale",
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("v0iddo/mint-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"
  ],
  "listingType": "for_sale",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call v0iddo/mint-zillow-scraper --silent --output-dataset

```

## MCP server setup

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