# Redfin Rentals Email Scraper (`leads-scraper/redfin-rentals-email-scraper`) Actor

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

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

### Redfin Rentals Email Scraper - the highest email volume in this rental batch

The Redfin Rentals Email Scraper extracts publicly indexed rental contact emails from Redfin and writes them to an Apify dataset. It is built for proptech vendors, multifamily marketing agencies and suppliers who sell into rental housing.

On raw volume this is the strongest Actor in the batch. In a run against live Google, roughly ten parsed result blocks produced eleven unique emails, along with six identities and six resolvable profile URLs.

More than one email per parsed block is unusual, and it is why the Redfin Rentals Email Scraper is the right first call when you need list size. Identity coverage is decent but not the best here.

There is one mechanism you should understand before running it, because Redfin is a general-purpose real estate domain that carries sale listings alongside rentals.

If you need named accounts rather than sheer volume, pair the Redfin Rentals Email Scraper with the [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) or the [Rent.com Email Scraper](https://apify.com/leads-scraper/rent-com-email-scraper) in the same metro.

#### Why the Redfin Rentals Email Scraper adds an `inurl:` filter

Redfin's domain covers homes for sale, agent pages and rentals in one index. A plain `site:redfin.com` query would return a majority of for-sale content, which is not what you are prospecting.

So the Redfin Rentals Email Scraper appends `inurl:apartments-for-rent` to every query it builds. A typical query looks like `site:redfin.com property manager inurl:apartments-for-rent "@gmail.com" "Denver"`.

Be clear about what that does and does not do. It is a heuristic URL filter that strongly biases results toward rental pages; it is not a guarantee that every returned page is a rental page.

Occasionally a page whose URL contains that fragment will not be the rental listing you expected, and occasionally a genuine rental page will be excluded because its URL is shaped differently. Spot-check `url` and `title` before a large send.

#### Who the Redfin Rentals 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 address is published on the listing.

Renovation and turn suppliers, landscaping firms and maintenance contractors use the Redfin Rentals Email Scraper to build a high-volume territory list. Insurance brokers selling landlord and multifamily policies work the same rows.

Leasing offices and landlords publish these addresses on purpose because they want inbound enquiries. That makes this a B2B contact list rather than a consumer harvest.

### What the Redfin Rentals Email Scraper actually does

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

1. Reads your input: keywords, location, email domains and limits.
2. Builds Google queries with the `site:` operator against `redfin.com`, plus the `inurl:apartments-for-rent` narrowing operator described above.
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 Redfin, does not use any Redfin API, and does not open the Redfin website. There is no browser, no JavaScript rendering, no authentication and no cookies.

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

### Key features of the Redfin Rentals Email Scraper

| Feature | What it means in practice |
|---|---|
| Rental narrowing | An `inurl:apartments-for-rent` operator on every query, biasing a mixed 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. Paid plans are uncapped, subject to what Google has indexed for the Redfin Rentals Email Scraper's query set.

### How the Redfin Rentals Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. Adding the `inurl:` filter narrows the pool further, so expansion matters even more here than on a rentals-only domain.

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

Every one of those variants carries the `inurl:apartments-for-rent` fragment. The narrowing is applied consistently rather than only on the base query.

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

Leave expansion on. Turning it off on a filtered domain like this one shrinks the Redfin Rentals Email Scraper's result pool twice over.

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

`location` is the single most valuable input here, and on a high-volume Actor it is also your main tool for keeping a list workable rather than enormous.

Redfin has strong coverage in West Coast and Mountain metros, so those make good starting points: `Denver CO`, `Portland OR`, `Tucson AZ`, `Milwaukee WI`, `Pittsburgh PA`.

Because email yield is high, you can afford to go straight to a submarket without starving the run: `LoDo Denver`, `Pearl District Portland`, `Lawrenceville Pittsburgh`, `Bay View Milwaukee`.

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

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

If a submarket returns almost nothing, widen one step at a time before assuming the Redfin Rentals Email Scraper is misconfigured. On this Actor the `inurl:` filter is another reason a very narrow query can come back empty.

#### Choosing keywords and email domains

Because the `inurl:` filter already scopes the pages to rentals, inventory-shaped keywords work well. Try `apartments for rent`, `property manager`, `leasing office`, `landlord` and `management company`.

`customDomains` drives volume, and this is the Actor where the default two domains already produce plenty. Start with `@gmail.com` and `@yahoo.com` before widening.

Add `@outlook.com` and `@hotmail.com` only if you need more, or swap in a named operator's domain when working one portfolio. The Redfin Rentals Email Scraper keeps only addresses ending in a domain you listed.

### Output data from the Redfin Rentals Email Scraper

Every dataset item produced by the Redfin Rentals 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 |

The `query` field is worth keeping in your export from the Redfin Rentals Email Scraper. It shows the `inurl:` fragment that produced each row, which makes it easy to audit whether the rental narrowing behaved.

Profile URLs follow the shape `https://www.redfin.com/{username}`. Around six in ten parsed results carried one in testing; the rest return `username: null` and an empty `profileUrl`.

### Example runs with the Redfin Rentals Email Scraper

A high-volume metro run for a turn and make-ready supplier:

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

Two dataset rows, including the `inurl:` fragment in the recorded query:

```json
[
  {
    "network": "Redfin",
    "keyword": "property manager",
    "query": "site:redfin.com property manager inurl:apartments-for-rent \"@gmail.com\" \"Denver CO\"",
    "title": "Apartments for Rent in LoDo, Denver, CO | Redfin",
    "accountName": "LoDo Apartments",
    "fullName": "LoDo Apartments",
    "username": "lodo-apartments-denver-co",
    "profileUrl": "https://www.redfin.com/lodo-apartments-denver-co",
    "url": "https://www.redfin.com/lodo-apartments-denver-co",
    "description": "Property manager contact: lodoapartments@gmail.com. Tours available weekdays.",
    "email": "lodoapartments@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T16:03:27Z"
  },
  {
    "network": "Redfin",
    "keyword": "apartments for rent",
    "query": "site:redfin.com apartments for rent inurl:apartments-for-rent leasing office \"@yahoo.com\" \"Denver CO\"",
    "title": "Cherry Creek Apartments for Rent - Denver, CO | Redfin",
    "accountName": "Cherry Creek Rentals",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Leasing office: cherrycreekleasing@yahoo.com. Availability updated daily.",
    "email": "cherrycreekleasing@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T16:07:11Z"
  }
]
```

Because the Redfin Rentals Email Scraper often finds several addresses inside one result block, expect the dataset to grow faster than the number of pages fetched would suggest.

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

### Use cases for the Redfin Rentals Email Scraper

| Audience | How they use the Redfin Rentals Email Scraper |
|---|---|
| Property management software vendors | Build a large metro pipeline quickly, then qualify down |
| Leasing and tour-scheduling tools | Target rentals that already publish an address and field enquiries by email |
| Tenant screening providers | Reach landlords and small operators at volume across a state |
| Smart-lock and IoT installers | Prospect rental buildings across a metro before a regional rollout |
| Renovation and turn suppliers | Build the largest make-ready and flooring outreach list in this family |
| Maintenance and landscaping contractors | Assemble a dense route list for one submarket |
| Multifamily marketing agencies | Run a volume-first discovery pass, then shortlist by property |
| Insurance brokers | Reach landlords and operators for landlord and rental property policies |
| Market researchers | Sample rental contact publishing on a mixed sale-and-rental portal |

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

Everything the Redfin Rentals Email Scraper collects is already published on public pages and indexed by Google. High volume makes disciplined sending more important, not less.

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

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

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

### Limitations of the Redfin Rentals Email Scraper

- **The rental narrowing is a heuristic.** `inurl:apartments-for-rent` biases results toward rental pages on a mixed sale-and-rental domain, but it 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. 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; the `inurl:` filter narrows the pool further.
- `username` and `profileUrl` are only populated when the platform exposes a handle in Google's result. About six in ten parsed results carried one in testing. 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 Redfin Rentals Email Scraper cannot run without Apify proxy credentials.
- Free Apify plans stop at 100 emails per run, which this Actor will reach quickly; paid plans are uncapped.
- Results vary with keywords, domains and location. No volume is guaranteed, and the Redfin Rentals Email Scraper is not affiliated with or endorsed by Redfin.

### Redfin Rentals Email Scraper FAQ

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

In a measured run against live Google, roughly ten parsed result blocks produced eleven unique emails, six identities and six profile URLs - the best email volume in this batch. Counts vary with location, keywords and domain filter.

#### Why does every query contain `inurl:apartments-for-rent`?

Because redfin.com carries sale listings, agent pages and rentals in one index. The fragment biases the result set toward rental pages. It is a heuristic filter, not a guarantee.

#### Could a non-rental page still slip through?

Yes. A page whose URL contains that fragment may not be the rental listing you expect, and some genuine rental pages will be missed. Spot-check `url` and `title` before a large send.

#### Does the Redfin Rentals Email Scraper log into Redfin?

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

#### Which input matters most?

`location`. On a high-volume Actor it is what keeps the list workable, and a submarket phrase is affordable here in a way it is not on thinner platforms.

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

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

#### What does `possiblyTruncated` mean?

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

#### Why does the Redfin Rentals Email Scraper run so many queries?

Google caps a single query at about 300 results and the `inurl:` filter narrows the pool further, so expansion across base, quoted, `intitle:` and modifier variants is how the Actor reaches useful depth.

#### Can I run the Redfin Rentals Email Scraper outside Apify?

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

#### Will I hit the free-plan cap quickly?

Probably. At eleven emails per ten parsed blocks, the 100-email free-plan cap arrives fast. Paid plans are uncapped.

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

[ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) and [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) add the account-shaped rows the Redfin Rentals Email Scraper produces less consistently.

#### 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 |
|---|---|
| [Redfin Email and Phone Number Scraper](https://apify.com/leads-scraper/redfin-rentals-email-and-phone-number-scraper) | Emails and phone numbers from Redfin |
| [Redfin Phone Number Scraper](https://apify.com/leads-scraper/redfin-rentals-phone-number-scraper) | Public phone numbers from Redfin |
| [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) | Public contact emails from Apartment List |
| [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) | Public contact emails from ApartmentFinder |
| [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) | Public contact emails from Apartments.com |
| [Century 21 Agent Email Scraper](https://apify.com/neuro-scraper/century-21-agent-email-scraper) | Public contact emails from Century 21 |
| [Coldwell Banker Agent Email Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-scraper) | Public contact emails from Coldwell Banker |
| [CommercialCafe Email Scraper](https://apify.com/neuro-scraper/commercialcafe-email-scraper) | Public contact emails from CommercialCafe |
| [CommercialSearch Email Scraper](https://apify.com/neuro-scraper/commercialsearch-email-scraper) | Public contact emails from CommercialSearch |
| [Compass Agent Email Scraper](https://apify.com/neuro-scraper/compass-agent-email-scraper) | Public contact emails from Compass |
| [Crexi Email Scraper](https://apify.com/leads-scraper/crexi-email-scraper) | Public contact emails from Crexi |
| [Domain Agents Email Scraper](https://apify.com/leads-scraper/domain-agents-email-scraper) | Public contact emails from Domain |
| [Homes & Land Email Scraper](https://apify.com/neuro-scraper/homes-and-land-email-scraper) | Public contact emails from Homes & Land |
| [Homes.com Email Scraper](https://apify.com/leads-scraper/homes-com-email-scraper) | Public contact emails from Homes.com |
| [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) | Public contact emails from HotPads |
| [Keller Williams Agent Email Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-scraper) | Public contact emails from Keller Williams |
| [Land And Farm Email Scraper](https://apify.com/leads-scraper/land-and-farm-email-scraper) | Public contact emails from Land And Farm |
| [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) | Public contact emails from Land.com |
| [LandWatch Email Scraper](https://apify.com/leads-scraper/landwatch-email-scraper) | Public contact emails from LandWatch |
| [LoopNet Email Scraper](https://apify.com/leads-scraper/loopnet-email-scraper) | Public contact emails from LoopNet |
| [OnTheMarket Email Scraper](https://apify.com/leads-scraper/onthemarket-email-scraper) | Public contact emails from OnTheMarket |
| [RealEstate.com.au Agents Email Scraper](https://apify.com/neuro-scraper/realestate-com-au-agents-email-scraper) | Public contact emails from realestate.com.au |
| [Realtor.ca Email Scraper](https://apify.com/leads-scraper/realtor-ca-email-scraper) | Public contact emails from Realtor.ca |
| [Realtor.com Rentals Email Scraper](https://apify.com/leads-scraper/realtor-com-rentals-email-scraper) | Public contact emails from Realtor.com |
| [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 Redfin 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 Redfin Rentals Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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 Redfin 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/redfin-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/redfin-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/redfin-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/redfin-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/cMwanG37yhxs1gELK/builds/dqwLdbt9bKG0f5okp/openapi.json