# Apartments.com Email Scraper (`leads-scraper/apartments-com-email-scraper`) Actor

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

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

### Apartments.com Email Scraper - publicly indexed leasing contacts, by keyword and city

The Apartments.com Email Scraper turns Google's public index of Apartments.com into a structured list of leasing contact emails. It is built for proptech vendors, multifamily marketing agencies and suppliers who sell into apartment communities.

Point it at a keyword such as `property manager`, add a city, choose the email domains you care about, and the Apartments.com Email Scraper writes one dataset row per unique email address it finds.

One thing to know before you start: Apartments.com indexes property listing pages rather than manager profiles, so rows carry a leasing email without a resolvable handle. That is not a bug in the Apartments.com Email Scraper - it is how Google sees the site.

In a measured run against live Google, roughly ten parsed result blocks produced nine unique emails and zero rows with a usable `username` or `profileUrl`. Email volume is genuinely good here; identity resolution is not.

If you need rows with handles and profile links attached, the [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) and the [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) resolved a handle for every parsed result in the same test.

#### Who the Apartments.com Email Scraper is for

Property management software vendors, leasing and tour-scheduling tools, tenant screening providers, smart-lock and IoT installers all sell to the same buyer: the person whose address is printed on the listing.

Renovation crews, turn and make-ready suppliers, landscaping firms and maintenance contractors use the Apartments.com Email Scraper to build a city-level supplier prospecting list. Insurance brokers selling landlord and multifamily policies work the same data.

Agencies running multifamily marketing campaigns treat the Apartments.com Email Scraper as a territory-building step: one metro per run, then a hand-checked shortlist before any outreach.

Leasing offices publish those addresses deliberately, because they want inbound enquiries. That makes this a B2B contact list, not a consumer harvest - but it still deserves careful, compliant outreach.

### What the Apartments.com Email Scraper actually does

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

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

Everything the Apartments.com Email Scraper returns comes from publicly indexed Google search results: titles, snippets and site labels. If a leasing address is not in that index, the Apartments.com Email Scraper cannot see it.

### Key features of the Apartments.com 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 actually indexes for the Apartments.com Email Scraper's query set.

### How the Apartments.com Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. One query against a network the size of Apartments.com would leave most of the index untouched.

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

Turning expansion off makes the Apartments.com Email Scraper cheaper and faster, but it also caps your reach at a few hundred results per keyword.

The default modifiers for this Actor are `email`, `contact`, `leasing office`, `inquiries` and `property manager`. Those words are the ones that actually appear next to a published address on an apartment listing page.

Two keywords, two domains and five modifiers therefore produce a broad sweep rather than a single narrow query. Each of those queries has its own ~300-result ceiling, which is exactly the point.

### Input settings for the Apartments.com 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 Apartments.com Email Scraper

`location` is the single most valuable input in the whole schema. Apartment marketing is a local business, and an untargeted national sweep produces a list nobody can work.

Use a metro name for volume: `Dallas`, `Phoenix`, `Atlanta`, `Charlotte`. These are large multifamily markets with deep Apartments.com inventory and plenty of published leasing addresses.

Use a submarket name for precision: `Uptown Dallas`, `Buckhead Atlanta`, `Tempe AZ`, `South Lake Union Seattle`. Submarket runs return fewer rows but land closer to a genuine territory.

Run one city per run rather than stuffing several into one string. `location` is appended verbatim to every query, so `Austin OR Houston` becomes a literal phrase and usually returns less, not more.

Pair `location` with `countryCode: "US"` when you want the search proxy to resolve from a US exit. State abbreviations help disambiguate: `Portland OR` and `Portland ME` are different rental markets.

If a city returns almost nothing, widen one step at a time - suburb to metro, metro to state - before you conclude the Apartments.com Email Scraper is misconfigured. Most empty runs are a location that is too narrow, not a broken Actor.

#### Choosing keywords and email domains

The default keywords are a reasonable starting point, but role-shaped terms tend to outperform inventory-shaped ones. Try `leasing consultant`, `community manager`, `regional manager`, `apartment community` or `management company`.

`customDomains` decides everything about volume. Free-mail domains such as `@gmail.com` and `@yahoo.com` are the default because independent operators and small management companies genuinely use them.

To reach larger operators, add corporate domains you already know: a specific management company's domain, or `@outlook.com` and `@hotmail.com` for broader coverage. The Apartments.com Email Scraper keeps only addresses ending in a domain you listed, so a narrow list means a narrow dataset.

### Output data from the Apartments.com Email Scraper

Every dataset item produced by the Apartments.com 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 |

When a handle is available the profile URL follows the shape `https://www.apartments.com/{username}/`. On this platform that is the exception rather than the rule.

### Example runs with the Apartments.com Email Scraper

A focused submarket run for a smart-lock vendor prospecting Austin:

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

Two representative dataset rows. Both honestly show the handle gap described above:

```json
[
  {
    "network": "Apartments.com",
    "keyword": "property manager",
    "query": "site:apartments.com property manager \"@gmail.com\" \"Austin TX\"",
    "title": "The Ridgeline Apartments - Austin, TX | Apartments.com",
    "accountName": "The Ridgeline Apartments",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.apartments.com/the-ridgeline-austin-tx/",
    "description": "Leasing office open Mon-Sat. Tour requests: ridgelineleasing@gmail.com",
    "email": "ridgelineleasing@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T09:14:22Z"
  },
  {
    "network": "Apartments.com",
    "keyword": "leasing office",
    "query": "site:apartments.com leasing office contact \"@yahoo.com\" \"Austin TX\"",
    "title": "Barton Creek Flats - Apartments for Rent | Apartments.com",
    "accountName": "Barton Creek Flats",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.apartments.com/barton-creek-flats-austin-tx/",
    "description": "Contact the leasing team at bartoncreekflats@yahoo.com for availability",
    "email": "bartoncreekflats@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T09:16:41Z"
  }
]
```

