# Realtor.com Rentals Email Scraper (`leads-scraper/realtor-com-rentals-email-scraper`) Actor

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

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

### Realtor.com Rentals Email Scraper - read this before you run it

The Realtor.com Rentals Email Scraper searches Google's public index of Realtor.com for rental contact emails and writes any it finds to an Apify dataset. Before anything else, here is the honest position.

Realtor.com blocks most of its rental index from search engines, so this Actor returns very little; try the [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper), [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) or [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) instead.

In a measured run against live Google, the Realtor.com Rentals Email Scraper returned a single parsed result block and zero emails. Not few - zero.

We are publishing the Realtor.com Rentals Email Scraper for completeness of the rental portal set, and because search indexes change over time. But you should expect an empty or near-empty dataset today, and you should plan your campaign around one of the siblings above.

Nothing in this page is a workaround for that. The Realtor.com Rentals Email Scraper cannot read pages Google has not indexed, and no combination of keywords, domains or location settings changes that.

#### When the Realtor.com Rentals Email Scraper is still worth running

If you are running a full sweep of every US rental portal and want Realtor.com covered for audit completeness, run it and accept that the result may be nothing.

If you want to periodically check whether Realtor.com's rental index has opened up, a small run with a low `maxEmails` is a cheap probe.

If you need leads today, use a different Actor. That is the honest recommendation for the Realtor.com Rentals Email Scraper, and it is the same one the yield note in its own configuration gives.

#### Who would use the Realtor.com Rentals Email Scraper if it yielded

The intended audience matches the rest of this family: proptech vendors selling property management software, leasing tools, tenant screening and smart-lock or IoT hardware.

Alongside them, multifamily marketing agencies, renovation and maintenance suppliers, and insurance brokers selling landlord policies. Leasing offices publish contact addresses on purpose, which is what makes this category viable in general.

It is simply that Realtor.com, unlike its peers, keeps most of that rental content out of the public search index. The Realtor.com Rentals Email Scraper inherits that constraint directly.

### What the Realtor.com Rentals Email Scraper actually does

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

1. Reads your input: keywords, location, email domains and limits.
2. Builds Google queries with the `site:` operator against `realtor.com`, plus the `inurl:apartments` narrowing operator described below.
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 any lead to the Apify dataset immediately.

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

Everything the Realtor.com Rentals Email Scraper could return comes from publicly indexed Google search results. When the platform keeps those pages out of the index, there is nothing for the Actor to parse.

#### Why the Realtor.com Rentals Email Scraper adds an `inurl:` filter

Realtor.com is a general-purpose real estate domain carrying for-sale listings, agent pages and rentals in one index. A plain `site:realtor.com` query would return mostly for-sale content.

So the Realtor.com Rentals Email Scraper appends `inurl:apartments` to every query. A typical query looks like `site:realtor.com property manager inurl:apartments "@gmail.com" "Phoenix"`.

That is a heuristic URL filter which biases results toward rental pages. It is not a guarantee that every returned page is a rental page, and it may exclude rental pages whose URLs are shaped differently.

On this platform the filter compounds an already thin index. Removing it would let the Realtor.com Rentals Email Scraper return more results, but they would overwhelmingly be for-sale pages rather than rental leads.

### Key features of the Realtor.com Rentals Email Scraper

The engine inside the Realtor.com Rentals Email Scraper is identical to the rest of this Actor family. It is capable; the input data on this platform is not.

| Feature | What it means in practice |
|---|---|
| Rental narrowing | An `inurl:apartments` operator on every query, biasing a mixed sale-and-rental domain toward rental pages. |
| 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. Running the Realtor.com Rentals Email Scraper, you are very unlikely to approach that cap.

### How the Realtor.com Rentals Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. Here the constraint is the opposite problem: there is very little indexed content to reach.

