Zillow Scraper: Every Listing Past 1,000, Zestimate, Details avatar

Zillow Scraper: Every Listing Past 1,000, Zestimate, Details

Pricing

from $0.50 / 1,000 listings

Go to Apify Store
Zillow Scraper: Every Listing Past 1,000, Zestimate, Details

Zillow Scraper: Every Listing Past 1,000, Zestimate, Details

Scrape every Zillow listing of a city, ZIP code, county or map area (for sale, for rent, sold), past the 1,000-per-search limit, with Zillow's announced count next to the returned count. Home pages by zpid or URL, new-listing and price-change watch.

Pricing

from $0.50 / 1,000 listings

Rating

0.0

(0)

Developer

Alexis Morain

Alexis Morain

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Zillow Scraper: scrape every Zillow listing of a city, ZIP code or map area

Zillow Scraper exports the listings that Zillow shows for a city, a ZIP code, a county, a neighborhood or a rectangle on the map: homes for sale, homes for rent and recently sold homes. One Zillow search serves 984 listings at most, however many it announces. This actor cuts the map into smaller cells until each one fits under that limit, reads them all, removes the duplicates on the borders and returns one row per listing, with the price, address, coordinates, beds, baths, living area, Zestimate, days on Zillow and brokerage.

It works as a Zillow API alternative for people who need rows, not a website: no login, no browser, plain HTTP. Results land in a dataset you can export as JSON, CSV, Excel or XML, or read through the Apify API from Python, JavaScript or cURL. Each run also writes a proof in its SUMMARY record: the count Zillow announced next to the count you received.

If you only need a handful of homes, give it zpids or home page URLs and it returns the full home page data of each one.

How to scrape more than 1,000 Zillow listings

Zillow's search pages stop at page 24 with 41 listings each, so 984 rows. Ask for Houston and Zillow says "15,361 results", then serves 984 of them. The table compares what Zillow announced with what this actor returned, for-sale listings, full coverage on, runs of 1 November 2026.

AreaZillow announcesOne Zillow searchThis actorRun timeRun
Austin, TX (map box)6,0299846,02949 sDzft0FXGd4FDJXkO3
Houston, TX15,36198415,3612 min 36 s3B6hnDvkHvKYINFw8
Denver, CO3,7729843,77260 s9BZBUGnwCLn45i7VY

With full coverage off, the actor returns Zillow's 984 and says so in the status message: "Zillow serves at most 984 listings per search; 2788 of the 3772 announced were not returned" (Denver again, run 0bOmQj2qCYXPqQ3Sz). The Austin run shows how much cleaning the borders need: 246 listings were served twice and returned once.

The SUMMARY record of the Denver run, trimmed to the fields that carry the proof:

{
"listingsReturned": 3772,
"inputs": [{
"input": "Denver, CO",
"announcedByZillow": 3772,
"uniqueListingsFound": 3772,
"announcedInLeafCells": 3772,
"servedInLeafCells": 3772,
"duplicatesSkipped": 123
}]
}

announcedInLeafCells is the sum of the counts Zillow gave for each map cell the actor read in full. servedInLeafCells is how many distinct listings those cells served. When the two match, nothing is missing. When they do not, the actor splits that cell again, and what is still short after that is reported as cellsStillOverLimit.

Why use a Zillow scraper

A market study of one metro area, a lead list of every listing in a ZIP code or a price model trained on a city needs the whole area, not the first 984 rows of a sort order.

  • Investors, analysts and researchers: every home of an area with price, size, Zestimate, days on Zillow and coordinates, for a spreadsheet, a notebook or a price model.
  • Agents, brokers and wholesalers: a daily feed of the listings that appeared since the last run, or whose price moved.
  • PropTech teams: complete, deduplicated rows for a database, or specific homes read by zpid.
  • Rental watchers: rentals by ZIP code, with apartment buildings kept as one row each.