Notice that `accountName` still carries the property name. Even without a handle, the Apartments.com Email Scraper gives you an address plus a named community you can personalise around.

A wider run for a maintenance supplier looks the same but swaps `location` for a metro and raises `maxEmails`. Keep `maxConcurrency` at 5 unless you have a reason to change it; the Apartments.com Email Scraper is already parallel by default.

### Use cases for the Apartments.com Email Scraper

| Audience | How they use the Apartments.com Email Scraper |
|---|---|
| Property management software vendors | Build a city-by-city list of communities to demo leasing, accounting or maintenance software to |
| Leasing and tour-scheduling tools | Target communities that publish a leasing address, which signals they handle inbound enquiries by email |
| Tenant screening providers | Reach independent operators who do not yet run a screening workflow |
| Smart-lock and IoT installers | Prospect apartment communities in a metro before a trade show or regional launch |
| Renovation and turn suppliers | Build a supplier outreach list for make-ready, flooring, paint and appliance work |
| Maintenance and landscaping contractors | Assemble a route-shaped territory list around a single submarket |
| Multifamily marketing agencies | Prospect communities whose listings look under-marketed, then pitch creative and paid media |
| Insurance brokers | Reach landlords and small operators for multifamily and landlord policies |
| Market researchers | Sample how contact publishing differs across metros and property tiers |

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

Everything the Apartments.com Email Scraper collects is already published on public web pages and indexed by Google. That does not remove your obligations as the sender.

Leasing offices publish contact addresses on purpose, so the Apartments.com Email Scraper is a discovery tool for inbound-friendly business contacts rather than a way around anyone's privacy setting.

Under GDPR and similar regimes, have a lawful basis for processing business contact data, honour deletion and objection requests, and say clearly 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 here. When you write to leasing offices, 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 own campaign against your jurisdiction's rules, and verify addresses before you send at volume.

### Limitations of the Apartments.com Email Scraper

- **Handle resolution is weak on this platform.** Apartments.com indexes property listing pages rather than manager profiles, so rows carry a leasing email without a resolvable handle. Expect `username: null` and `profileUrl: ""` on most or all rows.
- It only finds contacts whose email is publicly visible in Google's index. An address behind a contact form or rendered in an image will not be found.
- Google caps a single query at roughly 300 results. Query expansion exists to work around that ceiling, not to remove it.
- `username` and `profileUrl` are only populated when the platform exposes a handle in Google's result. This is a Google limitation, not a defect in the Actor.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the email. Verify those rows before sending.
- The Apify GOOGLE_SERP proxy is required. The Actor 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 Apartments.com Email Scraper is not affiliated with or endorsed by Apartments.com.

Treat the Apartments.com Email Scraper as a discovery layer that surfaces candidates fast, then verify before you send.

### Apartments.com Email Scraper FAQ

#### How many results should I expect from the Apartments.com Email Scraper?

In a measured run against live Google, roughly ten parsed result blocks yielded nine unique emails and zero resolvable profile URLs. Email volume is strong; identity data is not. Actual counts depend on your city, keywords and domain filter.

#### Why is `username` null on nearly every row?

Because Apartments.com indexes property listing pages rather than manager profiles, so rows carry a leasing email without a resolvable handle. Google shows a property title, not an account handle, so there is nothing to resolve.

#### Does the Apartments.com Email Scraper log into Apartments.com?

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

#### Which input matters most?

`location`. Apartment marketing is local, so a metro or submarket phrase does more for list quality than any other single setting.

#### Can I collect corporate emails instead of free-mail addresses?

Yes. Replace `customDomains` with the domains you want. Only emails ending in one of those domains are kept.

#### What does `possiblyTruncated` mean?

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

#### Why does the Apartments.com Email Scraper run so many queries?

Google caps one query at about 300 results. Expansion spreads your search across base, quoted, `intitle:` and modifier variants so you reach past that cap.

#### Can I run the Apartments.com Email Scraper outside Apify?

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

#### Does the Apartments.com Email Scraper return duplicate addresses?

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

#### Is 100 emails a hard limit?

Only on free plans. Paid plans are uncapped, though the real ceiling is what Google has indexed for your query set.

#### Which sibling Actor should I add for better identity data?

[ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) and [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) resolved a handle and profile URL for every parsed result in the same test, so they complement the Apartments.com Email Scraper well.

#### Does the run resume if it migrates?

Yes. State is saved in the key-value store keyed by a hash of your input, and saves also fire on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

#### Will a Google layout change break it?

It should degrade rather than fail. Parsing is structural rather than class-name based, and a whole-page fallback parser still returns emails without account details.

### Related Actors

| Actor | What it collects |
|---|---|
| [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 |
| [Apartments.com Phone Number Scraper](https://apify.com/neuro-scraper/apartments-com-phone-number-scraper) | Public phone numbers from Apartments.com |
| [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 |
| [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 |
| [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 |
| [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 Apartments.com 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 Apartments.com Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

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

Search terms describing the Apartments.com 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 Apartments.com.

## `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 Apartments.com 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/apartments-com-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/apartments-com-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/apartments-com-email-scraper --silent --output-dataset

```

## MCP server setup

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