Zillow Scraper: Listings, Agents, Zestimate & Filters
Pricing
$3.00 / 1,000 zillow listings
Zillow Scraper: Listings, Agents, Zestimate & Filters
Scrape Zillow for-sale, sold, and rental listings by city, ZIP, URL, ZPID, or dataset. Get prices, Zestimate, agent contacts, photos, property details, and history. Use fast search, full-detail enrichment, advanced filters, and listing change monitoring.
Pricing
$3.00 / 1,000 zillow listings
Rating
5.0
(2)
Developer
Kelopr
Maintained by CommunityActor stats
3
Bookmarked
134
Total users
23
Monthly active users
0.83 hours
Issues response
10 hours ago
Last modified
Categories
Share
Search, enrich, or monitor Zillow listings with pricing, Zestimate, agents, photos, history, and property filters.
Search, fully enrich, directly scrape, or monitor Zillow listings. Extract prices, Zestimate, agents, photos and property history with global filters for price, beds, area, HOA, days on Zillow, open houses and price cuts.
All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.
π What this Actor does
- Flexible collection:
SEARCH,SEARCH_DETAILS,DETAIL,MONITOR. - Structured output: clean JSON records organized into
overviewviews. - Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
- Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.
ποΈ Modes and workflows
| Mode or workflow | What it does |
|---|---|
SEARCH | Search listing cards with price, property, location, recency, and status filters. |
SEARCH_DETAILS | Search and enrich every selected listing with detail data. |
DETAIL | Resolve exact property URLs or ZPIDs. |
MONITOR | Compare a named snapshot and emit listing changes. |
π‘ Common use cases
- Property comps and inventory research
- Price, status, and listing-history monitoring
- Agent and market intelligence
π₯ Input schema
Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.
| Field | Type | Description | Default |
|---|---|---|---|
mode | string | Choose Search for quick listing cards, Search + details for complete property records, Detail for known properties, or Monitor to detect listing changes. Allowed: SEARCH, SEARCH_DETAILS, DETAIL, MONITOR. | SEARCH |
propertyStatus | string | Choose the Zillow market you want to search. In Detail mode this is only recorded as the expected status; a successfully fetched property is never discarded because of it. Allowed: ANY, FOR_SALE, SOLD, FOR_RENT. | FOR_SALE |
searchQueries | array | Used by Search, Search + details, and Monitor. Add a city, ZIP code, neighborhood, Zillow region slug, or full Zillow search URL. Each row starts a separate search. | ["Sonoma, CA"] |
startUrls | array | Used only in Detail mode. Add one or more Zillow property pages. You can combine URLs with ZPIDs and an input dataset below. | β |
zpids | array | Optional raw Zillow property IDs, for example 15800416. Each ID is resolved to its property page automatically. | [] |
datasetId | string | Optional dataset produced by a previous Search run. Items should contain zpid, detailUrl, hdpUrl, or url. | β |
maxPagesPerSearch | integer | Maximum Zillow result pages collected for each location or search URL. | 1 |
maxResults | integer | Global limit after duplicate removal, filtering, and sorting. This is the maximum number of paid rows saved to Results. | 50 |
maxDetailUrls | integer | Detail: caps properties from all direct inputs. Search + details: caps complete property records after Maximum saved results. Use 0 for no additional cap. | 0 |
propertyType | string | Keep only one Zillow property category, or leave Any selected. Allowed: ANY, HOUSE, CONDO, TOWNHOUSE, MULTI_FAMILY, MANUFACTURED, LOT_LAND, APARTMENT. | ANY |
minPrice | number | Keep properties priced at or above this amount. | β |
maxPrice | number | Keep properties priced at or below this amount. | β |
minBedrooms | number | Minimum number of bedrooms. | β |
maxBedrooms | number | Maximum number of bedrooms. | β |
minBathrooms | number | Minimum number of bathrooms. Decimal values such as 1.5 are supported. | β |
maxBathrooms | number | Maximum number of bathrooms. | β |
minLivingArea | number | Minimum interior living area in square feet. | β |
maxLivingArea | number | Maximum interior living area in square feet. | β |
minLotSize | number | Minimum lot size in square feet. | β |
maxLotSize | number | Maximum lot size in square feet. | β |
minYearBuilt | integer | Oldest construction year to keep. Missing years are enriched from property details when this filter is active. | β |
maxYearBuilt | integer | Newest construction year to keep. | β |
hoaStatus | string | Include every property, only properties with a positive monthly HOA fee, or properties with no reported HOA fee. Allowed: ANY, WITH_HOA, NO_HOA. | ANY |
minHoaFee | number | Minimum reported monthly HOA fee. Properties with missing HOA values are excluded while this range is active. | β |
maxHoaFee | number | Maximum reported monthly HOA fee. | β |
minDaysOnZillow | integer | Keep listings visible on Zillow for at least this many days. | β |
maxDaysOnZillow | integer | Keep listings visible on Zillow for no more than this many days. | β |
onlyWithPhotos | boolean | Exclude properties without a listing image or photo collection. | false |
onlyOpenHouses | boolean | Keep only listings currently advertising an open house. | false |
onlyPriceReductions | boolean | Keep only listings with a detected price cut. | false |
sortBy | string | Results are deduplicated and filtered first, then the entire result set is sorted before the maximum result limit is applied. Allowed: RELEVANCE, PRICE_ASC, PRICE_DESC, BEDROOMS_DESC, BATHROOMS_DESC, LIVING_AREA_DESC, LOT_SIZE_DESC, YEAR_BUILT_DESC, NEWEST, PRICE_REDUCTION_DESC. | RELEVANCE |
monitorKey | string | A stable name for this monitor, for example austin-family-homes. Leave empty to derive it automatically from the search and filters. | `` |
resetMonitor | boolean | Start a fresh baseline for this monitor. This run stores the current properties and returns no change rows. | false |
maxConcurrency | integer | Number of requests processed at the same time. The default balances speed and reliability. | 5 |
maxRetries | integer | Retry budget for temporary source errors and incomplete responses. | 5 |
maxProxyRetries | integer | Separate retry budget for temporary connection failures. | 5 |
maxCaptchaRetries | integer | Separate retry budget when Zillow temporarily interrupts access. | 5 |
proxy | object | US residential access is preconfigured and recommended because Zillow data is region-sensitive. The default is ready to use. | {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "US"} |
rawOutput | boolean | Add the original gdpClientCache payload under _raw in Detail and Search + details outputs. Most users should leave this disabled. | false |
βΆοΈ Example input
{"mode": "SEARCH_DETAILS","propertyStatus": "FOR_SALE","searchQueries": ["Austin, TX"],"maxResults": 50,"minBedrooms": 2,"maxPrice": 750000,"onlyWithPhotos": true}
π¦ Output schema
Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.
overview β Results
A compact table for fast scanning and export.
Fields: zpid, imgSrc, displayAddress, streetAddress, city, state, zipcode, homeStatus, statusType, homeType, price, unformattedPrice, currency, bedrooms, beds, bathrooms, baths, livingArea, area, yearBuilt, detailUrl, hdpUrl
π€ Example output
{"zpid": "DEMO-ZPID-01","displayAddress": "100 Example Street, Austin, TX 78701","city": "Austin","state": "TX","zipcode": "78701","homeStatus": "FOR_SALE","homeType": "SINGLE_FAMILY","price": 625000,"currency": "USD","bedrooms": 3,"bathrooms": 2,"livingArea": 1680}
Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.
π API example
Replace the placeholder with an Apify token and send the same input used in the Console:
curl -X POST "https://api.apify.com/v2/acts/trakk~zillow-scraper/runs?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"mode": "SEARCH_DETAILS", "propertyStatus": "FOR_SALE", "searchQueries": ["Austin, TX"], "maxResults": 50, "minBedrooms": 2, "maxPrice": 750000, "onlyWithPhotos": true}'
For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.
π§© Automation and exports
- Schedule recurring runs from the Apify Console.
- Trigger downstream systems with webhooks when a run succeeds or fails.
- Reuse named monitoring keys or stores where the selected workflow supports change tracking.
- Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.
β FAQ
Do I need a login or browser session?
Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.
Why can some fields be empty?
Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.
How should I run this at scale?
Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.
Is the example data real?
No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.