With `expandQueries` on, each keyword and email-domain pair is searched in several phrasings. The Realtor.com Rentals 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`. Leave expansion on - on a thin index, breadth is the only lever you have.

The run summary in the log is genuinely useful on the Realtor.com Rentals Email Scraper. Pages fetched with zero emails per page tells you the index is empty, not that something is misconfigured.

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

`location` is normally the most valuable input in this schema, and it still is here - but the advice runs the opposite way to every sibling Actor.

Do not narrow. On a platform this thin, a submarket phrase such as `Roosevelt Row Phoenix` will almost certainly return nothing at all.

Start with a large metro or leave `location` empty entirely: `Phoenix AZ`, `Chicago IL`, `Atlanta GA`, `Dallas TX`, `New York NY`. If a national run returns nothing, a city run will not save it.

Run one location per run. The value is appended verbatim to every query, so `Phoenix OR Tucson` becomes a literal phrase and returns even less.

Set `countryCode: "US"` so the proxy resolves from a US exit. Beyond that, location tuning has limited power against an index that is largely closed.

Treat an empty result from the Realtor.com Rentals Email Scraper as information about Realtor.com, not as a misconfiguration to debug.

#### Choosing keywords and email domains

Widen everything. Use several keywords - `property manager`, `apartments for rent`, `leasing office`, `landlord`, `management company` - rather than one precise term.

Widen `customDomains` too: `@gmail.com`, `@yahoo.com`, `@outlook.com` and `@hotmail.com` together. The Realtor.com Rentals Email Scraper keeps only addresses ending in a domain you listed, so a short list guarantees a short dataset.

Even with everything widened, expect little from the Realtor.com Rentals Email Scraper. That is the platform, not the settings.

### Output data from the Realtor.com Rentals Email Scraper

If the Realtor.com Rentals Email Scraper does find something, every dataset item 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 exists the profile URL would follow the shape `https://www.realtor.com/{username}`. In testing no row carried one, because no rows were produced at all.

### Example runs with the Realtor.com Rentals Email Scraper

A deliberately wide probe run - many keywords, many domains, no narrow location:

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

The measured result of a run like this was an empty dataset. The row below is illustrative - it shows the shape a result would take if the index ever exposes one, not something the Actor returned in testing:

```json
[
  {
    "network": "Realtor.com",
    "keyword": "property manager",
    "query": "site:realtor.com property manager inurl:apartments \"@gmail.com\" \"Phoenix AZ\"",
    "title": "Apartments for Rent in Phoenix, AZ | Realtor.com",
    "accountName": "Phoenix Apartments",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Leasing contact: examplephxleasing@gmail.com",
    "email": "examplephxleasing@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T18:00:00Z"
  }
]
```

We would rather show you an honest empty result and an illustrative schema than imply a yield the Realtor.com Rentals Email Scraper does not currently deliver.

If that row shape is what you actually need, run the Realtor.com Rentals Email Scraper's siblings instead - they return it reliably today.

### Use cases for the Realtor.com Rentals Email Scraper

| Audience | Realistic expectation |
|---|---|
| Proptech vendors | Coverage completeness only; use a sibling Actor for actual pipeline |
| Multifamily marketing agencies | Not a viable primary source today |
| Tenant screening providers | Not a viable primary source today |
| Smart-lock and IoT installers | Not a viable primary source today |
| Renovation and maintenance suppliers | Not a viable primary source today |
| Insurance brokers | Not a viable primary source today |
| Data and market researchers | Useful as evidence of how closed Realtor.com's rental index is |
| Audit and compliance teams | Documents that a portal was checked and returned nothing |
| Periodic monitoring | A cheap recurring probe for whether the index opens up |

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

Anything the Realtor.com Rentals Email Scraper collects would already be published on public 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 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. The Realtor.com Rentals Email Scraper surfaces candidates; the sending decision stays with you.

### Limitations of the Realtor.com Rentals Email Scraper

- **Realtor.com blocks most of its rental index from search engines, so this Actor returns very little.** Try the Apartments.com, Zumper or ApartmentFinder Actors instead. A measured run produced one parsed result block and zero emails.
- **The rental narrowing is a heuristic.** `inurl:apartments` biases results toward rental pages but does not guarantee every returned page is a rental page, and it may exclude rental pages whose URLs are shaped differently.
- It only finds contacts whose email is publicly visible in Google's index. If the platform keeps pages out of that index, there is nothing to find.
- Google caps a single query at roughly 300 results. That ceiling is not the binding constraint here; index coverage is.
- `username` and `profileUrl` are only populated when the platform exposes a handle in Google's result. This 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 Realtor.com Rentals Email Scraper cannot run without Apify proxy credentials.
- Free Apify plans stop at 100 emails per run; you are unlikely to reach that here.
- Results vary and no volume is guaranteed. The Realtor.com Rentals Email Scraper is not affiliated with or endorsed by Realtor.com.

