Zillow ZIP Code Scraper | $0.50/1K | Bulk Search

Zillow ZIP Code Scraper

Search Zillow properties across multiple US ZIP codes with a separate quota for each ZIP. Export homes for sale, rental listings or recently sold homes as a flat CSV or JSON dataset.

Result pricing: $0.50/1,000 property rows on paid Apify plans; $1.00/1,000 on Free. Automatic source access recovery is included. No Zillow login or additional service is required.

What you can collect

• Build a property export for a list of ZIP codes without configuring each search separately.
• Control both the total batch size and the number of unique properties collected for each ZIP.
• Keep ZIP codes such as 02108 intact by entering them as five-character strings.
• Inspect coverage for each ZIP and continue unfinished work without saving the same property twice along the same continuation chain.

How to use Zillow ZIP Code Scraper

1. Enter your five-digit ZIP codes and set a per-ZIP quota.
2. Set Maximum results this run and optional filters.
3. Set a spending limit in Apify run options, then click Start.
4. Open the results, review the coverage summary, and download CSV, Excel or JSON.

Quick-start input

{
  "zipCodes": [
    "78704",
    "78745"
  ],
  "maxResultsPerZip": 20,
  "maxResults": 40
}

This example is a starting point; replace its sources with your own. ZIP codes must remain five-character strings.

Input options

Input	Purpose	Default
zipCodes	Required: up to 100 five-digit US ZIP strings, e.g. ["78704", "02108"].	Your ZIP list
listingType	sale, rent or sold.	sale
maxResultsPerZip	Unique rows per ZIP across this collection and all continuation batches.	100
maxResults	Maximum new rows saved in this run.	100
Price and size filters	USD price; monthly USD for rent; bedrooms, bathrooms and living area in square feet.	Unset
resumeFromRunId	Continue the latest finished batch with the same query.	Unset
advanced	Optional request, time, download and retry ceilings.	300 requests, 600 seconds, 50 MB on paid plans

Manually supplied source lists accept up to 100 entries. You may combine supported input methods; earlier sources can consume the shared result limit before later ones are reached.

Output: CSV and JSON fields

Each result is one property record. Missing source fields are null. The default table uses readable column labels while exports keep stable field names.

Data	Columns
Property	recordId, zpid, url, status
Search attribution	searchedZipcode identifies the ZIP search that first saved the property.
Location	address, city, state, zipcode, latitude, longitude
Price and size	price, bedrooms, bathrooms, livingArea

Nested attributes, where present, are serialized as JSON strings so CSV remains flat. Errors are not mixed into paid dataset rows. Coverage and limits (RUN_SUMMARY), Source issues (ERRORS) and Continue collection (PAGINATION) are separate run output links. REQUEST_METRICS and CHECKPOINT are available in key-value storage.

Pagination and bounded map splitting handle larger ZIP searches. A reached per-ZIP quota is intentionally limited coverage, not a full ZIP export.

💳 Pricing and spending limits

Apify account	Price per 1,000 property rows	Collection allowance
Paid plan	$0.50	Requested count, source availability and run limits
Free	$1.00	100 rows across one collection and its continuation chain

Only saved result rows are charged as results. Failed requests and diagnostic records are kept separately.

The platform actor-start event is $0.00005 per GB of allocated memory, with a minimum of one event. A 256 MB run therefore pays $0.00005 to start. Each new continuation run and each Resurrect may incur another start event. There are no separate enrichment or access-recovery add-ons. Platform usage is included in the PPE policy; no extra dataset-item event is configured.

Apify authenticates the account plan automatically; input cannot select the cheaper rate. Free is an Apify account plan, not zero-price output: results consume available account credits. Free runs also stop at 40 requests, 180 seconds or 10 MB of compressed downloaded responses. These ceilings cannot be raised in the input. Downloads are checked between responses, so one response can exceed the remaining traffic allowance. Independent fresh collections have independent allowances; this is not an account-wide monthly quota.

Minimum permitted Max total charge: $0.00105, covering the start event and at least one result at the highest Free rate. This is a minimum budget setting, not a minimum bill: only the start and saved result events are charged. The same result rates apply to all paid Apify plans.

Set Max total charge in Apify run options, or maxTotalChargeUsd through the API. The requested result count is not a dollar budget. The SDK checks remaining run budget before saving charged rows, and Apify can stop a run when its budget is reached. Paid-account credit balance and overage settings are separate from this run limit. Rates are configured for the current private release; the actor has not been published in Apify Store.

🔁 Continue after a limit or source error

1. Keep the saved dataset and wait until the previous run has finished.
2. Open Continue collection (PAGINATION) in the run output.
3. If hasMore=true, copy the full nextInput into a new run of this same actor. It includes resumeFromRunId.
4. Keep the query, filters and any monitor baseline unchanged. You may change maxResults and advanced collection limits; ZIP per-code quotas stay unchanged.
5. Set a new spending budget. Download this batch’s dataset and combine it with your earlier batches.

The next batch contains newly saved rows only. Earlier rows are skipped and are not charged again along that continuation chain. Use the latest finished batch: branching twice from an older run can create overlapping datasets. The previous run must belong to your own account and this actor, and its storage must remain available.

Stop or issue	Next step
Result, request, time or download ceiling	Use PAGINATION.nextInput if hasMore=true; adjust the next batch’s limits.
Temporary restriction or HTTP 403	Bounded automatic recovery has already been attempted. Retain progress and try the continuation later. A fresh run does not guarantee that access is restored.
Spending limit	Keep saved rows and resume with a new per-run budget. The budget is not shared across the chain.
Free collection allowance	Continuation and Resurrect do not replenish it. Upgrade the account before collecting beyond the Free allowance.
Invalid input or changed query	Correct the input; keep the original query for continuation or start a separate collection.
Missing checkpoint after a hard stop	A usable continuation may be unavailable. Keep any saved rows; a fresh collection cannot guarantee deduplication against that dataset.

Apify Resurrect restarts the same run and storage. resumeFromRunId creates a separate batch and dataset. Do not use both methods simultaneously. A requested count is a ceiling, not a promise that Zillow has that many accessible records.

Run through the Apify API

The same JSON input works in Apify Console and through the Apify Actor API. Start a run, wait for it to finish, then export its dataset as JSON, CSV or Excel. Use the actor ID from its Console page and your own Apify API token; no Zillow API key is required. Pass maxTotalChargeUsd as a run option rather than an input field. Never put API tokens in the input.

Choose the right Zillow actor

Choose this actor for a list of ZIP territories with independent quotas and coverage. Use Zillow Scraper for a general city/search-URL workflow, Zillow Rental Scraper for available apartment units, or Zillow Property Details Scraper when you already have property URLs or ZPIDs.

Frequently asked questions

How is this different from a city search?

The ZIP scraper tracks a separate quota and coverage status for each ZIP. Use a general Zillow search scraper for a single city or a filtered Zillow search URL.

Does the ZIP quota mean all homes were collected?

No. A quota is a collection limit. Zillow pagination, source restrictions and runtime limits can leave a ZIP partially collected. Check RUN_SUMMARY.targets and zipCounts.

What happens if searches overlap?

Properties are deduplicated across the collection. searchedZipcode is the first search that emitted the property; the property’s own address ZIP is zipcode. Overlap can prevent a later ZIP from filling its quota.

Is this an official Zillow API?

No. This is an independent actor callable through the Apify API. It is not affiliated with, sponsored or endorsed by Zillow. Source fields, layouts and access can change; complete extraction and uninterrupted access are not guaranteed.