# Zumper Rental Listings Scraper — Search + Details (`haketa/zumper-scraper`) Actor

Search US apartments and houses for rent on Zumper: price, beds/baths, address, phone, agent and brokerage, amenities, availability — plus optional building details (relay email, homepage, year built). Keyless, no anti-bot.

- **URL**: https://apify.com/haketa/zumper-scraper.md
- **Developed by:** [Haketa](https://apify.com/haketa) (community)
- **Categories:** Real estate, Lead generation
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Zumper Rental Listings Scraper — Search + Details

Search **US apartments & houses for rent on Zumper** in bulk and get **price, beds/baths, address, phone, agent & brokerage, amenities and availability** — plus optional **building details** (contact email, homepage, year built, units). Clean JSON/CSV/Excel.

Uses Zumper's public mobile JSON API — **keyless, no anti-bot, pure HTTP** — so it's fast and reliable at scale.

> **About contacts & "emails":** Zumper exposes a **real phone on every listing** plus the **agent & brokerage name**. Email is a **Zumper relay address (`@zump.co`)** available on some buildings — it reaches the landlord *through* Zumper, it's not their raw inbox. For the real landlord email, the building's **homepage** (property-management website, included when available) is the place to look. This Actor gives you phone + agent + brokerage + relay-email + homepage — a complete outreach set.

***

### What this Actor does

For each city/search you point it at, it returns every rental listing with:

- **Pricing & layout** — min/max price, min/max bedrooms & bathrooms, property type.
- **Location** — address, city, state, zip, neighborhood, lat/lng.
- **Contact** — phone (real), agent name, brokerage name.
- **Listing** — availability date, pet policy, rating, amenities, title, Zumper URL.
- **Building details (optional)** — relay email (`@zump.co`), homepage, year built, unit count, building description.

Point it with a full URL, a path, or just a city slug — and it paginates through the results.

***

### Why use it

- **Rental market data at scale.** Pull entire cities of listings with price, beds and location for market analysis or aggregation.
- **Outreach-ready contacts.** Phone + agent + brokerage on every listing; relay email + building homepage when available.
- **Keyless & clean.** Public JSON API, no key, no anti-bot, no captcha.
- **Flexible input.** URL, path or city slug; multiple searches per run.
- **Building enrichment.** Optional building page adds email, homepage and year built.

***

### Who it's for

- **Rental marketplaces & aggregators** sourcing US listings.
- **Real-estate & proptech teams** building rental datasets and market dashboards.
- **Lead-gen / outreach teams** contacting property managers (phone + agent + homepage).
- **Analysts** studying rent, availability and inventory by city.

***

### Quick start

#### Run it in the console (no code)

1. In **Search URLs / cities**, add one per line:

   ```
   /apartments-for-rent/new-york-ny
   https://www.zumper.com/apartments-for-rent/austin-tx
   san-francisco-ca
   ```

2. Keep **Include building details** on for email/homepage/year-built.

3. Set **Max listings**, click **Start**, export as **JSON, CSV, Excel or HTML**.

Leave it empty for a **demo** (San Francisco).

#### Run it via API (Python)

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run_input = {
    "searchUrls": ["/apartments-for-rent/new-york-ny"],
    "includeDetails": True,
    "maxItems": 500,
}

run = client.actor("YOUR_USERNAME/zumper-scraper").call(run_input=run_input)

for r in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(f"{r['buildingName']} — ${r['minPrice']} — {r['phone']} — {r['agentName']}")
```

#### Run it via API (JavaScript)

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });

const run = await client.actor('YOUR_USERNAME/zumper-scraper').call({
    searchUrls: ['san-francisco-ca'],
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((r) => console.log(`${r.address}: $${r.minPrice}-${r.maxPrice} — ${r.phone}`));
```

***

### Input

| Field | Type | Description |
|---|---|---|
| **Search URLs / cities** | array | Full URL, path (`/apartments-for-rent/city-st`) or city slug. Empty = demo. |
| **Include building details** | boolean | Fetch each listing's building page for relay email, homepage, year built, units. Default on. |
| **Max listings** | integer | Total cap across searches. Default 200. |
| **Speed (parallel searches)** | integer | Searches at once. Default 5. |
| **Proxy configuration** | object | Apify Proxy. On by default. |

***

### Output

One record per listing:

```json
{
  "listingId": "58574872",
  "buildingId": "1717500",
  "buildingName": "340 Fremont",
  "address": "340 Fremont St",
  "city": "San Francisco", "state": "CA", "zipcode": "94105",
  "neighborhood": "Rincon Hill",
  "lat": "37.78", "lng": "-122.39",
  "minPrice": "4515", "maxPrice": "8228",
  "minBedrooms": "0", "maxBedrooms": "2",
  "minBathrooms": "1", "maxBathrooms": "2",
  "propertyType": "apartment",
  "dateAvailable": "2026-11-01",
  "pets": "cats, dogs",
  "phone": "(650) 753-5405",
  "agentName": "340 Fremont",
  "brokerageName": "Equity Residential",
  "email": "1911523@zump.co",
  "homepage": "https://www.equityapartments.com/...",
  "yearBuilt": "2016",
  "unitCount": "44",
  "amenities": "Pool; Gym; Parking; ...",
  "url": "https://www.zumper.com/apartment-buildings/1717500/340-fremont-san-francisco-ca",
  "scrapedAt": "2026-10-12T12:00:00.000Z"
}
```

| Field | Description |
|---|---|
| `minPrice` / `maxPrice` / `min-maxBedrooms` / `min-maxBathrooms` | Pricing & layout. |
| `address` / `city` / `state` / `zipcode` / `neighborhood` / `lat` / `lng` | Location. |
| `phone` / `agentName` / `brokerageName` | Contact (phone is the real number). |
| `email` | Zumper relay email (`@zump.co`) — present on some buildings (with *Include details*). |
| `homepage` | Building / property-management website — where the real landlord email usually lives. |
| `yearBuilt` / `unitCount` / `amenities` / `dateAvailable` / `pets` | Building & listing details. |
| `url` | Zumper listing/building URL. |
| `scrapedAt` | ISO timestamp. |

***

### Tips & notes

- **Contacts:** phone + agent + brokerage are on ~every listing. The `@zump.co` email is a relay (routes through Zumper); for the raw landlord email, use the building `homepage`.
- **Turn off details for speed:** `includeDetails: false` skips the per-building request (no email/homepage/year-built) and runs much faster for pure market data.
- **City formats:** `/apartments-for-rent/<city>-<state>` (e.g. `/apartments-for-rent/new-york-ny`). A full URL or bare slug also works.
- **Dedupe** on `listingId` or `buildingId` across searches.
- **Max listings** bounds the run; raise it to sweep a whole city.

***

### Frequently asked questions

**Do I need an API key?**
No — Zumper's public mobile JSON API, keyless and without anti-bot.

**Does it give landlord emails?**
It gives a Zumper **relay** email (`@zump.co`) on some buildings, plus **phone + agent + brokerage** on ~every listing and the building **homepage** (where the real email usually is). Zumper itself hides raw landlord inboxes behind its messaging relay.

**Can I scrape a whole city?**
Yes — it paginates through the search; set **Max listings** to control volume.

**What identifies a listing uniquely?**
`listingId` (and `buildingId` for the building).

**Is it good for a rental aggregator or market analysis?**
Yes — clean, structured price/beds/location/contact data across US cities.

***

### Export & integrate

Results are available as **JSON, CSV, Excel, HTML** and via the **Apify API**. Push to **Google Sheets**, a **webhook**, **Make**, **Zapier** or your database — and **schedule** runs to keep rental inventory fresh.

*Data from Zumper's public listings. Not affiliated with Zumper.*

# Actor input Schema

## `searchUrls` (type: `array`):

One Zumper search per line. Paste a full URL (`https://www.zumper.com/apartments-for-rent/new-york-ny`), a path (`/apartments-for-rent/new-york-ny`), or just a city slug (`new-york-ny`). Leave empty for a demo (San Francisco).

## `includeDetails` (type: `boolean`):

For each listing, also fetch the building page for the relay contact email (@zump.co), homepage, year built and unit count. Adds one request per listing.

## `maxItems` (type: `integer`):

Maximum listings to scrape in total (across all searches).

## `maxConcurrency` (type: `integer`):

How many searches to process at once.

## `proxyConfiguration` (type: `object`):

Apify Proxy. On by default — the API is public, rotation keeps large runs smooth.

## Actor input object example

```json
{
  "searchUrls": [
    "/apartments-for-rent/san-francisco-ca",
    "/apartments-for-rent/new-york-ny"
  ],
  "includeDetails": true,
  "maxItems": 200,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `listingId` (type: `string`):

Listing ID

## `buildingId` (type: `string`):

Building ID

## `title` (type: `string`):

Listing title

## `buildingName` (type: `string`):

Building name

## `address` (type: `string`):

Address

## `formattedAddress` (type: `string`):

Formatted address

## `city` (type: `string`):

City

## `state` (type: `string`):

State

## `zipcode` (type: `string`):

Zip code

## `neighborhood` (type: `string`):

Neighborhood

## `lat` (type: `string`):

Latitude

## `lng` (type: `string`):

Longitude

## `minPrice` (type: `string`):

Min price

## `maxPrice` (type: `string`):

Max price

## `minBedrooms` (type: `string`):

Min bedrooms

## `maxBedrooms` (type: `string`):

Max bedrooms

## `minBathrooms` (type: `string`):

Min bathrooms

## `maxBathrooms` (type: `string`):

Max bathrooms

## `propertyType` (type: `string`):

Property type

## `dateAvailable` (type: `string`):

Date available

## `pets` (type: `string`):

Pet policy

## `rating` (type: `string`):

Rating

## `phone` (type: `string`):

Contact phone (real)

## `agentName` (type: `string`):

Agent name

## `brokerageName` (type: `string`):

Brokerage

## `email` (type: `string`):

Zumper relay email @zump.co

## `homepage` (type: `string`):

Building homepage

## `yearBuilt` (type: `string`):

Year built

## `unitCount` (type: `string`):

Unit count

## `amenities` (type: `string`):

Amenities

## `url` (type: `string`):

Zumper listing URL

## `scrapedAt` (type: `string`):

Timestamp

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchUrls": [
        "/apartments-for-rent/san-francisco-ca",
        "/apartments-for-rent/new-york-ny"
    ],
    "maxItems": 200,
    "maxConcurrency": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("haketa/zumper-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchUrls": [
        "/apartments-for-rent/san-francisco-ca",
        "/apartments-for-rent/new-york-ny",
    ],
    "maxItems": 200,
    "maxConcurrency": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("haketa/zumper-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchUrls": [
    "/apartments-for-rent/san-francisco-ca",
    "/apartments-for-rent/new-york-ny"
  ],
  "maxItems": 200,
  "maxConcurrency": 5
}' |
apify call haketa/zumper-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,haketa/zumper-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xKdwAp2ILZBfV4eyy/builds/0Ble1MeRSbtuj5ELm/openapi.json