# RE/MAX Agent Email Scraper (`leads-scraper/remax-agent-email-scraper`) Actor

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

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

### RE/MAX Agent Email Scraper: reaching agents who buy their own tools

The RE/MAX Agent Email Scraper collects agent contact emails that are publicly visible in Google's index alongside RE/MAX pages.
The audience angle of the RE/MAX Agent Email Scraper is what separates it from the other franchise Actors: RE/MAX agents typically operate as independent contractors who fund their own marketing, technology and lead generation.
That means the person behind the address is often the buyer, not a gatekeeper who forwards you to a corporate procurement process.

Set the yield expectation up front. RE/MAX indexes property listings far more than agent pages, so most rows carry an agent email without a resolvable profile URL.
In a measured run, roughly ten parsed result blocks produced about seven unique emails but only one row with identity data and one resolved profile URL.
The RE/MAX Agent Email Scraper is therefore an address-first tool with the weakest handle coverage of the four franchise Actors in this category.

RE/MAX agents publish contact details on listing and office pages because buyers, sellers and cooperating agents must be able to reach them directly.
The RE/MAX Agent Email Scraper reads only what Google already indexed from those public pages.
It queries `remax.com` specifically, so regional RE/MAX sites on other domains are outside its scope.

#### Who the RE/MAX Agent Email Scraper is for

Vendors selling directly to the producing agent run the RE/MAX Agent Email Scraper for personal CRM, IDX and single-agent websites, paid lead products, signage and print, and coaching.
Mortgage loan officers, title and escrow partners and closing services use it to build relationships with individual high-production agents.
Photographers, videographers, drone operators, recruiters and franchise development teams use the RE/MAX Agent Email Scraper to target agents who control their own budget.

#### What the RE/MAX Agent Email Scraper never does

The RE/MAX Agent Email Scraper never logs into RE/MAX, never uses a RE/MAX API and never opens the remax.com website.
There is no browser, no JavaScript rendering, no authentication and no cookies in the pipeline.
Every field comes from publicly indexed Google search results: titles, snippets and site labels.

### Key features of the RE/MAX Agent Email Scraper

| Feature | What it does for an agent contact database |
|---|---|
| Google `site:` targeting | Every query is scoped to `remax.com` so nothing off-brand leaks in |
| Query expansion | Base, quoted and `intitle:` phrasings plus one variant per query modifier |
| Structural parsing | Locates the `<h3>` title then the smallest surrounding block, never Google CSS class names |
| Domain-filtered extraction | Only addresses ending in your `customDomains` are kept |
| Global deduplication | One row per unique email across every query and every page |
| Email normalisation | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width at sign |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` never matches inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another address in the same block |
| Concurrency pool | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries and block detection | Up to 3 attempts per page, exponential backoff, a fresh proxy session per request, and CAPTCHA or consent pages retried rather than counted as empty |
| Requeue of failures | Blocked or failed queries are retried once at the end of the run |
| Resumable state | Stored in the key-value store keyed by a hash of your input, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Fallback parser | A Google layout change degrades the run to emails without account details, not to nothing |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

With identity data on only about one in ten parsed blocks, the `description` field is doing quiet work in a RE/MAX Agent Email Scraper run.
It often carries the market and specialty context you would otherwise have taken from a profile page, so keep it in your export.

### How the RE/MAX Agent Email Scraper works

1. The RE/MAX Agent Email Scraper reads your input: keywords, location, email domains and limits.
2. It builds Google queries with the `site:` operator, for example `site:remax.com "realtor" "@gmail.com" "Colorado Springs"`.
3. It fetches result pages through the Apify GOOGLE_SERP proxy with async `aiohttp` requests.
4. It parses each result block structurally instead of by CSS class.
5. It extracts addresses from the block text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead to the dataset immediately.

Base queries run before expanded variants, so the strongest RE/MAX results land first.
Because the RE/MAX Agent Email Scraper writes rows as it finds them, an aborted run still leaves you everything collected so far.

### Input reference for the RE/MAX Agent Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["real estate agent", "realtor"]` | 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","listing agent","inquiries","broker"]` | 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` is the highest-value input

Because handle coverage is thin, geography is how you make a RE/MAX Agent Email Scraper dataset targeted, which makes `location` the single most valuable input.
Start at metro level: `Denver`, `Colorado Springs`, `Salt Lake City`, `Kansas City`, `Omaha`, `Albuquerque`, `Boise`, `Tucson`, `Greenville`.
Then farm the suburb or neighborhood where an office concentrates: `Littleton`, `Overland Park`, `Chandler`, `Ballantyne Charlotte`, `Sandy Springs`, `Fishers Indiana`.

Write the phrase as a listing or office page prints it.
`Overland Park` beats `Overland Park, Kansas, United States`, and a suburb name usually beats a ZIP code, though a ZIP is worth a second run in dense counties.
Run one RE/MAX Agent Email Scraper job per market so you can attribute reply rates and so a single busy suburb does not consume the whole `maxEmails` budget.

