# Realtor.ca Agent Scraper (`yugenox/realtor-ca-agent-scraper`) Actor

Scrape real-estate AGENT profiles from Canada's Realtor.ca (CREA MLS): name, brokerage, phone, office address, title, photo, profile link — by Canadian city, province, or postal code. Canada only, not the US realtor.com. For listings, use the Realtor.ca Property Scraper.

- **URL**: https://apify.com/yugenox/realtor-ca-agent-scraper.md
- **Developed by:** [Yugenox Corp](https://apify.com/yugenox) (community)
- **Categories:** Real estate, Lead generation, Agents
- **Stats:** 10 total users, 3 monthly users, 95.1% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Realtor.ca Agent Scraper — Canadian Real Estate Agent Data

Pull **real-estate agent profiles from [Realtor.ca](https://www.realtor.ca)**, the national
CREA/MLS® directory, for any Canadian city, neighbourhood, district or province. Name, brokerage,
direct phone, title, office address, photo and profile URL — as a clean JSON, CSV or Excel table.

> 🇨🇦 **Canada only.** This covers Realtor.ca. For US agents use a realtor.com scraper, and for
> Canadian *listings* see the **Realtor.ca Property Scraper**.

***

### Why this scraper

Realtor.ca sits behind **Imperva Advanced Bot Protection**, which is why most "Canadian real estate"
scrapers either don't exist or quietly return national results instead of the city you asked for.

- **No API key, no MLS® feed, no CREA membership.** You do not need a brokerage login.
- **Real location filtering.** Searches go through Realtor.ca's own search flow, so "Toronto" returns
  Toronto agents — not a national sample with a Toronto label on it.
- **Fast.** ~1,000 agents across three cities in about 30 seconds.
- **Honest failures.** A location Realtor.ca can't resolve is reported as a bad location, not
  silently swapped for national results.

***

### Input

| Field | Type | Required | Description |
|---|---|:--:|---|
| `locations` | array of strings | ✅ | Canadian locations to search. |
| `limitPerLocation` | integer | | Max agents to collect per location. Results page in ~20s. |

#### What `locations` accepts

| Form | Example | Works |
|---|---|:--:|
| City + province | `"Toronto, ON"` | ✅ |
| City | `"Mississauga"` | ✅ |
| Neighbourhood / district | `"Yorkville"`, `"North York"` | ✅ |
| Province name or code | `"Ontario"`, `"ON"` | ✅ |
| **Postal code** | `"M5V 2T6"` | ❌ not supported by Realtor.ca agent search |

Spelling has to match Realtor.ca. `"Godrich, ON"` is not a location — `"Goderich, ON"` is. A
misspelling is reported back to you explicitly rather than retried.

```json
{
  "locations": ["Toronto, ON", "Mississauga, ON", "Vancouver, BC"],
  "limitPerLocation": 100
}
```

***

### Output

One row per agent.

| Field | Type | Description |
|---|---|---|
| `individualId` | number | Realtor.ca agent ID. Stable — use it as your primary key. |
| `name` | string | Agent name, as CREA stores it (often upper case). |
| `phone` | string | Direct phone, when published. |
| `brokerage` | string | Brokerage / office name. |
| `officeAddress` | string | Brokerage address. |
| `position` | string | Title, e.g. Sales Representative, Broker, Broker of Record. |
| `credentials` | string | Designations, where Realtor.ca publishes them. |
| `photoUrl` | string | Profile photo. |
| `profileUrl` | string | Realtor.ca profile page. |
| `location` | string | The location you searched, echoed back for grouping. |

```json
{
  "individualId": 1234567,
  "name": "JANE DOE",
  "phone": "(416) 555-0142",
  "brokerage": "ROYAL LEPAGE SIGNATURE REALTY",
  "officeAddress": "123 Main St W, Toronto, ON M5V 1A1",
  "position": "Sales Representative",
  "credentials": null,
  "photoUrl": "https://cdn.realtor.ca/individuals/TS.../lowres/1234567.jpg",
  "profileUrl": "https://www.realtor.ca/agent/1234567/jane-doe",
  "location": "Toronto, ON"
}
```

*Values above are illustrative.*

***

### What people use it for

**Recruiting for a brokerage.** Pull every agent in a set of cities, filter by `position` and
`brokerage`, and you have a targeted recruiting list instead of a LinkedIn guess.

**Proptech and lead-gen.** A current agent directory per market, refreshed on a schedule, to power
agent-matching, CRM enrichment or a "find an agent" product.

**Market and competitive analysis.** Agent counts by brokerage per city tell you who actually holds
share in a market — useful for expansion planning and for pitching brokerages.

**Vendor prospecting.** Anyone selling *to* realtors — photographers, stagers, drone operators,
mortgage brokers, SaaS — needs the same list, by city, with brokerage and phone attached.

***

### Scale, speed and cost

- \~**1,000 agents in ~30 seconds** across three cities.
- A single city query tops out around **500 agents**; larger cities are swept in slices automatically.
- Province inputs work but are slower than naming cities directly.
- Cost is Apify compute only — there is no third-party solver or per-request fee behind this actor.

Start small (`limitPerLocation: 10`) to see the shape of the data, then scale up.

***

### FAQ

**Do I get agent email addresses?**
No. Realtor.ca does not publish agent emails anywhere — it uses a contact form. Any tool claiming
Realtor.ca emails is enriching them from another source, not reading them from Realtor.ca. You get
the direct phone, which is published.

**Can I search by postal code?**
No. Realtor.ca's agent search doesn't accept postal codes. Use the city, neighbourhood or district.

**Why is `officeAddress` empty for some agents?**
Because that agent has address display turned off in CREA. Realtor.ca's own page doesn't show it
either — the data isn't public rather than missed.

**Can I filter by rating, or by buyer vs seller agent?**
No. Unlike realtor.com, Realtor.ca publishes neither ratings nor a buyer/seller split, so no scraper
can return them.

**Do I need a proxy?**
No. It works from Apify's default IPs at normal volume.

**How do I get listings, not agents?**
Use the **Realtor.ca Property Scraper** — price, beds, baths, size, days on market, photos,
coordinates and MLS® number.

**How fresh is the data?**
It's read live at run time, so it reflects Realtor.ca at the moment of the run. Schedule the actor
to keep a directory current.

**A location returned nothing — why?**
Realtor.ca could not resolve the text. It's nearly always a spelling variation; the run tells you
which value failed so you can correct it.

***

**Is it legal to scrape REALTOR.ca?**
This Actor only collects publicly available data: agent and brokerage profiles that anyone can view on REALTOR.ca without an account. Collecting publicly available data is generally legal, but you're responsible for how you use it. Results can include agents' names and business contact details, and that counts as personal data. You must follow privacy laws such as GDPR, PIPEDA and CCPA, as well as REALTOR.ca's terms. If you're unsure, check with a lawyer. More on this: [Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/)

**Does it access any private data?**
No. Everything comes from pages REALTOR.ca shows to any visitor without logging in. It never uses a login, never touches private or restricted accounts, and never reaches password-protected areas.

### Notes

- MLS®, Multiple Listing Service® and REALTOR® are trademarks owned by The Canadian Real Estate
  Association. This actor is not affiliated with or endorsed by CREA or Realtor.ca.
- Only publicly visible directory information is collected.

# Actor input Schema

## `locations` (type: `array`):

Canadian locations to search. Use "City, Province" (e.g. "Toronto, ON"), a city, district or neighbourhood ("North York", "Yorkville"), or a province ("Ontario"). Postal codes are NOT supported by realtor.ca agent search. Spelling must match realtor.ca.

## `limitPerLocation` (type: `integer`):

Cap agents collected per location (~20 per results page).

## Actor input object example

```json
{
  "locations": [
    "Toronto, ON",
    "Mississauga, ON",
    "Vancouver, BC"
  ],
  "limitPerLocation": 50
}
```

# 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 = {
    "locations": [
        "Toronto, ON"
    ],
    "limitPerLocation": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("yugenox/realtor-ca-agent-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 = {
    "locations": ["Toronto, ON"],
    "limitPerLocation": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("yugenox/realtor-ca-agent-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 '{
  "locations": [
    "Toronto, ON"
  ],
  "limitPerLocation": 50
}' |
apify call yugenox/realtor-ca-agent-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,yugenox/realtor-ca-agent-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/eXsclWPjEQ0HNQRdI/builds/KxFodDzt6nJ7om1tB/openapi.json