Zillow Rental Scraper | $0.60/1K | Apartments & Units avatar

Zillow Rental Scraper | $0.60/1K | Apartments & Units

Pricing

from $0.60 / 1,000 paid plans: saved rental property or units

Go to Apify Store
Zillow Rental Scraper | $0.60/1K | Apartments & Units

Zillow Rental Scraper | $0.60/1K | Apartments & Units

Scrape Zillow rentals and available apartment units. Export advertised rent, base rent, required monthly fees, availability and leasing contacts to CSV.

Pricing

from $0.60 / 1,000 paid plans: saved rental property or units

Rating

0.0

(0)

Developer

Hundevmode Labs

Hundevmode Labs

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

18 days ago

Last modified

Categories

Share

Zillow Rental Scraper

Collect Zillow rental listings and available apartment units with advertised monthly rent, required monthly fees and move-in information. Search a city or ZIP, paste a rental search URL, or supply a supported apartment or building page.

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

What you can collect

  • Expand supported Zillow apartment and building pages into identifiable available units.
  • Compare advertised monthly rent, base rent and required monthly fees when Zillow provides them.
  • Export unit number, availability date, lease term and public leasing contact fields.
  • Apply rent, bedroom and living-area filters to the expanded unit rows.

How to use Zillow Rental Scraper

  1. Enter locations, a rental search URL or a supported apartment/building URL.
  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

{
"startUrls": [
{
"url": "https://www.zillow.com/apartments/austin-tx/maa-wells-branch/5XhsyQ/"
}
],
"maxResults": 10
}

This example is a starting point; replace its sources with your own. URL-only runs should leave locations empty.

Input options

InputPurposeDefault
locationsUp to 100 cities with state or five-digit ZIP codes; rental search is selected automatically.Empty
startUrlsRental search, /apartments/ or /b/ building URLs as [{"url":"…"}].Empty
maxResultsMaximum new rental property or available unit rows this run.100
minPrice / maxPriceAdvertised monthly rent in USD; applied to units after building expansion.Unset
Size filtersBedrooms, bathrooms and living area in square feet.Unset
resumeFromRunIdContinue the latest finished batch with the same query.Unset
advancedOptional 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 rental property or unit record. Missing source fields are null. The default table uses readable column labels while exports keep stable field names.

DataColumns
Unit and buildingrecordId, rowType, zpid, url, buildingUrl, buildingName, unitNumber
Locationaddress, city, state, zipcode
RentmonthlyRent, baseRent, requiredMonthlyMinFee
Move-in informationavailableFrom, leaseTerm
Size and contactbedrooms, bathrooms, livingArea, listingPhone

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.

Search pagination and bounded map splitting cover listing areas; supported building pages expand their actual available units. Unavailable units and unsupported source layouts can reduce coverage.

💳 Pricing and spending limits

Apify accountPrice per 1,000 rental property or unit rowsCollection allowance
Paid plan$0.60Requested count, source availability and run limits
Free$1.5050 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.00155, 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 issueNext step
Result, request, time or download ceilingUse PAGINATION.nextInput if hasMore=true; adjust the next batch’s limits.
Temporary restriction or HTTP 403Bounded automatic recovery has already been attempted. Retain progress and try the continuation later. A fresh run does not guarantee that access is restored.
Spending limitKeep saved rows and resume with a new per-run budget. The budget is not shared across the chain.
Free collection allowanceContinuation and Resurrect do not replenish it. Upgrade the account before collecting beyond the Free allowance.
Invalid input or changed queryCorrect the input; keep the original query for continuation or start a separate collection.
Missing checkpoint after a hard stopA 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 rental-specific fields and available apartment-unit expansion. Use Zillow Scraper for basic rental search cards, or Zillow ZIP Code Scraper when per-territory quotas matter more than unit expansion.

Frequently asked questions

Is one result a building, floor plan or apartment?

Individual rental properties and identifiable available units are emitted. Supported building pages are expanded into their available units. A floor-plan-only estimate without an identifiable unit is not presented as an available apartment.

Does the advertised rent include every fee?

Not necessarily. monthlyRent, baseRent and requiredMonthlyMinFee reflect the source fields when present. Unknown fees are null; this is not a guaranteed total move-in cost.

Can I collect a single apartment building?

Yes. Leave locations empty and paste the apartment or building URL into startUrls. This avoids adding a separate city search.

Why can availability differ when I reopen Zillow?

Units, prices and availability can change during and after a run. Use the collection timestamp and verify current terms before making a rental decision.

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.