# Kijiji Real Estate Scraper (Canada) (`scrapyx/kijiji-real-estate-scraper`) Actor

Scrapes real estate listings from Kijiji, Canada's largest classifieds site, from any search URL you paste. Every row carries title, description, price, location with GPS coordinates, images and ad source; optional detail adds canonical attributes and MLS data.

- **URL**: https://apify.com/scrapyx/kijiji-real-estate-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.84 / 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.
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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Kijiji Real Estate Scraper (Canada)

Scrapes real estate listings from **[Kijiji](https://www.kijiji.ca)** —
Canada's largest classifieds site.

Public data only. No login, no cookies, no browser. No bot challenge on any
of 8 TLS profiles tested across search and detail pages.

### How input works: paste a search URL, don't type a city name

Kijiji's location ids are opaque integers (`Toronto = 1700273`,
`Vancouver = 80003`, ...) with no public autocomplete to resolve a name into
one. Rather than guess, this actor takes full search URLs — build your query
in Kijiji's own UI (any location, category or filter combination) and paste
the resulting URL:

```
https://www.kijiji.ca/b-real-estate/toronto/c34l1700273
https://www.kijiji.ca/b-for-rent/vancouver/c30349001l80003
```

**Ignore Kijiji's own `?page=N` in a copied URL.** It does nothing — page 2
of a query returns the identical page-1 payload. Pagination happens through a
different mechanism this actor handles for you (a `page-N` *path* segment),
so any query string on a pasted URL is stripped rather than trusted.

### What you get

Three record types share one dataset, told apart by `recordType`.

#### `PROPERTY` — one row per listing

Upstream's listing object, passed through verbatim: title, description,
price, location (address, nearest intersection, GPS coordinates), image
URLs, ad source, activation date. With **Fetch full property details** on,
each row also gets a `detail` object: canonical attribute names and values
(bedrooms, bathrooms, unit type, amenities...), MLS data where the listing is
MLS-sourced, virtual tour and video links, and the request-viewing URL.

#### `SEARCH_SUMMARY` — one row per search URL

Kijiji's own match total, pages fetched, requests spent.

#### `ERROR` — one row per input that could not be processed

Every input maps to at least one row, so nothing disappears silently.

### Input

| Field | What it does |
| --- | --- |
| **Search URLs** | One Kijiji search URL per entry. |
| **Fetch full property details** | One extra request per listing. Off by default. |
| **Max listings per search URL** | `0` for everything Kijiji will serve. |
| **Max pages per search URL** | `0` for no limit — the actor stops correctly at the true end regardless (see below). |
| **Max concurrent requests / Minimum seconds between requests** | Throughput controls. |

### Known limits

- **URLs, not location names.** See above — this is a deliberate choice, not
  a missing feature; there is nothing reliable to resolve a name against.
- **A location id Kijiji cannot resolve is an honest empty result**, not an
  error and not a silent fallback to nationwide results — `totalMatches: 0`,
  zero rows, zero errors.
- **Real estate only.** Kijiji is also a huge general marketplace, jobs board
  and vehicle listings site on a similar contract — out of scope here.
- **Pagination clamps past the true last page rather than going empty** — the
  site itself re-serves page 1 if you ask for a page number past the end.
  This actor detects that (stopping when a page carries no listing ids it
  hasn't already seen) so it is invisible to you, but it means "keep paging
  until the page is empty" would be the wrong approach for anyone extending
  this actor.

# Actor input Schema

## `searchUrls` (type: `array`):

One Kijiji real-estate search URL per entry, each with its own SEARCH\_SUMMARY row.

Kijiji's location ids are opaque and there is no public autocomplete for them, so this actor takes URLs built in Kijiji's own search UI rather than city names — build your search at kijiji.ca (any location, category, or filter combination) and paste the resulting URL here.

Examples:

```
https://www.kijiji.ca/b-real-estate/toronto/c34l1700273
https://www.kijiji.ca/b-for-rent/vancouver/c30349001l80003
```

Query-string filters (`?...`) are dropped — Kijiji's `?page=` parameter in particular is completely inert, so the actor always paginates itself and never trusts a page number in the pasted URL.

## `includePropertyDetails` (type: `boolean`):

Adds one request per listing and attaches a `detail` object with canonical attribute names/values, MLS data (for real listings sourced from MLS), virtual tour and video links, and the request-viewing URL.

Off by default — search rows already carry title, description, price, location with coordinates, image URLs and ad source.

## `maxItems` (type: `integer`):

Stop after this many listings per search URL. Set to 0 for everything Kijiji will serve for that query.

## `maxPages` (type: `integer`):

Stop after this many pages (40 listings/page). Set to 0 for no page limit — the actor still stops correctly at the true end, because it watches for pages that carry no new listing ids rather than trusting an empty page (Kijiji re-serves page 1 past its real last page instead of going empty).

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across all search URLs and any detail fetches.

## `minRequestInterval` (type: `integer`):

Paces how often requests START, without tying up a concurrency slot. Leave at 0 to use the built-in default of 0.3s -- 0 does not mean 'no pacing'.

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

Residential pinned to Canada. No WAF or bot challenge was observed on any of 8 TLS profiles across search and detail surfaces, but Kijiji is a Canada-only platform and container egress is a different posture than a home connection.

## Actor input object example

```json
{
  "searchUrls": [
    "https://www.kijiji.ca/b-real-estate/toronto/c34l1700273"
  ],
  "includePropertyDetails": false,
  "maxItems": 100,
  "maxPages": 0,
  "maxConcurrency": 4,
  "minRequestInterval": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CA"
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 = {
    "searchUrls": [
        "https://www.kijiji.ca/b-real-estate/toronto/c34l1700273"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/kijiji-real-estate-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 = { "searchUrls": ["https://www.kijiji.ca/b-real-estate/toronto/c34l1700273"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/kijiji-real-estate-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 '{
  "searchUrls": [
    "https://www.kijiji.ca/b-real-estate/toronto/c34l1700273"
  ]
}' |
apify call scrapyx/kijiji-real-estate-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/kijiji-real-estate-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/wjwpZpLBW3BahYe16/builds/Y3exaACgsf2LZO7bH/openapi.json