What you get on top of a plain search export:

  • Full coverage past 984, with the announced count against the returned count in every run.
  • Duplicates removed before they are charged.
  • Optional home page data per listing: description, year built, price history when Zillow shows it, all photos, HOA fee, parking, agent and MLS details.
  • A watch mode that returns only new listings, or new listings plus price changes, with the previous price.
  • Residential US proxies included in the price, and Apify scheduling, API access and integrations (Make, Zapier, n8n, Google Sheets).

How to scrape Zillow listings, step by step

  1. Open the actor in Apify Console and go to the Input tab.
  2. In Places, type what you would type in Zillow's search box: Austin, TX, 78701, Travis County, TX or Hyde Park, Austin, TX. Each place is read separately.
  3. Pick For sale, For rent or Sold, and add filters if you want a subset.
  4. Set Max items. Use 100 for a first test. Empty means the whole area, tens of thousands of listings for a large city.
  5. Turn on Read each home page if you need the home page data. Leave Full coverage on to get more than 984 rows.
  6. Click Start. The status message ends with the announced count against the returned count.
  7. Download the dataset from the Output tab as JSON, CSV or Excel, or read it through the API.

Already have a search on zillow.com? Copy its URL into Zillow search URLs: when it carries searchQueryState (as soon as you moved the map or set a filter), the actor reads the region, the map and the filters from it.

Scrape Zillow by ZIP code, city, county, map area or zpid

You can mix inputs in the same run. Each one gets its own entry in the SUMMARY record and its own status.

Places (locations)

City and state, ZIP code, county or neighborhood, as Zillow's autocomplete knows it. The actor asks Zillow's autocomplete for the place, then reads the region outline from the search page, so a city search returns the city and not the rectangle around it. Austin by outline is 5,548 listings, while the same map box without the outline holds 9,760.

A place Zillow does not recognize ends as not-found, and the status message names it. Zillow answers garbage with a region (it sent "zzzzqqxx" to San Diego), so the actor only accepts a region that the autocomplete itself recognized.

Zillow search URLs (startUrls)

A search page copied from zillow.com. If it carries searchQueryState, the map, region and filters are used as they are, including the for sale, for rent or sold type. A plain page such as https://www.zillow.com/austin-tx/rentals/ gives its region and its rent or sold type, and filters you set in the input fields are added on top. Filters written inside the URL path, such as /3-_beds/, are not read: use the input fields for those.

Map area (area)

A rectangle with north, south, east and west, for an area that no place name covers, for example {"north": 30.50, "south": 30.15, "east": -97.55, "west": -97.95}. The whole rectangle is read, with no region outline.

Homes by zpid or URL (zpidsOrUrls)

