Zumper Scraper

Zumper Scraper at a glance

Zumper Scraper is a ready-to-run Apify actor from abotapi for collecting real estate data. Its documented output includes id, change type (incremental mode), url, title and building, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Real Estate, Lead Generation, Automation
Pricing: $2.00 per 1,000 results (Free plan), from $1.20 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 26 options

Scrape Zumper.com rental listings: apartments, houses, condos and rooms. Pulls 60+ fields per listing, including monthly rent, beds/baths, square footage, decoded amenities, agent name and phone, ratings, availability and full-resolution photos. Search by location with filters, or paste Zumper URLs.

What Zumper Scraper can do

60+ fields per listing, core data straight from the results page. Price, beds/baths, square footage, amenities, agent name, phone, rating and photos come back without turning on detail fetching.
Amenities decoded to plain text. Amenities and building features come back as readable labels ("In-Unit Laundry", "Fitness Center", "Garage Parking"), not opaque numeric codes.
Full photo URLs, not just IDs. Every image is returned as a ready to open URL.
Two ways to find data. Search by location and filters, or paste specific search, building or listing URLs (multiple URLs supported).
Availability monitoring. Scheduled runs classify every listing as NEW, UPDATED, UNCHANGED, REAPPEARED or EXPIRED, with per campaign state you can name or share.
Resume long pulls. Continue an interrupted or unbounded walk across separate runs without paying twice for what was already collected.

Choose what to collect

These inputs let you configure Zumper Scraper - Rentals, Prices, Agents & 60+ Fields. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string · required	search = build URLs from the search fields below; url = pass through your own Zumper URLs. Choices: search, url
`locations`array	Search mode only. City, state or neighborhood slug or name, e.g. "San Francisco, CA", "new-york-ny" or "Austin, TX". Leave empty to search New York, NY. A bare ZIP code is not a Zumper search page: to search one ZIP, paste its city and ZIP link (for example /apartments-for-rent/san-francisco-ca/94110) in URL mode. Multiple locations supported. Ignored in URL mode.
`propertyCategory`string	Search mode only for choosing which rental category to browse. In URL mode it filters nothing: the category is read from the pasted URL, and this value is used only as the label on the saved records when the pasted URL does not name a category. Choices: apartments, houses, condos, rooms
`petsAllowed`array	Search mode only. Asks Zumper for listings that allow the selected pets. It is not re-checked against the returned listings, and it has no effect in URL mode.
`urls`array	URL mode only. Paste Zumper search-results URLs or individual building/listing URLs. The filter and sort fields below still apply to a pasted search-results URL; a pasted building or listing URL is saved as-is. Search URLs continue from their page number onward. Supported shapes: city, category (apartments/houses/condos/rooms), paginated, filtered or sorted (price-min/max, bed-min/max, bath-min, pets, sort), neighborhood and city/ZIP search pages (the city and ZIP form, for example /apartments-for-rent/san-francisco-ca/94110), plus building or listing pages. Facets in a pasted URL win over the filter fields below.
`minPrice`integer	Applies in BOTH search mode and URL mode. Keeps listings priced at or above this monthly rent. In URL mode the results of a pasted search-results URL are narrowed after they are read; a pasted building or listing URL is saved as-is.
`maxPrice`integer	Applies in BOTH search mode and URL mode. Keeps listings priced at or below this monthly rent. In URL mode the results of a pasted search-results URL are narrowed after they are read; a pasted building or listing URL is saved as-is.

Show 19 more inputs

