Job Bank Canada Real-Time Data

Collect live job listings from Job Bank Canada in real time — keyword search, employer watchlists, full detail enrichment, and direct URL lookup. Every record streams to your dataset as it is collected, and can also be pushed to a webhook the moment it is finalized.

Free trial: on the Apify free plan each run returns a 2-result sample. Upgrade to a paid Apify plan for full, unlimited data.

Who it is for

• Recruiters & sourcers building pipeline from fresh Canadian postings by role and location
• Staffing agencies monitoring new openings at target employers across Canada
• Newcomers & job seekers tracking who is hiring right now, by city and occupation
• Labor-market researchers tracking hiring demand, titles, wages, and NOC codes
• Sales teams prospecting organisations that are actively hiring
• AI agents that need structured, up-to-date Canadian job data on demand

Features

Feature	What it does	Default
💼 Job search	Search live listings by keyword + location; fast cards with title, employer, location, salary, posting date, job number	On (10 per search)
✨ Fetch full details	Enriches each row in place with full description, salary range, employment terms, hours, vacancies, NOC code, address	Off
🏢 Company jobs	Openings at named employers (one search per employer)	Off
🔗 Scrape by URL	Full rows from explicit Job Bank posting links	Off
📣 Webhook delivery	Extra real-time push of every record (JSON or Slack)	Off

Enrichment never drops rows: every discovered job is exported, with detailsFetched: true when full details were added.

Input reference

Field	Type	Default	Example
enableJobSearch	checkbox	true	—
jobKeywords	string list	["cook"]	["truck driver", "registered nurse"]
jobLocation	text	""	"Toronto", "Vancouver", "Calgary"
jobsPerQuery	number	10	50
fetchFullDetails	checkbox	false	true for descriptions + salary ranges + NOC
enableCompanyJobs	checkbox	false	—
companyNames	string list	[]	["Air Canada", "Loblaws"]
jobsPerCompany	number	10	25
enableScrapeByUrl	checkbox	false	—
jobUrls	string list	[]	["https://www.jobbank.gc.ca/jobsearch/jobposting/50395604"]
webhookUrl	text	""	Slack incoming webhook or Zapier URL
webhookFormat	select	"json"	"slack" for chat-friendly messages
proxyConfiguration	proxy	Residential / CA	—

Leave everything untouched and press Start: the demo searches "cook" across Canada and returns up to 10 jobs in seconds.

Output fields

Each dataset row is one job: featureType, jobId, jobNumber, title, company, location, address (with full details on), salary, salaryMin, salaryMax, salaryCurrency, salaryPeriod, workHours, snippet, postedAt, postedText, employmentType, shifts, startDate, vacancies, nocCode, nocTitle, descriptionText (with full details on), detailsFetched, jobUrl, searchQuery, searchLocation, position, source, scrapedAt.

The run OUTPUT record summarizes totalPushed, enabledFeatures, errors, spendingLimitReached, and the paywall gate state.

Webhooks

Set webhookUrl to receive every record twice: once in the dataset (always), once as a POST to your URL. Choose json for the raw record or slack for a ready-to-read chat message. Delivery is fire-and-forget — a failing webhook never stops the run.

AI-agent usage (MCP)

Pair this Actor with the Apify MCP server, then ask things like:

"Find the 10 newest cook jobs in Toronto on Job Bank Canada with salary info, and send them to my webhook."

The agent maps your question onto jobKeywords, jobLocation, jobsPerQuery, and fetchFullDetails automatically.

FAQ

How fresh is the data? Every run collects the listings shown on Job Bank Canada right now — nothing is cached or pre-stored.

Which proxy should I use? The default Apify residential proxy (CA) works out of the box and gives the freshest results.

Why did a free-plan run return only 2 results? That is the free-trial sample. Upgrade to a paid Apify plan for full, unlimited data.

Do I pay per result? The Actor charges one result pay-per-event credit per exported job. The jobsPerQuery / jobsPerCompany caps are your cost levers, and runs always respect your spending limit gracefully.

A run returned fewer rows than my cap — is something wrong? Usually not: some searches simply have fewer matching listings, and detail enrichment never filters rows out. Re-run later or widen the keywords.