Zillow Real Estate Scraper

Pull Zillow listings into a clean dataset. Give it a city or ZIP code and get every matching property with price, beds, baths, square footage, home type, days on market, GPS coordinates and the Zestimate — for homes for sale, rentals, and recently sold properties.

No browser, no rendering, no waiting: it reads Zillow's own structured search data directly, which is why a 240-listing run finishes in about 25 seconds.

What you get

Every property becomes one row:

Field	Description
zpid	Zillow's property ID — a stable key for joins and de-duplication
url	Link to the Zillow listing
address	Full address, plus street, city, state, zipcode separately
price	Numeric price (monthly rent for rentals), with priceText and currency
beds, baths	Bedroom and bathroom counts
livingArea	Interior square footage
lotArea, lotAreaUnit	Lot size and its unit
homeType	SINGLE_FAMILY, CONDO, TOWNHOUSE, APARTMENT, LOT, …
homeStatus	FOR_SALE, FOR_RENT, RECENTLY_SOLD, …
statusText	Zillow's own label, e.g. "Active", "Coming soon"
daysOnZillow	How long the listing has been up
latitude, longitude	GPS coordinates
zestimate, rentZestimate	Zillow's estimated value and rent, when published
taxAssessedValue	Assessed value for tax purposes
priceChange, datePriceChanged	Size and date of the most recent price change
brokerName	Listing broker
imageUrl	Main listing photo
listingType, searchLocation, page, scrapedAt	What produced the row, and when

Example

{
  "zpid": "29329029",
  "url": "https://www.zillow.com/homedetails/1406-W-13th-St-Austin-TX-78703/29329029_zpid/",
  "address": "1406 W 13th St, Austin, TX 78703",
  "city": "Austin",
  "state": "TX",
  "zipcode": "78703",
  "price": 1299000,
  "beds": 3,
  "baths": 2,
  "livingArea": 1578,
  "homeType": "SINGLE_FAMILY",
  "homeStatus": "FOR_SALE",
  "daysOnZillow": 3,
  "latitude": 30.280336,
  "longitude": -97.75638
}

Input

Option	Description
Locations	US cities, neighborhoods or ZIP codes: Austin, TX, Brooklyn, NY, 90210. Required.
Listing type	For sale, for rent, or recently sold.
Max results per location	Up to 820 per location (see the limit note below).
Minimum / maximum price	Filter by price, or by monthly rent for rentals.
Minimum bedrooms	Skip anything smaller.
Max items	Hard cap across the whole run.
Proxy configuration	Residential proxy, required and on by default.

Use it for

• Market analysis — median price per ZIP, price-per-square-foot trends, inventory counts
• Investment screening — filter by price, beds and rentZestimate to find rental yield
• Comparable sales — pull recently sold properties near a target address
• Rental pricing — see what comparable units actually ask in a neighborhood
• Lead generation — listings with a long daysOnZillow and a recent priceChange

Honest notes

• Zillow caps every search at 20 pages — 820 listings — no matter how many results it reports. A city with 5,000 listings will only ever return the first 820 for a single search. To get full coverage, search by ZIP code instead of by city; the Actor reports Zillow's total count in the log so you can see what you're missing.
• Zestimates aren't published for every property. Roughly a quarter of for-sale listings carry one; zestimate is null for the rest. That's Zillow's data, not a scraping gap.
• Residential proxy is required. Zillow blocks datacenter IPs outright and rate-limits hard by address. The Actor gives each request a fresh proxy session and retries refusals automatically, but changing the proxy setting away from residential will cause runs to fail.
• Price filters are applied to what Zillow returns, so a filtered run reads the same number of pages as an unfiltered one. Narrow filters mean fewer results, not a cheaper run — the log shows how many were filtered out.

Pricing

Pay per listing actually extracted. Blocked or failed pages cost you nothing, and there is no charge per page or per hour — a run that returns 500 listings costs the same whether Zillow served them in one page or twenty.