More input fields
Input	What it controls
`minBedrooms`integer	Applies in BOTH search mode and URL mode. Keeps listings that can offer at least this many bedrooms; 0 = studio. In URL mode the results of a pasted search-results URL are narrowed after they are read; a pasted building or listing URL is saved as-is.
`maxBedrooms`integer	Applies in BOTH search mode and URL mode. Keeps listings that start at or below this many bedrooms. In URL mode the results of a pasted search-results URL are narrowed after they are read; a pasted building or listing URL is saved as-is.
`minBathrooms`integer	Applies in BOTH search mode and URL mode. Keeps listings that can offer at least this many bathrooms. In URL mode the results of a pasted search-results URL are narrowed after they are read; a pasted building or listing URL is saved as-is.
`sortBy`string	Applies in BOTH search mode and URL mode. Orders the listings that get saved. In URL mode the results of a pasted search-results URL are reordered after they are read; a pasted building or listing URL is saved as-is. Choices: default, price-asc, price-desc, newest, rating-desc
`fetchDetails`boolean	Add full description, amenity groups, pet policy, parking, deposits, fees, lease terms, units / floorplans, full agent contacts and Zumper's category ratings + resident-feedback summary. The results page already returns ~70 fields including price, beds/baths, decoded amenities, agent name, phone, rating and photos, so leaving this off is faster and cheaper.
`maxPages`integer	Results pages walked per location/URL. Leave empty to walk every result page (still bounded by Max listings). Pages stop early once Max listings is reached.
`maxListings`integer	Stop after this many listings across all searches. 0 = unlimited.
`resumeFromRunId`string	Paste a previous run ID or dataset ID to continue an unbounded walk across separate runs. Listings already collected there (matched by id) are skipped, so this run only saves the new ones. Leave empty for a normal fresh run. This continues ONE specific interrupted run; for recurring monitoring of the same search, use Incremental mode below instead.
`incrementalMode`boolean	Turn this on for daily/weekly or other recurring monitoring of the SAME search. The first run returns every matching listing as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED listings. UPDATED means any output field changed (rent and previous rent, availability date, beds, baths, size, amenities, description, photos, fees, specials, units) except scrapedAt and the fields you list in Ignore fields; the changed fields are named in changedFields. Order of the amenity lists never counts. Reviews are not part of this record. Turn on "Emit unchanged" or "Emit expired" only when you also want those returned (and billed). State is kept separately per location/category/filter/fetchDetails setup; use State key to name or deliberately share a monitoring campaign. Defaults off, so existing schedules are unaffected. To continue one specific interrupted run instead, use Resume from a previous run above.
`stateKey`string	Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the location/category/filters/fetchDetails, so different searches then never mix state with each other.
`emitUnchanged`boolean	Off by default. Turn on to also return listings that have not changed since the last run, marked UNCHANGED. This returns (and bills) extra rows you already have, so leave it off unless you specifically want the full snapshot every run.
`emitExpired`boolean	Off by default. Turn on to also return listings that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search, not when Max pages/Max listings capped it or when Resume was used. This returns (and bills) extra synthetic rows, so leave it off unless you need expiry tracking.
`expireAfterMissedScans`integer	With Emit expired on, a listing is reported EXPIRED only after it was missing from this many CONSECUTIVE complete scans of the same search (default 1 = the first complete scan that misses it). A listing that comes back resets the count. EXPIRED means the listing dropped out of the search results; without a detail check a dropped listing and a delisted one look the same, so use dateAvailable and the price fields rather than reading EXPIRED as unavailable.
`changeScope`string	all (default) compares every output field except the ones excluded below. priceAndStock compares ONLY the rent fields (minPrice, maxPrice, previousPrice, averagePrice, currency), dateAvailable, and for units / floorplanListings each element's id plus its price and availability keys, so description, photo, amenity or agent edits never create a billable UPDATED row. Changing scope on an explicit State key does not re-report existing listings; an automatic key is unaffected. Choices: all, priceAndStock
`compactUpdates`boolean	Return UPDATED and EXPIRED rows as slim records: id, url, title, address, current price and availability, changedFields, priceChanges (old and new per field) and variantChanges (per unit ADDED, REMOVED or CHANGED). NEW rows stay full. Compact rows carry no detail-page data, so they never add the detail enrichment charge. Default off.
`ignoreFieldsForChanges`array	Field names (dotted paths reach inside objects and every array element, for example units.status) that must NOT count as a change. The fields stay in the output; they are only left out of the comparison and out of changedFields. scrapedAt is always ignored. Existing saved state is re-compared under this list, so adding a field never reports every listing as UPDATED.
`mcpConnectors`array	Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify Settings, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON; the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
`notionParentPageUrl`string	URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idID (text)

changeTypeChange type (incremental mode) (text)

urlURL (link)

titleTitle (text)

buildingNameBuilding (text)

propertyCategoryCategory (text)

addressAddress (text)

cityCity (text)

stateState (text)

zipcodeZIP (text)

neighborhoodNeighborhood (text)

minPriceMin Rent (number)

Show 32 more fields

maxPriceMax Rent (number)

minBedroomsMin Beds (number)

maxBedroomsMax Beds (number)

minBathroomsMin Baths (number)

maxBathroomsMax Baths (number)

minSquareFeetMin Sqft (number)

maxSquareFeetMax Sqft (number)

dateAvailableAvailable (text)

ratingRating (number)

externalRatingExt. Rating (number)

agentNameAgent (text)

phonePhone (text)

primaryImagePhoto (image)

scrapedAtScraped At (text)

