# Zumper Email Scraper (`leads-scraper/zumper-email-scraper`) Actor

Zumper Email Scraper SD - Zumper Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Zumper results by keyword, location and email domain - Zumper email extractor.

- **URL**: https://apify.com/leads-scraper/zumper-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Email Scraper - account-shaped rental leads with profile links attached

The Zumper Email Scraper extracts publicly indexed leasing contacts from Zumper and delivers them as a structured Apify dataset. It is built for proptech vendors, multifamily marketing agencies and suppliers who sell into apartment communities.

Zumper measured joint-best on identity in this batch. In a run against live Google, roughly ten parsed result blocks produced ten identities, ten resolvable profile URLs and six unique emails.

Six emails per ten blocks is a little below the volume leaders, but every parsed result came back with an account name and a working link. The Zumper Email Scraper is the account-based option in this family.

If you are building a target account list rather than a raw send list, that trade is usually worth taking. A row you can look up before writing converts better than a row you cannot.

A common pattern is to run the Zumper Email Scraper for the structured core of a territory, then top it up with the [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) or the [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) in the same metro.

#### Who the Zumper Email Scraper is for

Property management software vendors, leasing and tour-scheduling tools, tenant screening providers, and smart-lock or IoT installers all sell to the person behind the address on the listing.

Renovation and turn suppliers, landscaping firms and maintenance contractors use the Zumper Email Scraper to build a territory list with enough context to qualify each row. Insurance brokers selling landlord and multifamily policies work the same data.

Leasing offices publish these addresses on purpose because they want inbound enquiries. That makes this a B2B contact list, not a consumer harvest - which still leaves you responsible for how you send.

### What the Zumper Email Scraper actually does

The Zumper Email Scraper is a Google search-results parser with a domain-filtered email extractor bolted on. It never touches Zumper directly.

1. Reads your input: keywords, location, email domains and limits.
2. Builds Google queries with the `site:` operator against `zumper.com`, for example `site:zumper.com property manager "@gmail.com" "Seattle"`.
3. Fetches Google result pages through the Apify GOOGLE_SERP proxy using async `aiohttp` requests.
4. Parses each result block structurally by locating the `<h3>` title and then the smallest surrounding block, rather than depending on Google's CSS class names.
5. Extracts emails from the block text with a domain-filtered regular expression.
6. Deduplicates globally and pushes every lead to the Apify dataset immediately.

It does not log into Zumper, does not use any Zumper API, and does not open the Zumper website. There is no browser, no JavaScript rendering, no authentication and no cookies.

Everything the Zumper Email Scraper returns comes from publicly indexed Google search results: titles, snippets and site labels. If an address is not in that index, the Zumper Email Scraper cannot find it.

### Key features of the Zumper Email Scraper

| Feature | What it means in practice |
|---|---|
| Query expansion | Base, quoted, `intitle:` and one variant per query modifier. Base queries run first. |
| Global deduplication | Every email is emitted once across all queries and all pages of the run. |
| Email normalisation | Case-insensitive; understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` sign. |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals. |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br`. |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same result block. |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails`. |
| Retries | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request. |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty. |
| Re-queue | Blocked or failed queries are retried once at the end of the run. |
| Resumable state | Saved in the key-value store keyed by an input hash; throttled saves plus `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. |
| Fallback parser | If Google's markup changes, the whole-page parser degrades to "emails without account details" instead of "no emails". |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page. |

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, subject to what Google has indexed for the Zumper Email Scraper's query set.

### How the Zumper Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. One query against a national rental marketplace barely dents the index.

With `expandQueries` on, each keyword and email-domain pair is searched in several phrasings. The Zumper Email Scraper runs the base query first, then the quoted variant, then an `intitle:` variant, then one variant per entry in `queryModifiers`.

The defaults are `email`, `contact`, `leasing office`, `inquiries` and `property manager` - the words that sit next to a published address on a rental listing.