A zpid (64625418) or a home page URL (https://www.zillow.com/homedetails/.../64625418_zpid/). Each one returns the full home page row and is charged as a detailed listing. This is the mode for pipelines that already hold a list of zpids, for example after an address match. A zpid that does not exist on Zillow is named in the status message.

Full coverage and home page details

Full coverage is on by default. The map is cut into four cells, then each cell that announces more than 800 listings is cut again, up to 12 levels deep. A cell that is already very small and still overflows, such as a dense block of condos, is split into price bands inside the price range you set. With Max items set, the actor reads the cells breadth first, so a limit of 300 spreads over the area instead of filling one corner.

Read each home page (includeDetails) opens the Zillow home page of each listing and adds the home page fields to its row. The row is charged as a detailed listing instead of a plain one, not on top of it. If a home page cannot be read, the row keeps the search fields, detailsStatus says failed, not-found or timeout, and it is charged as a plain listing. Apartment buildings have no home page and stay plain rows.

Scrape Zillow for sale, for rent and sold homes

For sale is the default. Set Listing type to For rent or Sold, or paste a search URL that already has the type.

  • For rent: price is the monthly rent, and minPrice and maxPrice apply to it. Zillow lists an apartment building as one card with several units. The actor returns it as one row with isBuilding true, no zpid, a buildingId, a unitCount and a units array (price starting at, and bedrooms, per unit type). The count Zillow announces for rentals counts units, so it is higher than the number of rows.
  • Sold: rows have homeStatus RECENTLY_SOLD and dateSold. In states that do not disclose the sale price (Texas is one), Zillow shows no price for sold homes, so price comes back null. The date is there, the price is not.

Filters

Each filter was checked against Zillow by comparing the total of the same map box with and without it.

FieldWhat it does
minPrice, maxPricePrice for sale and sold, monthly rent for rentals
minBeds, maxBedsBedrooms. Set both to 0 for studios only
minBathsBathrooms, halves count as .5
homeTypeshouse, townhouse, condo, apartment, multiFamily, lot, manufactured
daysOnZillow1, 7, 14, 30, 90, 6m, 12m, 24m or 36m. For sold homes it is the sale window

For rent, Zillow serves houses, townhouses and apartments or condos, and treats condo and apartment as linked. The actor stops with a clear message if you ask for lots, manufactured homes or multi-family in rent, because Zillow does not apply them to rentals and returns everything for multi-family. Sorting by price is not offered: it did not hold up when checked.

What data does the Zillow scraper extract?

A search row carries the identity, address, price, size, Zestimate, status, brokerage, photos and coordinates. With home pages on, or when you read homes by zpid, the row also gets the home page fields. Fields that Zillow does not show for a given home come back as null, so every row has the same keys. The full list, from the dataset schema:

FieldTypeDescription
zpidnumberZillow property ID. Null for apartment buildings (see buildingId)
urlstringListing page on Zillow
listingTypestringforSale, forRent or sold, as searched
homeStatusstringZillow status: FOR_SALE, FOR_RENT, RECENTLY_SOLD, PENDING...
statusTextstringStatus as shown on the card. Empty when a home is read by zpid or URL (no search card)
homeTypestringSINGLE_FAMILY, CONDO, TOWNHOUSE, MULTI_FAMILY, APARTMENT, LOT, APARTMENT_BUILDING...
pricenumberList price, or monthly rent for rentals. Null for sold homes in states that hide the sale price (Texas) and for buildings
currencystringCurrency code
streetAddressstringStreet address
citystringCity
statestringState code
zipcodestringZIP code
latitudenumberLatitude
longitudenumberLongitude
bedsnumberBedrooms
bathsnumberBathrooms (halves count as .5)
livingAreanumberLiving area in square feet
lotAreaValuenumberLot size, in lotAreaUnit
lotAreaUnitstringacres or sqft
zestimatenumberZillow's estimated market value, when Zillow shows one
rentZestimatenumberZillow's estimated monthly rent, when shown
taxAssessedValuenumberTax-assessed value
daysOnZillownumberDays since the listing appeared on Zillow
dateSoldstringSale date (YYYY-MM-DD) for sold homes
brokerNamestringListing brokerage
imgSrcstringMain photo
photosarrayPhoto URLs (all photos of the listing page with home pages on, else the search carousel)
isBuildingbooleanTrue for an apartment building row (rentals): no zpid, one row per building
buildingIdstringBuilding ID, only for building rows
unitCountnumberAvailable units of a building
unitsarrayUnit types of a building: price (monthly, starting at) and beds
has3DModelbooleanZillow 3D tour available
hasVideobooleanVideo available
searchInputstringWhat you entered: the place, search URL, area or home this row comes from
scrapedAtstringISO timestamp of the read
previousPricenumberMonitoring: price returned by the previous run for this listing, null for a new listing
priceChangestringMonitoring: new, up or down
detailsStatusstringWith home pages on: ok, failed, not-found or timeout. A failed read is charged as a plain listing
descriptionstringListing description (home page)
yearBuiltnumberYear built (home page)
priceHistoryarrayPrice and status events: date, price, event, source (home page). Null when Zillow serves the page template without history (see priceHistoryAvailable), which depends on the home, not on the run
priceHistoryAvailablebooleanHome page read: true when Zillow served a price history (it may be an empty list), false when its page template carries none
monthlyHoaFeenumberMonthly HOA fee (home page)
parkingarrayParking features (home page)
parkingSpacesnumberParking capacity (home page)
coolingarrayCooling systems (home page). Filled on rentals, usually null on sale pages
pricePerSquareFootnumberPrice per square foot (home page)
agentNamestringListing agent (home page, when the listing shows one)
agentPhonestringListing contact phone, the listing agent's line (home page, when shown)
brokerPhonestringBrokerage phone (home page, only when Zillow gives one apart from the agent line)
mlsIdstringMLS number (home page)
mlsNamestringMLS name (home page)
datePostedstringDate the listing was posted (YYYY-MM-DD, home page, when shown)
pageViewCountnumberZillow page views (home page, when shown)
favoriteCountnumberZillow saves (home page, when shown)

A few columns are empty by nature. priceHistory depends on the page template Zillow serves for that home (see the limits), price is empty for sold homes in states that do not disclose the sale price, and statusText is empty when you read a home by zpid, because a home page has no search card.

A real row from a search run on ZIP code 78701, 1 November 2026, with the photo list shortened to one URL:

{
"zpid": 339448049,
"url": "https://www.zillow.com/homedetails/44-East-Ave-UNIT-1208-Austin-TX-78701/339448049_zpid/",
"listingType": "forSale",
"homeStatus": "FOR_SALE",
"statusText": "Active",
"homeType": "CONDO",
"price": 231288,
"currency": "USD",
"streetAddress": "44 East Ave Unit 1208",
"city": "Austin",
"state": "TX",
"zipcode": "78701",
"latitude": 30.255808,
"longitude": -97.739,
"beds": 2,
"baths": 2,
"livingArea": 793,
"zestimate": null,
"taxAssessedValue": 221850,
"daysOnZillow": 68,
"brokerName": "HomeBase",
"photos": ["https://photos.zillowstatic.com/fp/dfff9bba8c9fbd2d2d5247215e45d7b4-p_e.jpg"],
"isBuilding": false,
"searchInput": "78701",
"scrapedAt": "2026-11-01T05:13:20+00:00"
}

Example row with home page details

A real row with Read each home page on (run a88mqWJ0Wh5adCUxf), some search fields left out and the description and price history shortened. This home has a price history, and priceHistoryAvailable says so:

{
"zpid": 89552472,
"streetAddress": "360 Nueces St APT 1301",
"price": 395000,
"livingArea": 801,
"description": "13th-floor end unit with panoramic Downtown Austin views and Lady Bird Lake. ...",
"yearBuilt": 2008,
"priceHistory": [
{"date": "2026-10-16", "price": 395000, "event": null, "source": null},
{"date": "2026-09-16", "price": 429000, "event": null, "source": null}
],
"priceHistoryAvailable": true,
"monthlyHoaFee": 704,
"parking": ["Assigned", "Covered", "Reserved"],
"pricePerSquareFoot": 493,
"mlsId": "3418824",
"detailsStatus": "ok"
}

Zillow price drop tracker: monitor new listings and price changes

Set Monitoring to get a feed instead of a full export.

  • New listings only returns the listings that no earlier run with the same input returned.
  • New listings and price changes also returns listings whose price moved, with previousPrice and priceChange (up or down). Listings new to the watch get priceChange new.

The first run returns everything. After that, unchanged listings are not pushed and not charged. Zillow's search order is not by date, so a watch always reads the whole area and compares it with its memory.

The memory lives in a named key-value store in your account called zillow-scraper-monitor, one record per search input and per watch. Runs that share the same input and the same Monitor name share one memory; change the name to start a second, separate watch on the same search. A listing joins the memory only after it was delivered, so one cut by Max items or by the maximum charge comes back in the next run. Entries older than 180 days are forgotten.

A test on ZIP code 78701, 1 November 2026: the first run returned 198 listings, the second returned 19 new listings, 1 price increase and 1 price drop, and left out 196 unchanged (runs TVhhVdLgtgguavT13 and I0bYCWGym0ha6Sryk).

To schedule it, open Schedules in Apify Console, pick the actor, paste the input and set a cron expression. A daily run at 7:00 with Monitoring on gives you what changed since yesterday.

Webhook. Set Webhook URL to get a POST at the end of the run, only when it returned at least one row. The JSON body carries actor, runId, datasetId, monitorMode, items, byEvent, inputs, plus a one-line message in text (Slack) and content (Discord). A webhook that fails is logged and does not fail the run.

How much does it cost to scrape Zillow?

The actor uses Apify's pay-per-event pricing. You pay for events, and the residential proxy that Zillow requires is included.

EventCharged whenFreeBronzeSilverGold, Platinum, Diamond
ListingA unique listing is returned from a search$1.00 per 1,000$0.87$0.73$0.50
Detailed listingA listing is returned with its home page data, or a home is read by zpid or URL. Charged instead of Listing$2.50 per 1,000$2.20$1.85$1.60
Actor startThe run starts, per GB of memory (256 MB by default)$0.002$0.002$0.002$0.002

The plan tier is the one of your Apify subscription. A listing found twice in a run is charged once. A listing skipped by the watch because it was already returned is not charged. A home page that could not be read is charged as a plain listing.

Example: a search that returns 10,000 listings, 1,000 of them with their home page (9,000 Listing events and 1,000 Detailed listing events).

That costs $11.50 on Free (9,000 x $0.00100 + 1,000 x $0.00250), $10.03 on Bronze, $8.42 on Silver and $6.10 on Gold, start event not included.

Other examples at the Free rate: Houston, all 15,361 for sale listings, about $15.36; a daily watch that sees 20 new listings a day, about $0.022 a run. To keep a test cheap, set Max items or the maximum charge per run in the run options: at the maximum charge the actor stops and keeps the rows it already read.

Scrape Zillow with Python, JavaScript or cURL

These examples use the actor alexmorain/zillow-scraper. Replace the token with your own and keep it in an environment variable.

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("alexmorain/zillow-scraper").call(run_input={
"locations": ["Austin, TX", "78701"],
"listingType": "forSale",
"minPrice": 300000,
"maxPrice": 900000,
"minBeds": 2,
"homeTypes": ["house", "condo"],
"daysOnZillow": "30",
"maxItems": 2000,
})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
print(row["streetAddress"], row["price"], row["zestimate"])
summary = client.key_value_store(run["defaultKeyValueStoreId"]).get_record("SUMMARY")["value"]
for entry in summary["inputs"]:
print(entry["input"], entry["announcedByZillow"], entry["uniqueListingsFound"])

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('alexmorain/zillow-scraper').call({
locations: ['Denver, CO'],
listingType: 'forRent',
minPrice: 1500,
maxPrice: 2500,
maxItems: 500,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, 'rows,', items.filter((r) => r.isBuilding).length, 'buildings');

cURL

Start a run and wait for the rows in one call:

curl -X POST \
"https://api.apify.com/v2/acts/alexmorain~zillow-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"zpidsOrUrls": ["64625418", "https://www.zillow.com/homedetails/x/89552472_zpid/"]}'

A synchronous call times out after five minutes: use it for short runs. For a whole city, start the run with POST /v2/acts/alexmorain~zillow-scraper/runs and read the dataset when it ends.

Limits of this Zillow scraper, written plainly

  • United States only. A place outside the US ends as not found.
  • Price history is missing on part of the home pages. Zillow serves two templates for a home page. One carries the price history, the other does not, and the home decides which one you get, not the run or the IP. In a sample of 10 homes in ZIP code 78701, 2 had a history and 8 did not (run a88mqWJ0Wh5adCUxf); a check of 10 other homes found 4 with history (6, 5, 15 and 17 events) and 6 without (run uMsfDvfAc29RlBkZe). The history of the other template sits behind a call that only Zillow's own pages may make, so the actor cannot get it. priceHistoryAvailable tells you which rows have one.
  • Sold homes have no price in states that do not disclose it, such as Texas. The row keeps dateSold and the rest.
  • For rent, the announced count is a count of units. In ZIP code 78701, with rent from $1,500 to $2,500, Zillow announced 78 units and the actor returned 24 rows, 13 of them buildings (run y1EWkS1ILc0oiuY2q). The returned count is lower than the announced count by design, and buildingRows in the SUMMARY tells you how many rows are buildings.
  • Not extracted: tax history, nearby schools, Zestimate history, mortgage data, agent directories. The home page request this actor reads does not return them, so there is no column for them.
  • Zillow can refuse requests. The actor changes IP after a refusal and every 40 requests, and retries. If Zillow refuses everywhere, the run ends FAILED with a message instead of returning a half empty dataset. A single input that fails does not stop the others.

Zillow scraper FAQ

How to scrape more than 1,000 listings from Zillow?

A Zillow search serves 984 listings at most (24 pages of 41), whatever the announced total. To get more, the map has to be split into smaller searches, each under the limit, and the results merged without duplicates. That is what full coverage does. Houston announced 15,361 listings and the actor returned 15,361 (run 3B6hnDvkHvKYINFw8).

Can I scrape Zillow by ZIP code?

Yes. Type the ZIP code in Places, for example 78701. ZIP codes are read with Zillow's region outline, so you get that ZIP code and not the neighbors. ZIP code 78701 for sale had 217 listings on 1 November 2026 and the actor returned 217 in 25 seconds (run eSYdwPLeOzztzX5Ef). You can pass many ZIP codes in the same run.

Do I get the Zillow price history of every home?

No, and the reason is on Zillow's side. With home pages on, the actor returns priceHistory (date, price, event and source for each event) for the homes whose page carries it. Zillow serves a second page template without a price history for part of the homes. priceHistoryAvailable tells you, for every row, whether Zillow gave one.

How do I track Zillow price changes?

Set Monitoring to New listings and price changes, schedule the run, and read priceChange and previousPrice on each row. See the monitoring section above.

This is not legal advice. The data this actor reads is what Zillow shows to any visitor of its public pages: no login, no private account data. Whether collecting it is allowed depends on what you do with it, where you are and Zillow's terms of use, which limit automated access and the reuse of its content. Read them before building a product on the data. The listing data also contains personal data: the name and phone number of listing agents. In the European Union the GDPR applies to it, and in the US state privacy laws and rules about unsolicited calls and texts may apply. Do not use agent contacts for mass cold calling or messaging, keep only what you need, and ask a lawyer if the use is commercial and at scale.

How does this compare to an official Zillow API?

This actor does not use an official Zillow API. It reads the public site and gives you the rows a visitor would see, in a dataset or through the Apify API. It is a scraper, so it depends on the site's structure and on Zillow's protections, and you should expect to rerun or adjust if Zillow changes them.

Disclaimers and support

Our actors do not extract private user data such as email addresses or the location of users. They only extract what Zillow shows publicly. Your results can still contain personal data, such as the name and phone number of a listing agent. Personal data is protected by the GDPR in the European Union and by other regulations around the world. Do not scrape personal data unless you have a legitimate reason, and if you are unsure whether yours is legitimate, consult a lawyer. This actor is not affiliated with or endorsed by Zillow.

Something wrong or missing? Use the Issues tab of this actor. Send the run id and the input. The API tab has the endpoints and ready-made code to start the actor from your own tools.

Guide and use cases

Use cases for outbound and automation, the output fields, pricing and common questions are on the Zillow Scraper page of my site. The Classifieds and real estate family page puts it side by side with the other scrapers of the same family.