# ApartmentFinder Email Scraper (`leads-scraper/apartmentfinder-email-scraper`) Actor

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

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

### ApartmentFinder Email Scraper - the strongest identity yield in this rental batch

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

Of the ten rental portals in this family, ApartmentFinder measured best on identity data. In a run against live Google, roughly ten parsed result blocks produced ten identities, ten resolvable profile URLs and seven unique emails.

That ratio is what makes the ApartmentFinder Email Scraper worth reaching for first. You get fewer raw addresses than a pure volume portal, but almost every row arrives with an account name and a usable link.

For a CRM import, that matters more than headline count. A row with `accountName`, `username` and `profileUrl` filled in can be deduplicated, enriched and assigned to a rep; a bare address cannot.

If you need sheer email volume alongside it, run the ApartmentFinder Email Scraper first for structured accounts, then top up with the [Redfin Rentals Email Scraper](https://apify.com/leads-scraper/redfin-rentals-email-scraper) or the [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper).

#### Who the ApartmentFinder 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 whose contact address appears on the listing.

Renovation, turn and make-ready suppliers, landscaping firms and maintenance contractors use the ApartmentFinder Email Scraper to build a route-shaped territory list. Insurance brokers selling landlord and multifamily policies work the same rows.

Leasing offices publish those addresses on purpose because they want inbound enquiries. This is a B2B contact list, not a consumer harvest - but it still deserves careful, compliant outreach.

Sales operations teams also use the ApartmentFinder Email Scraper as an enrichment source, matching new rows against an existing account list on property name and profile link.

### What the ApartmentFinder Email Scraper actually does

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

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

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

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

### How the ApartmentFinder Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. A single query against a national rental network would leave most of the index untouched.

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

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

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

Unlike the general-purpose portals in this family, ApartmentFinder is rentals-only, so the ApartmentFinder Email Scraper needs no extra `inurl:` filter to keep sale listings out. Every indexed page is already a rental page.

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

`location` is the most valuable field in the schema. Multifamily is a local business, and an untargeted national sweep produces a list nobody can actually work.

ApartmentFinder has particularly usable depth in secondary and tertiary metros, so this is a good Actor for markets the big portals under-serve: `Columbus OH`, `Louisville KY`, `Tulsa OK`, `Greenville SC`, `Boise ID`.

For dense urban runs, use a submarket rather than a metro: `Wicker Park Chicago`, `Midtown Atlanta`, `Capitol Hill Denver`, `Oak Lawn Dallas`. Fewer rows, far better territory fit.

Run one location per run. `location` is appended verbatim to every query, so `Columbus OR Cincinnati` becomes a literal phrase and typically returns less, not more.

Pair `location` with `countryCode: "US"` so the search proxy resolves from a US exit. Add the state abbreviation when a city name is ambiguous - `Springfield IL` and `Springfield MO` are unrelated rental markets.

If a location returns almost nothing, widen one step at a time, suburb to metro to state, before concluding the ApartmentFinder Email Scraper is misconfigured.

#### Choosing keywords and email domains

Role-shaped keywords tend to beat inventory-shaped ones on this platform. Try `leasing consultant`, `community manager`, `regional manager`, `management company` or `apartment community` alongside the defaults.

`customDomains` controls volume more than anything else. Free-mail domains are the default because independent operators and small management companies genuinely publish `@gmail.com` and `@yahoo.com` addresses.

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

### Output data from the ApartmentFinder Email Scraper

Every dataset item produced by the ApartmentFinder 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.apartmentfinder.com/{username}`. Because this platform exposes handles reliably, most rows from the ApartmentFinder Email Scraper arrive with both `username` and `profileUrl` populated.

### Example runs with the ApartmentFinder Email Scraper

A secondary-market run for a property management software vendor:

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

Two representative dataset rows:

```json
[
  {
    "network": "ApartmentFinder",
    "keyword": "property manager",
    "query": "site:apartmentfinder.com property manager \"@gmail.com\" \"Columbus OH\"",
    "title": "Maple Row Apartments - Columbus, OH | ApartmentFinder",
    "accountName": "Maple Row Apartments",
    "fullName": "Maple Row Apartments",
    "username": "maple-row-columbus-oh",
    "profileUrl": "https://www.apartmentfinder.com/maple-row-columbus-oh",
    "url": "https://www.apartmentfinder.com/maple-row-columbus-oh",
    "description": "On-site property manager. Tours and availability: maplerowleasing@gmail.com",
    "email": "maplerowleasing@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:02:18Z"
  },
  {
    "network": "ApartmentFinder",
    "keyword": "community manager",
    "query": "site:apartmentfinder.com community manager contact \"@yahoo.com\" \"Columbus OH\"",
    "title": "Northgate Commons - Apartments for Rent | ApartmentFinder",
    "accountName": "Northgate Commons",
    "fullName": "Northgate Commons",
    "username": "northgate-commons-columbus-oh",
    "profileUrl": "https://www.apartmentfinder.com/northgate-commons-columbus-oh",
    "url": "https://www.apartmentfinder.com/northgate-commons-columbus-oh",
    "description": "Leasing office contact: northgatecommons@yahoo.com. Ask about current specials.",
    "email": "northgatecommons@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:05:44Z"
  }
]
```

Rows like these drop straight into a CRM. The profile link gives a rep something to check before writing, which is exactly why the ApartmentFinder Email Scraper is the recommended starting point in this batch.

For a broader sweep, drop `location` to a state, raise `maxEmails`, and let the ApartmentFinder Email Scraper work through the expanded query set. Leave `maxConcurrency` at 5 unless you have a reason to change it.

### Use cases for the ApartmentFinder Email Scraper

| Audience | How they use the ApartmentFinder Email Scraper |
|---|---|
| Property management software vendors | Build a metro-by-metro demo pipeline with profile links attached for pre-call research |
| Leasing and tour-scheduling tools | Target communities that publish a leasing address and already handle enquiries by email |
| Tenant screening providers | Reach independent operators in secondary markets who lack a screening workflow |
| Smart-lock and IoT installers | Prospect apartment communities in a metro ahead of a regional launch or trade show |
| Renovation and turn suppliers | Assemble a make-ready, flooring and appliance outreach list per submarket |
| Maintenance and landscaping contractors | Build a route-shaped territory list around one submarket |
| Multifamily marketing agencies | Shortlist under-marketed communities, 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 ApartmentFinder Email Scraper collects is already published on public web pages and indexed by Google. That does not remove your obligations as the sender.

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 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 sending at volume. The ApartmentFinder Email Scraper surfaces candidates; the sending decision stays yours.

### Limitations of the ApartmentFinder 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. ApartmentFinder is strong here, but individual rows can still come back with `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 ApartmentFinder 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 ApartmentFinder Email Scraper is not affiliated with or endorsed by ApartmentFinder.

### ApartmentFinder Email Scraper FAQ

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

In a measured run against live Google, roughly ten parsed result blocks produced ten identities, ten profile URLs and seven unique emails - the best identity resolution in this batch. Your counts will vary with location, keywords and domain filter.

#### Why is the identity yield higher here than on Apartments.com?

Google surfaces ApartmentFinder pages with handle-shaped URLs and account-style titles, so there is something to resolve. On Apartments.com the indexed pages are listing pages without a resolvable handle.

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

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 or submarket phrase does more for list quality than any other setting in the ApartmentFinder Email Scraper.

#### 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 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 adding them to a send.

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

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

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

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

#### Does it return 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.

#### Which sibling Actor pairs best with this one?

[Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) measured almost identically on identity, and [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) adds raw email volume where handles are scarce.

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

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

### Related Actors

| Actor | What it collects |
|---|---|
| [ApartmentFinder Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartmentfinder-email-and-phone-number-scraper) | Emails and phone numbers from ApartmentFinder |
| [ApartmentFinder Phone Number Scraper](https://apify.com/neuro-scraper/apartmentfinder-phone-number-scraper) | Public phone numbers from ApartmentFinder |
| [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) | Public contact emails from Apartment List |
| [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 |
| [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 |
| [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 ApartmentFinder 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 ApartmentFinder Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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 ApartmentFinder 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/apartmentfinder-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/apartmentfinder-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/apartmentfinder-email-scraper --silent --output-dataset

```

## MCP server setup

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