# Realtor.ca Listings Scraper (`devilscrapes/realtor-ca-listings-scraper`) Actor

Search Realtor.ca, Canada's national real-estate listing site from CREA, by city or bounding box and get normalized listing rows: price, address, beds, baths, and agent or brokerage contact details, with photos, for investment and lead-gen pipelines.

- **URL**: https://apify.com/devilscrapes/realtor-ca-listings-scraper.md
- **Developed by:** [DevilScrapes](https://apify.com/devilscrapes) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

<p align="center">
<img src=".actor/icon.svg" width="160" alt="Realtor.ca Listings Scraper" />
</p>

## Realtor.ca Listings Scraper

**$3.20 / 1,000 results** — pay only for results, no credit card to try.

Normalized Canadian residential listings from [Realtor.ca](https://www.realtor.ca),
CREA's national listing site — price, address, beds/baths, agent and
brokerage contact, and photos, ready for a spreadsheet or a pipeline, not a
scroll-and-read map search.

### 🎯 What this scrapes

Give it a curated Canadian city or an explicit bounding box, plus a
transaction type (sale or rent), and it returns one normalized record per
listing: MLS number, price, street address, latitude/longitude, property
type, beds/baths, interior size, amenities, agent name and
phone, brokerage name and address, photo URLs, and the listing's own
detail-page URL — deduplicated by listing ID across every page fetched in
the run. Canada's #1 residential portal already draws serious scraping
demand — the category's current leader alone runs over 16,000 times every
30 days — and this Actor targets the same `api2.realtor.ca` search
endpoint the site's own map search calls.

### 🔥 Features

- Curated 10-city convenience input (`Toronto`, `Vancouver`, `Montreal`,
  and more) **or** an explicit bounding box for precise areas.
- Sale **and** rent transaction types in one Actor.
- Price parsed from the listing's own numeric field, not scraped off
  formatted display text — with a formatted-text fallback if the numeric
  field is ever missing.
- Agent name, phone, and brokerage name/address normalized per row.
- Deduplicated by listing ID across pages within a run.
- English and French response modes (`cultureId`).

### 💡 Use cases

- **Investment deal screening** — pull normalized for-sale listings across
  any curated city or bounding box, with price/beds/baths ready for
  comparables analysis.
- **Rental market research** — switch transaction type to rent to track
  asking rents across a city or micro-area.
- **Agent/brokerage lead-gen** — collect agent name, phone, and brokerage
  contact per listing without visiting each detail page by hand.
- **Cross-city market monitoring** — run the curated city list on a
  schedule to track new listings and price movement over time.

### ⚙️ How to use it

1. Click **Try for free**.
2. Set `searchArea` to `{"city": "Toronto"}` (or any curated city), or pass
   an explicit `{"latitudeMax","latitudeMin","longitudeMax","longitudeMin"}`
   bounding box.
3. Pick `transactionType` (`sale` or `rent`) and `maxResults`.
4. Run. Results land in the default dataset — export to JSON or CSV.

### 📥 Input

| Field | Type | Default | Description |
|---|---|---|---|
| `searchArea` | object | `{"city": "Toronto"}` | Either `{"city": "<curated city>"}` or an explicit bounding box. Exactly one form |
| `transactionType` | string | `"sale"` | `sale` or `rent` |
| `cultureId` | string | `"1"` | `1` = English, `2` = French |
| `maxResults` | integer | `48` | Cap on rows returned for this run (server page size 12, server max 600) |
| `proxyConfiguration` | object | `{"useApifyProxy": true}` | Apify Proxy configuration |

```json
{
  "searchArea": {"city": "Toronto"},
  "transactionType": "sale",
  "cultureId": "1",
  "maxResults": 48,
  "proxyConfiguration": {"useApifyProxy": true}
}
```

Curated cities in v1: Toronto, Vancouver, Montreal, Calgary, Edmonton,
Ottawa, Winnipeg, Quebec City, Halifax, Victoria. Need somewhere else? Pass
an explicit bounding box instead.

### 📤 Output

One row per listing, deduplicated by `id`:

```json
{
  "id": "30320779",
  "mlsNumber": "C13821958",
  "price": 699000.0,
  "currency": "CAD",
  "transactionType": "sale",
  "streetAddress": "3703 - 35 MARINER TERRACE|Toronto (Waterfront Communities), Ontario M5V3V9",
  "latitude": 43.6398435,
  "longitude": -79.3920963,
  "propertyType": "Single Family",
  "bedrooms": "1 + 1",
  "bathroomTotal": 1,
  "sizeInterior": "65.0316 m2",
  "storiesTotal": "",
  "amenities": ["Security/Concierge", "Exercise Centre", "Visitor Parking", "Storage - Locker"],
  "floorAreaMeasurements": ["700+ sqft"],
  "agentName": "ROY WANG",
  "agentPhone": "905-909-0101",
  "brokerageName": "BAY STREET GROUP INC.",
  "brokerageAddress": "8300 WOODBINE AVE STE 500|MARKHAM, Ontario L3R9Y7",
  "photoUrls": ["https://cdn.realtor.ca/listings/TS639258083800500000/reb82/highres/8/c13821958_1.jpg"],
  "listingDetailUrl": "https://www.realtor.ca/real-estate/30320779/3703-35-mariner-terrace-toronto-waterfront-communities-waterfront-communities-c1",
  "searchCity": "Toronto",
  "page": 1,
  "scrapedAt": "2026-09-24T00:00:00Z"
}
```

### 💰 Pricing

| Event | Price |
|---|---|
| Actor start | $0.20 |
| Result row emitted | $0.003 |

Pay-per-event: 1,000 listings = **$3.20 per run** ($0.20 start + 1000 x $0.003).
No data → no charge (only the small actor-start warm-up fee).

### 🚧 Limitations

- v1 covers one search (one city or bounding box, one transaction type) per
  run, capped at the server's own 600-result ceiling.
- Only residential listings — commercial and land property groups are out
  of scope for v1.
- Listing-detail-page-only data (full photo galleries, open-house
  schedules, tax history, school ratings) isn't part of this search
  payload and isn't returned.
- No agent email and no listing description text: Realtor.ca's search
  results carry neither (emails are contact-form references, remarks are
  blank), so we don't emit empty columns for them.
- Curated city list covers 10 major Canadian cities; anywhere else needs an
  explicit bounding box.

### ❓ FAQ

**Do I need a Realtor.ca account or API key?**
No. This Actor reads Realtor.ca's own publicly listed search-result data —
no login, no API key.

**Can I search a custom area instead of a city?**
Yes — pass an explicit bounding box (`latitudeMax`/`latitudeMin`/
`longitudeMax`/`longitudeMin`) instead of a city name.

**What happens if my search matches nothing?**
The run finishes successfully with zero rows and a status message naming
what was searched — no charge beyond the small actor-start fee.

### 💬 Your feedback

Found a field that's off, or a city that needs adding to the curated list?
Open an issue via the Actor's Apify Store page or reach out at
[apify.com/DevilScrapes](https://apify.com/DevilScrapes) — we read every
report.

# Changelog

This Actor's version history is a separate document: https://apify.com/devilscrapes/realtor-ca-listings-scraper/changelog.md

# Actor input Schema

## `searchArea` (type: `object`):

Either {"city": "<curated Canadian city>"} or an explicit bounding box {"latitudeMax","latitudeMin","longitudeMax","longitudeMin"}. Exactly one form.

## `transactionType` (type: `string`):

sale or rent listings.

## `cultureId` (type: `string`):

1 = English, 2 = French.

## `maxResults` (type: `integer`):

Cap on rows returned for this run; drives pagination (server page size 12, server max 600).

## `proxyConfiguration` (type: `object`):

Apify Proxy. Defaults to RESIDENTIAL pinned to CA — a bare useApifyProxy with no group resolves to datacenter egress, which Cloudflare treats differently than the fingerprint-only block seen from a residential/office IP during recon.

## Actor input object example

```json
{
  "searchArea": {
    "city": "Toronto"
  },
  "transactionType": "sale",
  "cultureId": "1",
  "maxResults": 48,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CA"
  }
}
```

# Actor output Schema

## `datasetItems` (type: `string`):

All dataset items as JSON.

## `datasetItemsCsv` (type: `string`):

Same data exported to CSV.

## `datasetView` (type: `string`):

Open the run dataset in the Console.

# 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 = {
    "searchArea": {
        "city": "Toronto"
    },
    "transactionType": "sale",
    "cultureId": "1",
    "maxResults": 48,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "CA"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("devilscrapes/realtor-ca-listings-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 = {
    "searchArea": { "city": "Toronto" },
    "transactionType": "sale",
    "cultureId": "1",
    "maxResults": 48,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "CA",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("devilscrapes/realtor-ca-listings-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 '{
  "searchArea": {
    "city": "Toronto"
  },
  "transactionType": "sale",
  "cultureId": "1",
  "maxResults": 48,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CA"
  }
}' |
apify call devilscrapes/realtor-ca-listings-scraper --silent --output-dataset

```

## MCP server setup

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