Zillow Scraper — US Real Estate, Prices, Zestimate | from $3/1K

Scrape Zillow listings by city, ZIP code, or URL. Supports For Sale, For Rent, and Recently Sold. Returns 22+ fields per property including price, Zestimate, beds/baths/sqft, lot size, home type, days on market, broker name, lat/lng, image URLs, and Zillow Property ID (zpid). No API key, no manual browser clicks — pay only for records returned.

Features

• Three listing types: For Sale, For Rent, and Recently Sold
• Rich fields: price, Zestimate, rent Zestimate, beds, baths, sqft, lot area, home type, status, days on market, broker, coordinates, images
• Flexible input: city/state (Austin, TX), ZIP code (90210), or paste a full Zillow search URL
• Filter support: price range, minimum bedrooms, home type (house, condo, townhome, multi-family, land, manufactured)
• Automatic pagination: follows Zillow's next-page links automatically up to your maxItems limit
• Pay-per-result: charged only for records actually delivered — never for blocked pages or empty runs

How to scrape Zillow listings

1. Open the actor and enter a Location (e.g. Seattle, WA or 10001) or paste a Zillow search URL.
2. Pick a Listing type: For Sale, For Rent, or Recently Sold.
3. Optionally set price, bedroom, and home type filters.
4. Set Max listings (default 100; set to 0 for unlimited — be aware costs scale linearly).
5. Leave Proxy configuration at the default Apify Residential US setting — this is required for Zillow.
6. Click Start and wait. Results appear in the dataset as they stream in.

Typical run time for 100 listings: under 60 seconds. For 1,000 listings expect ~3–5 minutes.

How much does it cost?

This actor uses pay-per-result pricing: you pay only for listings actually returned.

Volume	Approximate cost
100 listings	~$0.30
1,000 listings	~$3.00
10,000 listings	~$30.00

Proxy usage (Apify Residential) is billed separately to your Apify account by Apify platform at their standard rates. No external proxy key or subscription needed.

Input

Field	Type	Description
location	string	City/state, ZIP, or neighborhood. Example: Austin, TX or 90210
searchUrl	string	Optional: paste a full Zillow search URL to override location + filters
operation	enum	sale (default), rent, or sold
maxItems	integer	Max records to return (default 100; 0 = unlimited)
priceMin	integer	Minimum price in USD
priceMax	integer	Maximum price in USD
bedsMin	integer	Minimum bedroom count
homeType	enum	house, condo, townhome, multi-family, land, manufactured
proxyConfiguration	proxy	Apify Residential US proxy (required — Zillow blocks datacenter IPs)

Input example

{
  "location": "Austin, TX",
  "operation": "sale",
  "priceMin": 300000,
  "priceMax": 800000,
  "bedsMin": 3,
  "homeType": "house",
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

Output fields

Field	Description
zpid	Zillow Property ID
url	Property detail page URL
price	List price (USD)
sold_price	Sold price (for "Recently Sold" mode)
zestimate	Zillow's automated valuation (when available)
rent_zestimate	Estimated monthly rent (when available)
tax_assessed_value	Tax assessed value
beds	Bedrooms
baths	Bathrooms
sqft	Living area square footage
lot_area_value	Lot size value
lot_area_unit	Lot size unit (sqft or acres)
home_type	SINGLE_FAMILY, CONDO, TOWNHOUSE, etc.
status	FOR_SALE, FOR_RENT, RECENTLY_SOLD
status_text	Human-readable status (e.g. "Active", "For Sale (Broker)")
days_on_zillow	Days the listing has been on Zillow
date_sold	Sale date (YYYY-MM-DD, for sold listings)
address	Full address string
address_street	Street address
address_city	City
address_state	State code (e.g. TX)
address_zipcode	ZIP code
lat	Latitude
lng	Longitude
broker_name	Listing broker/agency name
image_urls	Array of full-resolution photo URLs
image_count	Number of photos
thumbnail	Primary photo URL

Output example

{
  "zpid": "29391332",
  "url": "https://www.zillow.com/homedetails/4608-Wally-Ave-Austin-TX-78721/29391332_zpid/",
  "price": 495000.0,
  "sold_price": null,
  "zestimate": null,
  "rent_zestimate": null,
  "tax_assessed_value": 387930.0,
  "beds": 3,
  "baths": 2.0,
  "sqft": 1200,
  "lot_area_value": 6982.668,
  "lot_area_unit": "sqft",
  "home_type": "SINGLE_FAMILY",
  "status": "FOR_SALE",
  "status_text": "Active",
  "days_on_zillow": 5,
  "date_sold": null,
  "address": "4608 Wally Ave, Austin, TX 78721",
  "address_street": "4608 Wally Ave",
  "address_city": "Austin",
  "address_state": "TX",
  "address_zipcode": "78721",
  "lat": 30.281445,
  "lng": -97.684395,
  "broker_name": "Sprout Realty",
  "image_urls": ["https://photos.zillowstatic.com/fp/..."],
  "image_count": 40,
  "thumbnail": "https://photos.zillowstatic.com/fp/...",
  "search_location": "Austin, TX",
  "operation": "sale",
  "page_number": 1,
  "scraped_at": "2026-06-07T16:52:30+00:00"
}

Proxy requirement

Zillow requires a residential proxy for reliable access — datacenter IPs are not reliable. Apify Residential proxy (US) is required. The actor is pre-configured to use Apify's standard proxyConfiguration input — no external proxy account, API key, or subscription needed. Proxy compute is billed to your Apify run at Apify's standard rates.

FAQ

Q: Why is Zestimate null for most listings? Zillow only exposes Zestimate in search results for a fraction of listings (~5–15%). This is Zillow's deliberate data policy, not a parsing bug. Zestimate is always available on individual property pages.

Q: Can I scrape a specific neighborhood or zip code? Yes — enter the ZIP code (e.g. 90210) or a neighborhood name directly in the Location field. Zillow's URL slug resolver handles both.

Q: Will this break if Zillow updates their site? The actor uses Zillow's embedded __NEXT_DATA__ JSON (server-side rendered), not brittle CSS selectors. This approach is significantly more stable than HTML scraping and tolerates most layout changes.

Q: How many results can I scrape? Zillow typically returns up to ~500 pages × 41 listings ≈ 20,500 results per search query. Set maxItems to 0 for unlimited, or cap it to control cost.

Legal disclaimer

This actor is provided for legitimate data collection use cases such as market research, price analysis, academic study, and business intelligence. Users are responsible for complying with Zillow's Terms of Use, applicable laws, and any rate limits. The actor does not access authentication-gated or private/gated data. Zillow is a trademark of Zillow, Inc.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Dubai Property Scraper
• Onthemarket Properties Scraper
• Realtor Scraper
• Redfin Scraper
• Rightmove Listings
• Zoopla Properties Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.