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

{ "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.