Zumper is a rentals-only domain, so the Zumper Email Scraper needs no additional `inurl:` narrowing to keep for-sale inventory out. Every indexed page is already rental inventory, which keeps the query set clean.

Turning expansion off makes the Zumper Email Scraper faster and cheaper but caps your reach at a few hundred results per keyword. Leave it on for any real prospecting run.

### Input settings for the Zumper Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["property manager", "apartments for rent"]` | Search terms describing the accounts you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional |
| `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email", "contact", "leasing office", "inquiries", "property manager"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1-20 | `5` | Parallel queries |

#### Location targeting in the Zumper Email Scraper

`location` is the highest-leverage input in the schema. Multifamily selling is territorial, and a run with no location produces a scattered list nobody can work.

Zumper skews urban, so dense coastal and tech metros are strong starting points: `Seattle WA`, `San Francisco CA`, `Boston MA`, `Chicago IL`, `Washington DC`.

In those metros a submarket beats the metro name almost every time: `Capitol Hill Seattle`, `Mission District San Francisco`, `Back Bay Boston`, `Logan Square Chicago`. Fewer rows, far better fit for a rep's patch.

Run one location per run. The value is appended verbatim to every query, so `Seattle OR Portland` becomes a literal phrase and usually returns less rather than more.

Set `countryCode: "US"` so the proxy resolves from a US exit, and add the state abbreviation when a city name is ambiguous - `Portland OR` and `Portland ME` are unrelated rental markets.

If a submarket returns almost nothing, widen one step at a time - neighbourhood, metro, state - before concluding the Zumper Email Scraper is misconfigured.

#### Choosing keywords and email domains

Role-shaped keywords work best on a platform with account-style pages. Try `property manager`, `leasing consultant`, `community manager`, `management company` and `landlord` alongside the defaults.

`customDomains` decides volume more than any other field. Free-mail domains are the default because independent landlords and smaller operators genuinely publish `@gmail.com` and `@yahoo.com` addresses on Zumper.

Add `@outlook.com` and `@hotmail.com` for coverage, or a named operator's domain when working one portfolio. The Zumper Email Scraper keeps only addresses ending in a domain you listed.

### Output data from the Zumper Email Scraper

Every dataset item produced by the Zumper Email Scraper carries all fourteen fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for listing-style titles |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, for example `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

Profile URLs follow the shape `https://www.zumper.com/{username}`. Because this platform exposes handles reliably, most rows from the Zumper Email Scraper arrive with both `username` and `profileUrl` filled in.

### Example runs with the Zumper Email Scraper

A submarket run for a smart-lock vendor working Seattle:

```json
{
  "keywords": ["property manager", "leasing consultant"],
  "location": "Capitol Hill Seattle",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 120,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "leasing office", "inquiries", "property manager"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Two representative dataset rows:

```json
[
  {
    "network": "Zumper",
    "keyword": "property manager",
    "query": "site:zumper.com property manager \"@gmail.com\" \"Capitol Hill Seattle\"",
    "title": "Broadway Court Apartments - Capitol Hill, Seattle | Zumper",
    "accountName": "Broadway Court Apartments",
    "fullName": "Broadway Court Apartments",
    "username": "broadway-court-seattle-wa",
    "profileUrl": "https://www.zumper.com/broadway-court-seattle-wa",
    "url": "https://www.zumper.com/broadway-court-seattle-wa",
    "description": "Managed on site. Tours and availability: broadwaycourtpm@gmail.com",
    "email": "broadwaycourtpm@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T13:21:09Z"
  },
  {
    "network": "Zumper",
    "keyword": "leasing consultant",
    "query": "site:zumper.com leasing consultant contact \"@yahoo.com\" \"Capitol Hill Seattle\"",
    "title": "Pike Terrace - Apartments for Rent | Zumper",
    "accountName": "Pike Terrace",
    "fullName": "Pike Terrace",
    "username": "pike-terrace-seattle-wa",
    "profileUrl": "https://www.zumper.com/pike-terrace-seattle-wa",
    "url": "https://www.zumper.com/pike-terrace-seattle-wa",
    "description": "Leasing consultant on site. Enquiries: piketerraceleasing@yahoo.com",
    "email": "piketerraceleasing@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T13:24:47Z"
  }
]
```

Rows like these import cleanly into a CRM and give a rep something concrete to check before the first touch. That is the main argument for starting a campaign with the Zumper Email Scraper.

For a broader sweep, drop `location` to a metro or state and raise `maxEmails`. Leave `maxConcurrency` at 5 unless you have a reason to change it.

### Use cases for the Zumper Email Scraper

| Audience | How they use the Zumper Email Scraper |
|---|---|
| Property management software vendors | Build an account-based demo pipeline with profile links for pre-call research |
| Leasing and tour-scheduling tools | Target listings that already publish an address and field enquiries by email |
| Tenant screening providers | Reach independent landlords and small operators in dense urban submarkets |
| Smart-lock and IoT installers | Prospect buildings in a specific neighbourhood before a rollout |
| Renovation and turn suppliers | Build a make-ready, flooring and appliance outreach list per submarket |
| Maintenance and landscaping contractors | Assemble a walkable or drivable territory list |
| Multifamily marketing agencies | Shortlist under-marketed buildings, then pitch creative and paid media |
| Insurance brokers | Reach landlords and small operators for landlord and multifamily policies |
| Sales operations teams | Enrich an existing account list using `accountName` and `profileUrl` as match keys |

### Responsible use, GDPR, CAN-SPAM and Fair Housing

Everything the Zumper Email Scraper collects is already published on public pages and indexed by Google. That does not move your obligations as the sender onto anyone else.

Under GDPR and similar regimes, have a lawful basis for processing business contact data, honour deletion and objection requests, and say in your first message where you found the address. Under CAN-SPAM, use accurate headers and subject lines, disclose your identity and postal address, and honour opt-outs promptly.

Fair Housing is genuinely relevant to US rental outreach. Keep messaging focused on your product and avoid anything that could be read as steering or as encouraging discrimination based on a protected characteristic.

None of this is legal advice. Check your campaign against your own jurisdiction's rules, and verify addresses before you send at volume. The Zumper Email Scraper surfaces candidates; the sending decision stays with you.

### Limitations of the Zumper Email Scraper

- It only finds contacts whose email is publicly visible in Google's index. Addresses behind a contact form or rendered in an image will not be found.
- Google caps a single query at roughly 300 results. Query expansion works around that ceiling; it does not remove it.
- `username` and `profileUrl` are only populated when the platform exposes a handle in Google's result. Zumper is strong here, but individual rows can still return `username: null` and an empty `profileUrl`. That is a Google limitation, not a defect.
- Email volume is slightly lower than the volume leaders in this family; six unique emails per ten parsed blocks in testing.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the email. Verify those rows before sending.
- The Apify GOOGLE_SERP proxy is required. The Zumper Email Scraper cannot run without Apify proxy credentials.
- Free Apify plans stop at 100 emails per run; paid plans are uncapped.
- Results vary with keywords, domains and location. No volume is guaranteed, and the Zumper Email Scraper is not affiliated with or endorsed by Zumper.

### Zumper Email Scraper FAQ

#### How many results should I expect from the Zumper Email Scraper?

In a measured run against live Google, roughly ten parsed result blocks produced ten identities, ten profile URLs and six unique emails. Identity coverage is excellent; email volume is moderate. Counts vary with location, keywords and domain filter.

#### Why does Zumper resolve handles when Apartments.com does not?

Google surfaces Zumper pages with handle-shaped URLs and account-style titles, so there is something to resolve. Apartments.com pages are indexed as listings without a resolvable handle.

#### Does the Zumper Email Scraper log into Zumper?

No. It reads Google search results through the Apify GOOGLE_SERP proxy. No login, no API key, no browser, no cookies.

#### Which input matters most?

`location`. On an urban-skewed platform, a submarket phrase does more for list quality than any other setting in the Zumper Email Scraper.

#### Can I target corporate domains instead of free-mail?

Yes. Replace `customDomains` with the domains you want; only addresses ending in one of them are kept.

#### What does `possiblyTruncated` mean?

Google cut the snippet near the email, so the address may be incomplete. Filter or verify those rows before a send.

#### Why does the Zumper Email Scraper run so many queries?

Google caps a single query at about 300 results, so expansion spreads the search across base, quoted, `intitle:` and modifier variants to reach past that ceiling.

#### Can I run the Zumper Email Scraper outside Apify?

No. The GOOGLE_SERP proxy is a required dependency and needs Apify proxy credentials.

#### Will I get duplicate addresses?

No. Deduplication is global across every query and page, so each unique email appears once per run.

#### Is 100 emails a hard cap?

Only on free plans. Paid plans are uncapped, though the practical ceiling is whatever Google has indexed.

#### How do I get more raw addresses in the same metro?

Pair the Zumper Email Scraper with the [Redfin Rentals Email Scraper](https://apify.com/leads-scraper/redfin-rentals-email-scraper) or the [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper), both of which measured higher on unique emails.

#### Does a run resume after a migration?

Yes. State is stored in the key-value store keyed by a hash of your input, with saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING`.