changedFieldsChanged fields (incremental mode) (array)

firstSeenAtFirst seen at (incremental mode) (date)

lastSeenAtLast seen at (incremental mode) (date)

detectedAtDetected at (incremental mode) (date)

leadScoreLead score 0-100 (incremental mode) (number)

priceChangeAmountPrice change amount (incremental mode) (number)

priceChangePercentPrice change percent (incremental mode) (number)

stateKeyState key (text)

descriptionDescription (text)

categoryRatingsCategory ratings (object)

reviewsSummaryReviews summary (text)

agentsAgents (array)

unitsUnits (array)

petPolicyPet policy (object)

parkingParking (object)

feesFees (object)

yearBuiltYear built (number)

previousPricePrevious price (number)

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "id": "64606115",
  "url": "https://www.zumper.com/apartment-buildings/p000000/sample-building-city-st",
  "padmapperUrl": null,
  "title": "1A with Balcony",
  "buildingName": "Sample Apartments",
  "propertyCategory": "apartments",
  "isBuilding": true,
  "address": "123 Sample St",
  "city": "San Francisco",
  "state": "CA",
  "zipcode": "94103",
  "neighborhood": "SOMA",
  "latitude": 37.77,
  "longitude": -122.4,
  "minPrice": 4035,
  "maxPrice": 6360,
  "previousPrice": 4200,
  "currency": "USD",
  "minBedrooms": 0,
  "maxBedrooms": 2,
  "minBathrooms": 1,
  "maxBathrooms": 2,
  "minSquareFeet": 509,
  "maxSquareFeet": 980,
  "dateAvailable": "2026-01-15",
  "listedOn": "2025-12-01T00:00:00.000Z",
  "modifiedOn": "2026-01-01T00:00:00.000Z",
  "unitAmenities": [
    "In-Unit Laundry",
    "Dishwasher",
    "Air Conditioning"
  ],
  "buildingAmenities": [
    "Fitness Center",
    "Garage Parking",
    "Roof Deck"
  ],
  "shortDescription": "Bright corner unit with balcony.",
  "rating": 9.3,
  "externalRating": 4.1,
  "agentName": "Sample Mgmt",
  "brokerageName": "Sample Brokerage",
  "phone": "(415) 555-0100",
  "primaryImage": "https://img.zumpercdn.com/000000000/1280x960",
  "images": [
    "https://img.zumpercdn.com/000000000/1280x960"
  ],
  "imageCount": 1,
  "scrapedAt": "2026-01-01T00:00:00.000Z"
}

Ways to use this data

Rent trend and market research: track rent ranges, price drops and new listings across neighborhoods and cities over time.
Apartment hunters and relocation services: pull filtered listings (price, beds, pets) for a target city into your own site or alert tool.
PropTech and rental aggregators: build a secondary Zumper sourced feed with agent contacts and photos, without visiting the site by hand.
Investors and property managers: monitor competing buildings' pricing and availability in a submarket.
Lead generation for movers and brokers: watch specific buildings or listings for status changes (NEW, price change, EXPIRED) and reach out through the agent contact on the record.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Zumper Scraper return?

The documented output for Zumper Scraper includes id, change type (incremental mode), url, title, building, category, address and city. Availability of each field depends on the source page and the selected mode.

How much does Zumper Scraper cost?

It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I get only new or changed listings on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated and reappeared listings (plus expired ones when emitExpired is on), and unchanged ones are not billed unless you turn on emitUnchanged.

Why did my run return fewer listings than I expected?

With several locations, Max listings is split into an equal share per location, and each stops at its share or its last page, whichever comes first. Filters (price, beds, baths, pets) also narrow the result set. On a recurring, incremental run over a location with a lot of steady state (unchanged) inventory, the per page budget can also be used up on suppressed rows before reaching new ones on the same page (see "How Max listings shapes a run" above). Raise Max listings, or set it to 0, to collect more.

Does emitExpired respect Max listings?

No. Max listings caps the live NEW/UPDATED/REAPPEARED side of a run; once a run qualifies to detect EXPIRED listings, every tracked listing found gone is pushed regardless of Max listings. See the known limitation under "Resume and recurring updates" above.

Can EXPIRED ever be wrong?

In specific cases, yes: overlapping or adjoining locations searched together in one run, or a stateKey that is shared or reused across a differently scoped or differently starting run (including a pasted URL that starts mid pagination), or a results page that loads without readable listing data, can make a still live listing look unscanned this run and get marked EXPIRED. See the known limitations under "Resume and recurring updates" above for the exact triggers and the workaround.