Zillow Search Scraper: Homes for Sale, Rent and Sold
Pricing
from $1.05 / 1,000 results
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.
Pricing
from $1.05 / 1,000 results
Rating
0.0
(0)
Developer
vøiddo
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 hours ago
Last modified
Categories
Share
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:
{"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:
{"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.