# Apartment List Email Scraper (`leads-scraper/apartment-list-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/apartment-list-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

### Apartment List Email Scraper - structured rental leads from a matchmaking marketplace

The Apartment List Email Scraper extracts publicly indexed leasing contacts from Apartment List and writes them to an Apify dataset. It serves proptech vendors, multifamily marketing agencies and suppliers who sell into apartment communities.

Apartment List measured strong on identity and modest on volume. In a run against live Google, roughly ten parsed result blocks produced seven identities, seven resolvable profile URLs and five unique emails.

Read that as a quality-over-quantity result. Most rows the Apartment List Email Scraper returns arrive with an account name and a working profile link, which is what makes them useful in a CRM.

Five unique emails per ten blocks is the lowest count in the rental batch, so plan for a longer run or a second source if you need raw send volume rather than named accounts.

The usual pairing is to run the Apartment List Email Scraper for named accounts, then add the [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) or the [RentCafe Email Scraper](https://apify.com/leads-scraper/rentcafe-email-scraper) in the same metro for extra addresses.

#### Who the Apartment List 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 Apartment List Email Scraper to build a qualified territory list. Insurance brokers selling landlord and multifamily policies work the same rows.

Leasing offices publish these addresses on purpose because inbound enquiries are the point of the listing. That makes this a B2B contact list rather than a consumer harvest - and it still deserves compliant outreach.

Sales operations teams also treat the Apartment List Email Scraper as an enrichment source, matching rows to an existing account list on property name and profile link.

### What the Apartment List Email Scraper actually does

The Apartment List Email Scraper is a Google search-results parser with a domain-filtered email extractor attached. It never touches Apartment List directly.

1. Reads your input: keywords, location, email domains and limits.
2. Builds Google queries with the `site:` operator against `apartmentlist.com`, for example `site:apartmentlist.com property manager "@gmail.com" "Orlando"`.
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 Apartment List, does not use any Apartment List API, and does not open the Apartment List website. There is no browser, no JavaScript rendering, no authentication and no cookies.

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

### Key features of the Apartment List 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 Apartment List Email Scraper's query set.

### How the Apartment List Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. On a platform where email yield is already modest, leaving expansion on matters more than usual.

With `expandQueries` on, each keyword and email-domain pair is searched in several phrasings. The Apartment List 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.

Apartment List is a rentals-only domain, so the Apartment List Email Scraper needs no additional `inurl:` narrowing to exclude for-sale inventory. Every indexed page is already rental inventory.

Turning expansion off will noticeably shrink an already modest email count here. Leave it on unless you are deliberately running a cheap sample with the Apartment List Email Scraper.

### Input settings for the Apartment List 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 Apartment List Email Scraper

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

Because email yield here is modest, start at metro level rather than neighbourhood level: `Orlando FL`, `Jacksonville FL`, `Omaha NE`, `Des Moines IA`, `Albuquerque NM`.

Move to a submarket only once a metro run shows healthy volume: `Winter Park Orlando`, `Riverside Jacksonville`, `Benson Omaha`, `Nob Hill Albuquerque`. Narrowing too early is the most common cause of a thin run.

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

Set `countryCode: "US"` so the proxy resolves from a US exit, and include the state abbreviation for ambiguous names - `Springfield MO` and `Springfield IL` are different rental markets.

If a location comes back thin, widen one step at a time - suburb, metro, state - and raise `maxPagesPerQuery` before concluding the Apartment List Email Scraper is misconfigured.

#### Choosing keywords and email domains

Role-shaped keywords tend to work well on a platform with account-style pages. Try `property manager`, `community manager`, `leasing office`, `management company` and `apartment community`.

`customDomains` drives volume more than any other field, and on this platform that lever matters most. Free-mail domains are the default because smaller operators genuinely publish `@gmail.com` and `@yahoo.com` addresses.

Widen with `@outlook.com` and `@hotmail.com` when a run looks thin. The Apartment List Email Scraper keeps only addresses ending in a domain you listed, so a short domain list produces a short dataset.

### Output data from the Apartment List Email Scraper

Every dataset item produced by the Apartment List 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.apartmentlist.com/{username}`. Most rows from the Apartment List Email Scraper carry one, which is why this Actor suits account-based workflows.

### Example runs with the Apartment List Email Scraper

A metro run for a tenant screening provider prospecting Orlando:

```json
{
  "keywords": ["property manager", "community manager"],
  "location": "Orlando FL",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com"],
  "maxEmails": 150,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "leasing office", "inquiries", "property manager"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Two representative dataset rows:

```json
[
  {
    "network": "Apartment List",
    "keyword": "property manager",
    "query": "site:apartmentlist.com property manager \"@gmail.com\" \"Orlando FL\"",
    "title": "Lakeview Terrace Apartments - Orlando, FL | Apartment List",
    "accountName": "Lakeview Terrace Apartments",
    "fullName": "Lakeview Terrace Apartments",
    "username": "lakeview-terrace-orlando-fl",
    "profileUrl": "https://www.apartmentlist.com/lakeview-terrace-orlando-fl",
    "url": "https://www.apartmentlist.com/lakeview-terrace-orlando-fl",
    "description": "On-site property manager. Leasing enquiries: lakeviewterracepm@gmail.com",
    "email": "lakeviewterracepm@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T15:02:44Z"
  },
  {
    "network": "Apartment List",
    "keyword": "community manager",
    "query": "site:apartmentlist.com community manager contact \"@outlook.com\" \"Orlando FL\"",
    "title": "Winter Park Commons - Apartments for Rent | Apartment List",
    "accountName": "Winter Park Commons",
    "fullName": "Winter Park Commons",
    "username": "winter-park-commons-orlando-fl",
    "profileUrl": "https://www.apartmentlist.com/winter-park-commons-orlando-fl",
    "url": "https://www.apartmentlist.com/winter-park-commons-orlando-fl",
    "description": "Community manager contact: winterparkcommons@outlook.com. Tours by appointment.",
    "email": "winterparkcommons@outlook.com",
    "emailDomain": "@outlook.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T15:06:19Z"
  }
]
```

Note the third domain in that input. Adding `@outlook.com` is the cheapest way to raise the Apartment List Email Scraper's email count without sacrificing the identity data you came for.

For a broader sweep, move `location` to a state and raise `maxEmails`. Leave `maxConcurrency` at 5 unless you have a reason to change it; the Apartment List Email Scraper already runs its queries in parallel.

### Use cases for the Apartment List Email Scraper

| Audience | How they use the Apartment List 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 communities that publish an address and field enquiries by email |
| Tenant screening providers | Reach operators in growth metros who lack a formal screening workflow |
| Smart-lock and IoT installers | Prospect apartment communities in a metro before a regional rollout |
| Renovation and turn suppliers | Build a make-ready, flooring and appliance outreach list per metro |
| Maintenance and landscaping contractors | Assemble a territory list with enough context to qualify each stop |
| Multifamily marketing agencies | Shortlist under-marketed communities, then pitch creative and paid media |
| Insurance brokers | Reach operators and owners 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 Apartment List 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 Apartment List Email Scraper surfaces candidates; the sending decision stays with you.

### Limitations of the Apartment List Email Scraper

- Email volume is the lowest in this rental batch: five unique emails per ten parsed blocks in testing. Budget a longer run or add a second source.
- 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. Apartment List is strong here, but some rows still return `username: null` and an empty `profileUrl`. That is a Google limitation, not a defect.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the email. Verify those rows before sending.
- The Apify GOOGLE_SERP proxy is required. The Apartment List 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 Apartment List Email Scraper is not affiliated with or endorsed by Apartment List.

### Apartment List Email Scraper FAQ

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

In a measured run against live Google, roughly ten parsed result blocks produced seven identities, seven profile URLs and five unique emails. Identity coverage is strong; email volume is the lowest of the rental batch. Counts vary with location, keywords and domain filter.

#### How do I raise the email count?

Add domains. Putting `@outlook.com` and `@hotmail.com` into `customDomains` is the single most effective change, followed by widening `location` and raising `maxPagesPerQuery`.

#### Does the Apartment List Email Scraper log into Apartment List?

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`. A metro phrase does more for list quality than any other setting in the Apartment List Email Scraper, and starting at metro level protects an already modest yield.

#### 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 Apartment List 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 Apartment List 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 on this platform the practical ceiling is what Google has indexed rather than the plan limit.

#### Which sibling Actors pair well with this one?

[Redfin Rentals Email Scraper](https://apify.com/leads-scraper/redfin-rentals-email-scraper) for raw email volume and [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) for more of the same account-shaped rows.

#### 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 |
|---|---|
| [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 |
| [Apartment List Phone Number Scraper](https://apify.com/neuro-scraper/apartment-list-phone-number-scraper) | Public phone numbers 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 |
| [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) | Public contact emails from Zumper |
| [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 |
| [Land And Farm Email and Phone Number Scraper](https://apify.com/neuro-scraper/land-and-farm-email-and-phone-number-scraper) | Emails and phone numbers from Land And Farm |

### Leave a review

If the Apartment List 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 Apartment List Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

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

Search terms describing the Apartment List 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 Apartment List.

## `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 Apartment List 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/apartment-list-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/apartment-list-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/apartment-list-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/apartment-list-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/SqrAibXgoxTMncL37/builds/2NQfAGNIbv8PUavTu/openapi.json