#### `countryCode` guidance

Set `countryCode` to `US`, since this Actor targets `remax.com`. US routing keeps ambiguous names such as `Aurora`, `Springfield` and `Kingston` on the right pages.
If your market is Canada, note that Canadian RE/MAX inventory largely lives on a different domain that is out of scope here; [Realtor.ca Email Scraper](https://apify.com/leads-scraper/realtor-ca-email-scraper) is the better Canadian source.

#### Example input

```json
{
  "keywords": ["real estate agent", "realtor", "listing agent"],
  "location": "Colorado Springs",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com", "@aol.com"],
  "maxEmails": 400,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "listing agent", "inquiries", "broker"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

### Output reference for the RE/MAX Agent Email Scraper

Every dataset item written by the RE/MAX Agent Email Scraper carries all fourteen fields.

| 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 captions |
| `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 caption snippet, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example output

```json
[
  {
    "network": "RE/MAX",
    "keyword": "realtor",
    "query": "site:remax.com realtor \"@gmail.com\" \"Colorado Springs\"",
    "title": "Colorado Springs, CO Real Estate & Homes for Sale | RE/MAX",
    "accountName": "RE/MAX",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.remax.com/co/colorado-springs/homes-for-sale",
    "description": "Direct showing requests to the listing agent at m.eberhardt.homes@gmail.com.",
    "email": "m.eberhardt.homes@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T16:11:09Z"
  },
  {
    "network": "RE/MAX",
    "keyword": "real estate agent",
    "query": "site:remax.com \"real estate agent\" contact \"@yahoo.com\" \"Colorado Springs\"",
    "title": "Sofia Marchetti - RE/MAX Real Estate Agent",
    "accountName": "sofia-marchetti",
    "fullName": "Sofia Marchetti",
    "username": "sofia-marchetti",
    "profileUrl": "https://www.remax.com/real-estate-agents/sofia-marchetti",
    "url": "https://www.remax.com/real-estate-agents/sofia-marchetti",
    "description": "Residential and relocation specialist serving El Paso County. Contact sofia.marchetti.re@yahoo.com.",
    "email": "sofia.marchetti.re@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T16:12:31Z"
  }
]
```

The first row is overwhelmingly the common case: a usable address with `username: null` and an empty `profileUrl`.
The second is the agent-page case, which the RE/MAX Agent Email Scraper resolved on roughly one of ten parsed blocks in testing.
Treat any resolved profile link as a bonus rather than an expected field.

### Use cases for the RE/MAX Agent Email Scraper

| Use case | How the RE/MAX Agent Email Scraper fits |
|---|---|
| Selling to the individual agent | RE/MAX agents commonly fund their own tools, so the recipient is often the decision maker |
| Personal CRM and website vendors | Reach agents who buy technology for themselves rather than through a brokerage |
| Paid lead and coaching products | Target producing agents in a specific metro |
| Mortgage, title and escrow | Build direct relationships with listing agents in your closing footprint |
| Listing media services | Find agents publishing inventory in a defined suburb |
| Recruiting | Source experienced agents by market for brokerage conversations |
| Cross-brand US list building | Merge with other franchise Actors and deduplicate on `email` |

#### Example run recipes

Three RE/MAX Agent Email Scraper configurations that work well in practice.

Front Range farm: keywords `["realtor", "real estate agent"]`, location `Colorado Springs`, `countryCode` `US`, `maxEmails` 400.
Suburban Kansas City: keywords `["listing agent", "realtor"]`, location `Overland Park`, domains `["@gmail.com", "@yahoo.com", "@outlook.com"]`.
Cross-brand build: run the RE/MAX Agent Email Scraper alongside the other franchise Actors, then merge and deduplicate on `email` before import.

### Results you should realistically expect

In a measured run the RE/MAX Agent Email Scraper returned about seven unique emails per ten parsed result blocks, with identity data and a resolved profile URL on about one.
That is solid address volume with the weakest handle coverage among the franchise Actors, exactly as the yield note describes.
No volume is guaranteed, and totals move with keywords, domains, location and what Google has indexed.

If you need names and profile links on most rows, run [Keller Williams Agent Email Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-scraper) or [Coldwell Banker Agent Email Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-scraper) instead; both publish real agent profile pages.
For higher raw email density with a similar listing-heavy shape, [Century 21 Agent Email Scraper](https://apify.com/neuro-scraper/century-21-agent-email-scraper) and [Homes.com Email Scraper](https://apify.com/leads-scraper/homes-com-email-scraper) are the better choices.

### Responsible use

RE/MAX agents publish these addresses so clients and cooperating agents can reach them, so make RE/MAX Agent Email Scraper outreach a relevant business offer rather than a blast.
CAN-SPAM governs commercial email to US recipients, covering accurate headers, a physical address and an opt-out you honor promptly.
CASL applies to Canadian recipients, the Spam Act to Australian ones, and GDPR with PECR to EU and UK ones; phone and SMS follow-up bring TCPA-adjacent rules into scope.

Fair Housing law is central to US real estate outreach.
Do not use the `location` input in the RE/MAX Agent Email Scraper to include or exclude people on the basis of protected characteristics, and keep your messaging neutral.
This is not legal advice; confirm your own obligations before you send.

### Limitations of the RE/MAX Agent Email Scraper

- RE/MAX indexes property listings far more than agent pages, so most rows carry an agent email without a resolvable profile URL. This is the governing limitation, and handle coverage here is the lowest of the franchise Actors.
- The RE/MAX Agent Email Scraper only finds addresses that are publicly visible in Google's index.
- It queries `remax.com`, so regional RE/MAX sites on other domains are out of scope.
- Google caps a single query at roughly 300 results, which is why query expansion exists; keep `expandQueries` on.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the address, so verify those rows before sending.
- `username` and `profileUrl` populate only when Google exposes a handle; empty values are a Google limitation, not a bug.
- The RE/MAX Agent Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
- Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
- Results vary with keywords, domains and location, and no volume is guaranteed.

### FAQ about the RE/MAX Agent Email Scraper

#### How many results should I expect?

In a measured run the RE/MAX Agent Email Scraper returned about seven unique emails per ten parsed result blocks, with identity data on about one.
Widen keywords, domains and markets if a run finishes short of your `maxEmails` target.

#### Why is `profileUrl` empty on almost every row?

Because RE/MAX indexes property listings far more than agent pages, Google usually prints no agent handle for the Actor to build a link from.
The address is still real and usable; only the profile link is missing.

#### Does the RE/MAX Agent Email Scraper log into RE/MAX?

No. It reads publicly indexed Google results only, with no login, no API and no site visits.

#### Does the RE/MAX Agent Email Scraper cover RE/MAX outside the United States?

It queries `remax.com`. Regional RE/MAX sites on other domains are out of scope, so use a market-appropriate Actor for those countries.

#### What should I put in `location`?

A metro or suburb as a listing page prints it: `Colorado Springs`, `Overland Park`, `Chandler`, `Boise`.
Geography is your main targeting lever here, because identity data is sparse.

#### Should I set `countryCode`?

Yes, use `US`. It keeps ambiguous city names on US pages and stops the page budget leaking abroad.

#### Which email domains should I use?

Start with `@gmail.com` and `@yahoo.com`, then add `@outlook.com`, `@hotmail.com`, `@aol.com` and `@icloud.com`.
Office domains work when you already know which RE/MAX office you are targeting.

#### How do I get more emails from one RE/MAX Agent Email Scraper run?

Raise `maxEmails` above the default of 20, keep `expandQueries` on, and add keywords such as `listing agent`, `broker associate` and `buyer agent`.
Several suburb-level runs usually outperform one statewide run.

#### What does `possiblyTruncated` mean?

Google's snippet ellipsis touched the address, so it may be incomplete. Verify those rows before adding them to a sequence.

#### Can I resume an interrupted RE/MAX Agent Email Scraper run?

Yes. State lives in the key-value store keyed by a hash of your input and is saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING`.
A whole-page fallback parser also keeps the run producing emails if Google changes its markup mid-flight.

#### How do I export the data?

Download the RE/MAX Agent Email Scraper dataset as CSV, JSON or Excel from the Apify console, or pull it through the Apify API into your CRM.

#### Is this affiliated with RE/MAX?

No. The RE/MAX Agent Email Scraper is an independent Actor and is not affiliated with, supported by or endorsed by RE/MAX or its franchisees.

### Related Actors

| Actor | What it collects |
|---|---|
| [RE/MAX Email and Phone Number Scraper](https://apify.com/leads-scraper/remax-agent-email-and-phone-number-scraper) | Emails and phone numbers from RE/MAX |
| [RE/MAX Phone Number Scraper](https://apify.com/leads-scraper/remax-agent-phone-number-scraper) | Public phone numbers from RE/MAX |
| [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 |
| [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 RE/MAX Agent 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? Email neurodata.apify@gmail.com and we will help.

# Actor input Schema

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

Search terms describing the RE/MAX 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 RE/MAX.

## `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": [
    "real estate agent",
    "realtor"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "listing agent",
    "inquiries",
    "broker"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by RE/MAX Agent 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": [
        "real estate agent",
        "realtor"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "listing agent",
        "inquiries",
        "broker"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/remax-agent-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": [
        "real estate agent",
        "realtor",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "listing agent",
        "inquiries",
        "broker",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/remax-agent-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": [
    "real estate agent",
    "realtor"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "listing agent",
    "inquiries",
    "broker"
  ]
}' |
apify call leads-scraper/remax-agent-email-scraper --silent --output-dataset

```

## MCP server setup

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