# Canada Building Permits: Toronto, Vancouver, Calgary, Montréal (`steady-scrape/canada-building-permits`) Actor

Issued building permits from the official open data of Toronto, Vancouver, Calgary and Montréal in one schema. Filter by city, date, keywords (English or French) and value; monitor mode returns only new or changed permits. No owner names.

- **URL**: https://apify.com/steady-scrape/canada-building-permits.md
- **Developed by:** [SteadyScrape](https://apify.com/steady-scrape) (community)
- **Categories:** Lead generation, Real estate, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 permit returneds

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

## Canada Building Permits: Toronto, Vancouver, Calgary, Montréal

Get **issued building permits** from the official open data of **Toronto, Vancouver, Calgary and Montréal** in one clean schema. Filter by keyword (English or French), estimated value and date. **Monitor mode** returns only permits that are new or changed since your last run, so a daily schedule gives you a feed of fresh leads.

Built for roofers, renovators, HVAC, solar and window installers, suppliers, lenders and anyone who watches construction activity in Canadian cities.

### What you get

| Field | Example |
|---|---|
| `city`, `province` | Toronto, ON |
| `permitNumber` | 26 123456 BLD |
| `issuedDate`, `appliedDate`, `completedDate` | 2026-11-10 |
| `status` | Issued Permit |
| `permitType`, `workType`, `buildingType` | Small Residential Projects / Alteration |
| `description` | Re-roofing of existing single family dwelling |
| `estimatedValue`, `currency` | 45000, CAD |
| `dwellingUnitsCreated` | 0 |
| `address`, `postalPrefix` (FSA only), `area` | 123 Example St, M4C, Ward 14 |
| `latitude`, `longitude` | 51.05, -114.10 (where the city publishes them) |
| `contractor` | only when `includeContractor` is on |
| `sourceName`, `sourceUrl`, `licence`, `attribution` | per city |
| `changeType`, `changedFields` | new / changed, \["status"] |

Results are sorted newest first. The run summary (key-value store `OUTPUT`) shows rows per city, matches, and which cities (if any) failed.

### Input

- **Cities**: any of Toronto, Vancouver, Calgary, Montréal (default: all).
- **Issued in the last N days**: 1–90 (default 14).
- **Keywords / exclude keywords**: matched against description, permit type, work type and uses. Case- and accent-insensitive, so `toiture` matches `Toiture` and `TOITURE`. For Montréal use French terms (e.g. `toiture`, `fenêtres`, `agrandissement`, `démolition`).
- **Minimum estimated value (CAD)**: drops permits below the value, and permits with no value (Montréal does not publish values).
- **Max results** (default 200, up to 5,000), shared fairly across cities.
- **Mode**: `search` (everything in the window) or `monitor` (only new or changed since the last run with the same **Monitor ID**). `firstRunEmitsAll` = false makes the first monitor run a silent baseline.

#### Example

```json
{
  "cities": ["toronto", "calgary", "montreal"],
  "issuedWithinDays": 7,
  "keywords": ["roof", "re-roof", "shingle", "toiture"],
  "mode": "monitor",
  "monitorId": "roofing-leads"
}
```

### Sources and licences

| City | Source | Licence | Freshness |
|---|---|---|---|
| Toronto | City of Toronto Open Data (CKAN) – Building Permits, Active Permits | Open Government Licence – Toronto | daily |
| Vancouver | City of Vancouver Open Data (Opendatasoft) – Issued building permits | Open Government Licence – Vancouver | weekly-ish |
| Calgary | City of Calgary Open Data (Socrata) – Building Permits | Open Government Licence – City of Calgary | daily |
| Montréal | Données Montréal – Permis de construction, transformation et démolition | CC BY 4.0 | weekly-ish |

Each row carries its `licence` and `attribution` text. If you republish the data, keep the attribution. This Actor is not affiliated with or endorsed by any of these cities.

### Privacy

Permit data is public, but this Actor keeps personal data out:

- **Never output:** applicant and owner names, applicant addresses, e-mails and phone numbers.
- Phone numbers and e-mail addresses inside free-text descriptions are masked (`[phone]`, `[email]`).
- Toronto postal codes are cut to the first three characters (FSA).
- **Contractor names** are off by default (an owner-builder can be a private person). Turn on `includeContractor` only if you have a legitimate business use.
- Caveat: Vancouver descriptions sometimes name the engineer or architect of record. Those names come from the city's own text and can't be reliably removed.

### Pricing

Pay per event: a small charge per permit returned plus a small charge per run that returns at least one permit. Runs with no results, failed runs and invalid input are free. Set a **maximum charge per run** in the run options to cap your spend; the Actor stops returning permits before the cap.

### Limits and notes

- **Ottawa** is not included: it publishes monthly Excel files only, with no live API.
- **Montréal** has no estimated value and descriptions are in French.
- **Calgary** descriptions are often short or empty; use `workType`, `permitType` and `proposedUse`.
- Cities sometimes publish a permit days after its issue date. For a daily monitor, use a 7-day window; monitor mode removes duplicates.
- If one city's API is down, the others still return and the summary names the failed city. If every selected city fails, the run fails and nothing is charged.

### FAQ

**Can I get permits for other cities?** Not yet. Edmonton, Winnipeg and Ottawa are candidates; tell us in Issues.

**Are these applications or issued permits?** Issued permits (with status where the city publishes it).

**How far back can I go?** Up to 90 days per run.

### More from SteadyScrape

- [Public Tenders Monitor: SAM.gov, CanadaBuys & TED](https://apify.com/steady-scrape/public-tenders-monitor): new government tenders and contract notices from the US, Canada and the EU, to pair with permit activity.
- [Google Maps Leads: No Website, Unclaimed Profiles](https://apify.com/steady-scrape/google-maps-business-segments): local business lead lists from Google Maps, to find suppliers and contractors in the same cities.
- [Company Data Enrichment by Domain: Logo & Socials](https://apify.com/steady-scrape/company-profile-by-domain): enrich the companies you find with profiles from their own sites.

See every **SteadyScrape (steady-scrape)** Actor on [our Apify profile](https://apify.com/steady-scrape).

# Actor input Schema

## `cities` (type: `array`):

Which cities to check. Each comes from the city's official open-data API. Ottawa is not included yet (it publishes monthly spreadsheets only).

## `issuedWithinDays` (type: `integer`):

Permits issued in this window (1-90 days, by calendar date). For a daily monitor, 7 days is a safe overlap: cities sometimes publish a permit a few days after its issue date.

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

Return permits whose permit type, work type, building use or description contains any of these words (case- and accent-insensitive). Add French words for Montréal, e.g. toiture, revêtement, agrandissement. Leave empty for all permits.

## `excludeKeywords` (type: `array`):

Drop permits containing any of these words, e.g. antenna, sign, enseigne.

## `minValue` (type: `integer`):

Only permits with an estimated value at or above this. Montréal publishes no value, so Montréal permits are dropped when this is set.

## `mode` (type: `string`):

Monitor mode remembers what it returned (per Monitor ID) and returns only new permits and permits whose status, dates, value, type or description changed.

## `monitorId` (type: `string`):

Name for this watch list (letters, digits, dashes). Use a different ID for each saved search you schedule.

## `firstRunEmitsAll` (type: `boolean`):

On: the first run of a new Monitor ID returns every match as 'new'. Off: it silently saves them as the baseline and later runs return only changes.

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

Maximum permits returned per run (newest first, shared across cities).

## `includeDescription` (type: `boolean`):

The city's description of the work (phone numbers and e-mails masked).

## `includeContractor` (type: `boolean`):

Add the builder or contractor name where the city publishes one (Toronto builder, Vancouver building contractor, Calgary contractor). Off by default: for owner-builders this can be a private person's name. Applicant and owner names are never returned.

## Actor input object example

```json
{
  "cities": [
    "toronto",
    "vancouver",
    "calgary",
    "montreal"
  ],
  "issuedWithinDays": 14,
  "keywords": [
    "roof",
    "toiture",
    "siding",
    "revêtement"
  ],
  "mode": "search",
  "monitorId": "default",
  "firstRunEmitsAll": true,
  "maxResults": 50,
  "includeDescription": true,
  "includeContractor": false
}
```

# Actor output Schema

## `permits` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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": [
        "roof",
        "toiture",
        "siding",
        "revêtement"
    ],
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("steady-scrape/canada-building-permits").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": [
        "roof",
        "toiture",
        "siding",
        "revêtement",
    ],
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("steady-scrape/canada-building-permits").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": [
    "roof",
    "toiture",
    "siding",
    "revêtement"
  ],
  "maxResults": 50
}' |
apify call steady-scrape/canada-building-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,steady-scrape/canada-building-permits"
        }
    }
}
```

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/zlASm92vWuqCSenlP/builds/JXDN6rtVOIyedOVR4/openapi.json
