Canada Company Data — Corporations Registry 🇨🇦

foXLabs Americas company-registry series: Brazil · Mexico · Colombia · Peru

🎉 Turn the Canadian corporations registries into clean, structured company data — no login, no API key, one row per entity, with the corporation number, status, jurisdiction and address. Built for B2B sales, lead generation, KYB / compliance and market-research teams.

🔍 What is the Canada Company Data — and when should you use it?

Give this actor company names or Canadian corporation numbers and it returns matching companies from the Canadian federal and provincial corporations registries (open data) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a company list for outreach; a quick profile before a call; or a starting point for account research.

Use something else when: you need firmographics the registry doesn’t hold (revenue, headcount, website, email) — pair this with an enrichment actor from Fox Labs.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/canada-company-data.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull Canada company records using the Apify Actor `foxlabs/canada-company-data`.
Input: `companyNames`, `corporationNumbers`, `category`, `province` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"companyNames":["Shopify","Lululemon"],"maxResults":100}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/canada-company-data.md.

📋 Overview

Everything you need to turn the Canadian federal and provincial corporations registries (open data) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole registry, one call — name or ID in, matching companies out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~canada-company-data/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companyNames":["Shopify","Lululemon"],"maxResults":100}'

🚀 Getting Started (3 steps)

1. Choose your targets — company names or Canadian corporation numbers.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"companyNames":["Shopify","Lululemon"],"maxResults":100}

Field	Type	Description
companyNames	array	Search by company name across Federal + BC registries. Substring match (e.g. "Shopify" finds Shopify Inc.).
corporationNumbers	array	Federal corporation number (e.g. 8660115) or BC registration number. Most precise lookup.
category	string	Browse/list federal corporations by organisation TYPE. The federal open data has no industry/NAICS codes, so this is the corporate form. Works without a…
province	string	Filter federal results to a province/territory. Use with Category to browse (e.g. all not-for-profits in Ontario), or alongside a name search.
jurisdiction	string	Which registry to search. Federal = Corporations Canada (CBCA). BC = British Columbia (OrgBook). Both = merge. Category/Province browse is federal only.
includeInactive	boolean	Federal: also stream the dissolved/inactive corporations file (larger, slower). BC already excludes historical.
bcBusinessNumber	boolean	For BC results, make one extra OrgBook call per company to retrieve the 9-digit business number (the search result alone rarely includes it). Turn off for…
maxResults	integer	Hard cap on records (1–50000).
proxyConfiguration	object	Apify Proxy. Datacenter is fine — official open-data sources don't block.

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
jurisdiction	Jurisdiction of formation
corporateName	Corporate Name
corporateNameSecondary	Corporate Name Secondary
corporationNumber	Corporation Number
businessNumber	Business Number
governingLegislation	Governing Legislation
status	active / inactive / dissolved
anniversaryDate	Anniversary Date
yearOfLastFiling	Year Of Last Filing
lastAnnualMeeting	Last Annual Meeting
street	Street
city	City
province	Province
country	Country
postalCode	Postal code
directorsMin	Directors Min
directorsMax	Directors Max
source	Source
sourceUrl	Public registry URL for the record

💼 Use cases

1. Canada B2B lead lists — active Canadian corporations by name. Input: name searches. Output: entities + jurisdiction + address. Use: a ready sales list.

2. Federal vs provincial — separate federal and provincial incorporations. Input: name searches. Output: jurisdiction. Use: segment the market.

3. KYB / due diligence — verify a Canadian corporation by number. Input: the number or name. Output: the canonical registry record. Use: confirm existence and status.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/canada-company-data').call({"companyNames":["Shopify","Lululemon"],"maxResults":100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/canada-company-data').call(run_input={"companyNames":["Shopify","Lululemon"],"maxResults":100})
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

Written for apify-client 3 for Python, where call() returns a run object; with version 1 or 2 it returns a dict — write run['defaultDatasetId'] there.

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads the Canadian federal and provincial corporations registries (open data).

What do I search by? Company names or Canadian corporation numbers.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

Why are firmographics like revenue or website missing? A public business registry doesn’t hold them; we don’t ship empty columns. Pair with an enrichment actor from Fox Labs.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads a public government business registry published as open data. Results can still contain personal data (e.g. a registered agent’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.27 — 2026-10-08 — README: the Python example works with the current Apify client

• The README's Python example read the results with run['defaultDatasetId']. With the current Apify client for Python (version 3) call() returns a run object, not a dict, and that line raised TypeError: 'Run' object is not subscriptable — after the run itself had finished. The example now reads run.default_dataset_id; with client version 1 or 2, keep run['defaultDatasetId']. Checked with apify-client 3.2.1, 2.5.1 and 1.12.2.
• No code, output field or pricing change.

0.1.26 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"companyNames":["Shopify","Lululemon"],"maxResults":100}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from the Canadian federal and provincial corporations registries (open data) by name or registry ID.