Zillow Listings Scraper (For Sale, Rent, Sold)

Homes for sale, for rent or recently sold on Zillow, for any US city or ZIP code. For each home: price, full address, beds, baths, living area, lot size, home type, days on Zillow, tax assessed value, Zestimate where Zillow shows one, sold date, coordinates and the listing URL — and, for rental buildings, the starting price of every unit type.

Reads Zillow's public city and ZIP pages. No login, no browser.

What it is for

• Market monitoring — new listings and price levels by city or ZIP.
• Rental research — rents by bedroom count, including apartment complexes.
• Comps — recently sold homes with dates (and prices where the state publishes them — see 3).

Input

field	what it does
locations	austin-tx, san-diego-ca, austin-tx-78701 (or "Austin, TX").
listingType	for_sale, for_rent, sold.
homeType	any, houses, condos, townhomes.
maxItems	Homes per location (default 82; 41 per page).

Four things worth knowing before you trust the data

1. Zillow stops after about 20 pages, whatever the total says

Austin shows 5,757 homes for sale, but Zillow serves only ~20–21 pages of 41 before answering with an error. Split big cities by ZIP code to reach more. The summary reports Zillow's total next to what was returned.

2. Rentals are mostly whole buildings

40 of the first 41 Austin rentals were apartment complexes with no single price — just "from" prices per unit type ("1 bed from $1,320"). Each such row gets unitPrices (per bedroom count) and priceFrom (the lowest), so you don't get a column of empty prices.

3. Sold prices are missing in non-disclosure states

Recently sold homes in Austin, TX came with no sale price at all (0 of 41), while San Diego, CA came with prices on every row. Texas and about ten other states do not make sale prices public record, so Zillow can't show them. When a sold search returns no prices, the summary says so in plain words (priceNote) — the dates and home details are still there.

4. Filters are checked against the rows

Home type and listing type are part of the page address on Zillow; the Actor checks the first page's homes actually match what you asked for and returns nothing (with an explanation) if they don't.

Proxy

US residential is required and is the default. Zillow refused every Apify server and datacenter address measured, and served US residential addresses — but only for some browser fingerprints, so the Actor uses the two that passed. Pages are about 0.6 MB; residential transfer is billed on the compressed size.

Output

{
  "recordType": "LISTING",
  "zpid": "185179147",
  "statusType": "FOR_SALE",
  "priceValue": 524900,
  "addressStreet": "12500 Turkey Ridge Ct",
  "addressCity": "Austin",
  "addressZipcode": "78729",
  "beds": 4,
  "baths": 2,
  "livingArea": 2314,
  "lotArea": 0.2717,
  "lotAreaUnit": "acres",
  "homeType": "SINGLE_FAMILY",
  "daysOnZillow": 9,
  "taxAssessedValue": 490354,
  "detailUrl": "https://www.zillow.com/homedetails/12500-Turkey-Ridge-Ct-Austin-TX-78729/185179147_zpid/"
}

Every row also carries Zillow's full listing object.

Limits

• Zillow's filter panel (price, beds, etc.) is not used — its robots.txt disallows the filter parameter. City, ZIP, listing type and home type are the permitted filters; filter the output for the rest.
• Home detail pages are not fetched.