### Related Actors

| Actor | What it collects |
|---|---|
| [Zumper Email and Phone Number Scraper](https://apify.com/neuro-scraper/zumper-email-and-phone-number-scraper) | Emails and phone numbers from Zumper |
| [Zumper Phone Number Scraper](https://apify.com/neuro-scraper/zumper-phone-number-scraper) | Public phone numbers from Zumper |
| [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) | Public contact emails from Apartment List |
| [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) | Public contact emails from ApartmentFinder |
| [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) | Public contact emails from Apartments.com |
| [Century 21 Agent Email Scraper](https://apify.com/neuro-scraper/century-21-agent-email-scraper) | Public contact emails from Century 21 |
| [Coldwell Banker Agent Email Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-scraper) | Public contact emails from Coldwell Banker |
| [CommercialCafe Email Scraper](https://apify.com/neuro-scraper/commercialcafe-email-scraper) | Public contact emails from CommercialCafe |
| [CommercialSearch Email Scraper](https://apify.com/neuro-scraper/commercialsearch-email-scraper) | Public contact emails from CommercialSearch |
| [Compass Agent Email Scraper](https://apify.com/neuro-scraper/compass-agent-email-scraper) | Public contact emails from Compass |
| [Crexi Email Scraper](https://apify.com/leads-scraper/crexi-email-scraper) | Public contact emails from Crexi |
| [Domain Agents Email Scraper](https://apify.com/leads-scraper/domain-agents-email-scraper) | Public contact emails from Domain |
| [Homes & Land Email Scraper](https://apify.com/neuro-scraper/homes-and-land-email-scraper) | Public contact emails from Homes & Land |
| [Homes.com Email Scraper](https://apify.com/leads-scraper/homes-com-email-scraper) | Public contact emails from Homes.com |
| [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) | Public contact emails from HotPads |
| [Keller Williams Agent Email Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-scraper) | Public contact emails from Keller Williams |
| [Land And Farm Email Scraper](https://apify.com/leads-scraper/land-and-farm-email-scraper) | Public contact emails from Land And Farm |
| [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) | Public contact emails from Land.com |
| [LandWatch Email Scraper](https://apify.com/leads-scraper/landwatch-email-scraper) | Public contact emails from LandWatch |
| [LoopNet Email Scraper](https://apify.com/leads-scraper/loopnet-email-scraper) | Public contact emails from LoopNet |
| [OnTheMarket Email Scraper](https://apify.com/leads-scraper/onthemarket-email-scraper) | Public contact emails from OnTheMarket |
| [RealEstate.com.au Agents Email Scraper](https://apify.com/neuro-scraper/realestate-com-au-agents-email-scraper) | Public contact emails from realestate.com.au |
| [Realtor.ca Email Scraper](https://apify.com/leads-scraper/realtor-ca-email-scraper) | Public contact emails from Realtor.ca |
| [Realtor.com Rentals Email Scraper](https://apify.com/leads-scraper/realtor-com-rentals-email-scraper) | Public contact emails from Realtor.com |
| [Redfin Rentals Email Scraper](https://apify.com/leads-scraper/redfin-rentals-email-scraper) | Public contact emails from Redfin |
| [RE/MAX Agent Email Scraper](https://apify.com/leads-scraper/remax-agent-email-scraper) | Public contact emails from RE/MAX |
| [Rent.com Email Scraper](https://apify.com/leads-scraper/rent-com-email-scraper) | Public contact emails from Rent.com |
| [RentCafe Email Scraper](https://apify.com/leads-scraper/rentcafe-email-scraper) | Public contact emails from RentCafe |
| [Zillow Rentals Email Scraper](https://apify.com/leads-scraper/zillow-rentals-email-scraper) | Public contact emails from Zillow |
| [Apartment List Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartment-list-email-and-phone-number-scraper) | Emails and phone numbers from Apartment List |
| [ApartmentFinder Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartmentfinder-email-and-phone-number-scraper) | Emails and phone numbers from ApartmentFinder |
| [Apartments.com Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartments-com-email-and-phone-number-scraper) | Emails and phone numbers from Apartments.com |
| [Century 21 Email and Phone Number Scraper](https://apify.com/neuro-scraper/century-21-agent-email-and-phone-number-scraper) | Emails and phone numbers from Century 21 |
| [Coldwell Banker Email and Phone Number Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-and-phone-number-scraper) | Emails and phone numbers from Coldwell Banker |
| [CommercialCafe Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialcafe-email-and-phone-number-scraper) | Emails and phone numbers from CommercialCafe |
| [CommercialSearch Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialsearch-email-and-phone-number-scraper) | Emails and phone numbers from CommercialSearch |
| [Compass Email and Phone Number Scraper](https://apify.com/neuro-scraper/compass-agent-email-and-phone-number-scraper) | Emails and phone numbers from Compass |
| [Crexi Email and Phone Number Scraper](https://apify.com/leads-scraper/crexi-email-and-phone-number-scraper) | Emails and phone numbers from Crexi |
| [Domain Email and Phone Number Scraper](https://apify.com/leads-scraper/domain-agents-email-and-phone-number-scraper) | Emails and phone numbers from Domain |
| [Homes & Land Email and Phone Number Scraper](https://apify.com/neuro-scraper/homes-and-land-email-and-phone-number-scraper) | Emails and phone numbers from Homes & Land |
| [Homes.com Email and Phone Number Scraper](https://apify.com/leads-scraper/homes-com-email-and-phone-number-scraper) | Emails and phone numbers from Homes.com |
| [Keller Williams Email and Phone Number Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-and-phone-number-scraper) | Emails and phone numbers from Keller Williams |

### Leave a review

If the Zumper Email Scraper saved you time, please leave a star rating and a short review on
the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, a bug report, or a custom build request for the Zumper Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Zumper accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Zumper.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

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

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "property manager",
    "apartments for rent"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "leasing office",
    "inquiries",
    "property manager"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Zumper Email Scraper, stored in the run's default dataset.

# 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 = {
    "keywords": [
        "property manager",
        "apartments for rent"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "leasing office",
        "inquiries",
        "property manager"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/zumper-email-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 = {
    "keywords": [
        "property manager",
        "apartments for rent",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "leasing office",
        "inquiries",
        "property manager",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/zumper-email-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 '{
  "keywords": [
    "property manager",
    "apartments for rent"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "leasing office",
    "inquiries",
    "property manager"
  ]
}' |
apify call leads-scraper/zumper-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/zumper-email-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/Q1eBcz53gbiEfAWHg/builds/73ezX92udoxMXQr2H/openapi.json