# RentCafe Email Scraper (`leads-scraper/rentcafe-email-scraper`) Actor

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

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

### RentCafe Email Scraper - leasing addresses from property and city pages

The RentCafe Email Scraper collects publicly indexed leasing contact emails from RentCafe and writes them to an Apify dataset. It is built for proptech vendors, multifamily marketing agencies and suppliers selling into apartment communities.

Start with the honest part. RentCafe indexes property and city pages rather than manager profiles, so rows carry a leasing email without a resolvable handle.

In a measured run against live Google, roughly ten parsed result blocks produced seven unique emails and zero rows with a usable `username` or `profileUrl`. The RentCafe Email Scraper finds addresses well; it cannot manufacture account handles Google never shows.

That shape suits list building more than account enrichment. If you want profile links attached to every row, the [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) and the [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) resolved one for every parsed result in the same test.

#### Who the RentCafe 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 appears on the listing.

Renovation and turn suppliers, landscaping firms and maintenance contractors use the RentCafe Email Scraper to build a workable metro or submarket territory. Insurance brokers selling landlord and multifamily policies work the same rows.

Leasing offices publish these addresses deliberately, because inbound enquiries are the point of the listing. That makes this a B2B contact list rather than a consumer harvest.

Teams that run city-by-city campaigns tend to get the most out of the RentCafe Email Scraper, because the platform's indexed pages are themselves organised by city.

### What the RentCafe Email Scraper actually does

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

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

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

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

### How the RentCafe 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 marketplace leaves most of the index untouched.

With `expandQueries` on, each keyword and email-domain pair is searched in several phrasings. The RentCafe 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`. Those are the words that sit next to a published address on a property or city page.

Because RentCafe indexes city-level roundup pages as well as individual properties, expansion matters more here than on a profile-shaped platform. Different phrasings surface genuinely different page types.

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

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

`location` is the highest-leverage input in the schema, and it matters even more on a platform whose indexed pages are organised by city.

Because RentCafe surfaces city roundup pages, a plain metro name works unusually well here: `Philadelphia PA`, `Baltimore MD`, `Denver CO`, `Kansas City MO`, `Minneapolis MN`.

Submarket phrases still sharpen the result when a metro is too broad: `Fishtown Philadelphia`, `Canton Baltimore`, `RiNo Denver`, `Uptown Minneapolis`. Fewer rows, tighter territory.

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 include state abbreviations when a city name is ambiguous - `Kansas City MO` and `Kansas City KS` are separate rental markets.

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

#### Choosing keywords and email domains

Because the indexed pages are property and city pages, inventory-shaped keywords work as well as role-shaped ones here. Try `apartments for rent`, `apartment community`, `leasing office`, `management company` and `community manager`.

`customDomains` drives volume more than any other field. Free-mail domains are the default because independent operators and smaller management companies genuinely publish `@gmail.com` and `@yahoo.com` addresses.

Add `@outlook.com` and `@hotmail.com` for coverage, or a named operator domain when working a single portfolio. The RentCafe Email Scraper keeps only addresses ending in a domain you listed.

### Output data from the RentCafe Email Scraper

Every dataset item produced by the RentCafe Email Scraper carries all fourteen fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for listing-style titles |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, for example `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

When a handle is available the profile URL follows the shape `https://www.rentcafe.com/{username}`. On this platform that is the exception, not the rule, so plan your pipeline around `email`, `accountName` and `description`.

### Example runs with the RentCafe Email Scraper

A metro run for a multifamily marketing agency prospecting Philadelphia:

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

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

```json
[
  {
    "network": "RentCafe",
    "keyword": "property manager",
    "query": "site:rentcafe.com property manager \"@gmail.com\" \"Philadelphia PA\"",
    "title": "Spring Garden Lofts - Philadelphia, PA | RentCafe",
    "accountName": "Spring Garden Lofts",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "On-site property manager. Leasing enquiries: springgardenlofts@gmail.com",
    "email": "springgardenlofts@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T12:04:11Z"
  },
  {
    "network": "RentCafe",
    "keyword": "apartments for rent",
    "query": "site:rentcafe.com apartments for rent leasing office \"@yahoo.com\" \"Philadelphia PA\"",
    "title": "Apartments for Rent in Fishtown, Philadelphia, PA | RentCafe",
    "accountName": "Fishtown Apartments",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Leasing office contact: fishtownleasing@yahoo.com. Availability updated weekly.",
    "email": "fishtownleasing@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T12:07:52Z"
  }
]
```

Note that `accountName` still carries a property or neighbourhood label. Even without a handle, the RentCafe Email Scraper hands you an address plus enough context to personalise a first message.

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

### Use cases for the RentCafe Email Scraper

| Audience | How they use the RentCafe Email Scraper |
|---|---|
| Property management software vendors | Build a city-level list of communities to demo leasing and accounting software to |
| Leasing and tour-scheduling tools | Target communities that publish an address and already field enquiries by email |
| Tenant screening providers | Reach independent operators without a formal screening workflow |
| Smart-lock and IoT installers | Prospect apartment communities in a metro before a regional rollout |
| Renovation and turn suppliers | Build a make-ready, flooring and appliance outreach list per neighbourhood |
| Maintenance and landscaping contractors | Assemble a route-shaped territory list around one part of a city |
| Multifamily marketing agencies | Shortlist communities by neighbourhood, then pitch creative and paid media |
| Insurance brokers | Reach landlords and small operators for landlord and multifamily policies |
| Market researchers | Sample how contact publishing differs between city roundups and property pages |

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

Everything the RentCafe Email Scraper collects is already published on public pages and indexed by Google. That does not shift your obligations as the sender onto anyone else.

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

Fair Housing is genuinely relevant to US rental outreach. Keep your 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 you send at volume. The RentCafe Email Scraper surfaces candidates; the sending decision remains yours.

### Limitations of the RentCafe Email Scraper

- **Handle resolution does not work on this platform.** RentCafe indexes property and city pages rather than manager profiles, so rows carry a leasing email without a resolvable handle. Expect `username: null` and `profileUrl: ""` on most or all rows.
- It only finds contacts whose email is publicly visible in Google's index. 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. This is a Google limitation, not a defect in the Actor.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the email. Verify those rows before sending.
- The Apify GOOGLE_SERP proxy is required. The RentCafe 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 RentCafe Email Scraper is not affiliated with or endorsed by RentCafe.

### RentCafe Email Scraper FAQ

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

In a measured run against live Google, roughly ten parsed result blocks produced seven unique emails and zero resolvable profile URLs. Email yield is solid; identity data is absent. Your counts will vary with location, keywords and domain filter.

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

Because RentCafe indexes property and city pages rather than manager profiles, so rows carry a leasing email without a resolvable handle. Google shows a property or neighbourhood title, not an account handle.

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

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 platform organised around city pages, the location phrase shapes the whole result set more than anything else in the RentCafe Email Scraper.

#### 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 RentCafe 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 ceiling.

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

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

#### Will I get duplicate addresses?

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

#### 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 should I pair with the RentCafe Email Scraper?

[Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) or [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) if you want profile links in the same metro, since both resolve handles that RentCafe pages do not expose.

#### 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 |
|---|---|
| [RentCafe Email and Phone Number Scraper](https://apify.com/neuro-scraper/rentcafe-email-and-phone-number-scraper) | Emails and phone numbers from RentCafe |
| [RentCafe Phone Number Scraper](https://apify.com/neuro-scraper/rentcafe-phone-number-scraper) | Public phone numbers from RentCafe |
| [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 |
| [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 |
| [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 RentCafe 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 RentCafe Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

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

```

## MCP server setup

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