### Realtor.com Rentals Email Scraper FAQ

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

Very few, quite possibly none. In a measured run against live Google it returned a single parsed result block and zero emails. Plan on an empty dataset and use a sibling Actor for real pipeline.

#### Why is the yield this low?

Realtor.com blocks most of its rental index from search engines. The Actor can only read what Google has indexed, and for Realtor.com rentals that is almost nothing.

#### Which Actor should I use instead?

[Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) for email volume, [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) or [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) for account-shaped rows with profile links.

#### Is the Realtor.com Rentals Email Scraper broken?

No. The same engine returns eleven unique emails per ten parsed blocks on Redfin rentals. The difference is index coverage, not code.

#### Why does every query contain `inurl:apartments`?

Because realtor.com carries for-sale listings, agent pages and rentals in one index. The fragment biases results toward rental pages. It is a heuristic, not a guarantee.

#### Would removing the `inurl:` filter help?

It would return more results, but they would overwhelmingly be for-sale pages rather than rental leads. The filter is not what makes the rental yield thin.

#### Which input matters most?

`location` - but inverted. Do not narrow it. Start with a large metro or leave it empty; a submarket phrase on this Actor reliably returns nothing.

#### Does the Realtor.com Rentals Email Scraper log into Realtor.com?

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

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

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

#### What does `possiblyTruncated` mean?

Google cut the snippet near the email, so the address may be incomplete. Verify those rows before sending.

#### Is it worth running at all?

As a completeness check or a periodic probe of whether the index has opened, yes. As a primary lead source, no.

#### 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 |
|---|---|
| [Realtor.com Email and Phone Number Scraper](https://apify.com/leads-scraper/realtor-com-rentals-email-and-phone-number-scraper) | Emails and phone numbers from Realtor.com |
| [Realtor.com Phone Number Scraper](https://apify.com/leads-scraper/realtor-com-rentals-phone-number-scraper) | Public phone numbers from Realtor.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 |
| [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 |
| [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 |
| [Apartments.com Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartments-com-email-and-phone-number-scraper) | Emails and phone numbers from Apartments.com |
| [Century 21 Email and Phone Number Scraper](https://apify.com/neuro-scraper/century-21-agent-email-and-phone-number-scraper) | Emails and phone numbers from Century 21 |
| [Coldwell Banker Email and Phone Number Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-and-phone-number-scraper) | Emails and phone numbers from Coldwell Banker |
| [CommercialCafe Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialcafe-email-and-phone-number-scraper) | Emails and phone numbers from CommercialCafe |
| [CommercialSearch Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialsearch-email-and-phone-number-scraper) | Emails and phone numbers from CommercialSearch |
| [Compass Email and Phone Number Scraper](https://apify.com/neuro-scraper/compass-agent-email-and-phone-number-scraper) | Emails and phone numbers from Compass |
| [Crexi Email and Phone Number Scraper](https://apify.com/leads-scraper/crexi-email-and-phone-number-scraper) | Emails and phone numbers from Crexi |
| [Domain Email and Phone Number Scraper](https://apify.com/leads-scraper/domain-agents-email-and-phone-number-scraper) | Emails and phone numbers from Domain |
| [Homes & Land Email and Phone Number Scraper](https://apify.com/neuro-scraper/homes-and-land-email-and-phone-number-scraper) | Emails and phone numbers from Homes & Land |
| [Homes.com Email and Phone Number Scraper](https://apify.com/leads-scraper/homes-com-email-and-phone-number-scraper) | Emails and phone numbers from Homes.com |
| [Keller Williams Email and Phone Number Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-and-phone-number-scraper) | Emails and phone numbers from Keller Williams |

### Leave a review

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

# Actor input Schema

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

Search terms describing the Realtor.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 Realtor.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 Realtor.com Rentals 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/realtor-com-rentals-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/realtor-com-rentals-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/realtor-com-rentals-email-scraper --silent --output-dataset

```

## MCP server setup

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