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.

• Pay per result row: the platform usage of the run is included, and a run that finds nothing has no result charges.
• No login, no cookies, no account on Zillow: public pages only.
• Export to JSON, CSV, Excel, XML or HTML, or read the rows through the Apify API.
• Start it from the Console, on a schedule, through the API, or as a tool for agents over MCP.
• Tested every day on its example input, with the rows checked, and repaired when a check fails.

What you can use it for

• Home price research by city or ZIP code, for sale, for rent or recently sold.
• Comparables: beds, baths, living area and price of nearby homes.
• Days on Zillow shows which listings sit and which sell fast.
• Broker market share: count listings per brokerage in an area.

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:

{
  "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/"
}

How to use it

1. Open the Input tab (or call the actor through the API, see below).
2. Fill in Locations, Listing type; the form opens with a working example.
3. Set Maximum results to cap the size and the cost of the run.
4. Click Start. Rows appear on the Output tab while the run works.
5. Download the dataset, or connect it to Google Sheets, Make, Zapier, n8n or a webhook.

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:

{
  "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"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/zillow-scraper").call(run_input={"locations": ["Austin, TX"], "listingType": "for_sale", "maxItems": 20})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/zillow-scraper').call({"locations": ["Austin, TX"], "listingType": "for_sale", "maxItems": 20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~zillow-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"locations": ["Austin, TX"], "listingType": "for_sale", "maxItems": 20}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/zillow-scraper",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Then ask, for example: "List homes for sale in Austin, TX with price, beds, baths and days on Zillow."

FAQ

Do I need an account on Zillow, cookies or an API key?

No. The actor reads only what every visitor of Zillow can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 5,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

How am I charged?

Per result row in the dataset, at the price on the Pricing tab for your Apify plan. The platform usage of the run is included in that price. A run that finds nothing produces no rows and no result charges, and your spending limit for a run is always respected.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects only what Zillow publishes to every visitor, without a login, and it reads only pages that robots.txt leaves open. Public data can still be personal data under laws such as the GDPR, and sites have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when Zillow changes its pages?

Automated tests run the actor every day on the example input and check the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Fotocasa Scraper: Spain Homes for Sale and Rent
• Rightmove Scraper: UK Property for Sale and to Rent