North America Jobs Scraper · USA & Canada, 6 Boards, One Schema
Pricing
from $0.96 / 1,000 job postings
North America Jobs Scraper · USA & Canada, 6 Boards, One Schema
Extract job postings from 6 major US and Canadian job boards in one run: Job Bank (Canada), The Muse, Built In, Dice, Wellfound and Hacker News Who is Hiring. One unified schema, deduplicated across sources, no login.
Pricing
from $0.96 / 1,000 job postings
Rating
0.0
(0)
Developer
Vivien MORVAN
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Extract job postings from 6 major US and Canadian job boards in a single run — Job Bank (the Government of Canada's official board), The Muse, Built In, Dice, Wellfound and Hacker News "Who is Hiring" — mapped to one unified schema, deduplicated across sources. No login, no browser to configure.
What you can do with it
- Search US and Canadian jobs across tech, startups and government postings in one run, instead of buying and maintaining 6 separate scrapers.
- Filter once, everywhere:
keywords,locationandcountriesapply the same way across all 6 sources. - Compare pay across boards: every record shares the same
salaryMin/salaryMaxandemploymentTypefields, whichever site it came from. - Monitor new postings daily: schedule it with
onlyNewchecked andpublishedWithinDays: 1to get, and pay for, only what is new since the last run.
Input
| Field | What it does |
|---|---|
keywords | Job title, skill or trade, for example backend engineer. Empty means every posting. |
location | City, province or state, used only by the sources that support it; ignored by the others. |
remote | Keep only postings matching this work mode: any, remote, hybrid or onsite. Best effort, based on whatever the source itself publishes. |
countries | Keep only postings in these countries: US, CA, or both (default). Best effort, based on whatever location the source itself publishes. |
sources | Which of the 6 job boards to query in this run. Defaults to all 6. |
publishedWithinDays | Keep only postings published in the last N days. Use 1 for a daily monitoring run. |
maxItems | The run stops once this many postings are saved, across all sources combined (default 50). |
includeDescriptions | Add the job description as plain text (off by default, for a fast run). |
onlyNew | For scheduled runs: skip postings an earlier run of this same search already delivered. |
Output
One record per posting, in the schema shared by every job actor on this account:
| Field | Type | Meaning |
|---|---|---|
id | string | Stable identifier (<source>:<native id>), used to deduplicate between runs. |
url | string | Public page of the posting. |
title | string | Job title as published. |
companyName | string or null | Employer name; null when hidden (then confidentialCompany: true). |
companyUrl | string or null | Company page on the source site, when it exists. |
locationLabel | string or null | Location as displayed by the site. |
city / region / postalCode | string or null | Finer location breakdown, when the site publishes one. |
country | string or null | US or CA. Job Bank is always CA; the other sources are matched against the location they publish, defaulting to US when nothing points elsewhere. Hacker News listings are free text with no reliable location convention, so an unresolved one stays null rather than being guessed. |
remote | string | remote, hybrid, onsite or unknown. |
employmentType | string | full_time, part_time, contract, freelance, internship, apprenticeship, temporary or unknown. |
salaryMin / salaryMax | number or null | Salary range, as numbers. |
salaryCurrency | string or null | ISO 4217 currency code. |
salaryPeriod | string or null | hour, day, month or year. |
datePosted | string or null | Publication date, ISO 8601. |
validThrough | string or null | Expiry date, ISO 8601. |
description | string or null | Plain-text description, only when includeDescriptions is on. No personal data. |
experienceLevel | string or null | As named by the site. |
industry | string or null | As named by the site. |
skills | string[] | Skills listed by the site, if any. |
source | string | Host name of the source site. |
sourceId | string | Native identifier on the source site. |
scrapedAt | string | Extraction timestamp, ISO 8601. |
Site-specific fields are kept in addition to these (never in place of them) — for example Wellfound's compensation free text, or Dice's remoteOnly flag.
Why this one
The only Apify actor that puts Canada's official Job Bank in the same schema as US tech boards (The Muse, Built In, Dice, Wellfound) and Hacker News's "Who is hiring?" threads — one run, one schema, deduplicated between sources. country on every row to split US from Canada without guessing. No connection, no login, no browser to configure, no recruiter e-mail ever included.
Good to know
countryis a best-effort filter for the 5 sources that are not single-country by construction: an unclear location is kept rather than dropped, only a clear signal (a Canadian province, city, or a place clearly outside North America) decides.employmentTypeis read from each site's own field when it has one; when a source carries none, it is inferred from the title and description, and leftunknownrather than guessed when nothing matches.- Hacker News "Who is hiring?" postings are free text with no enforced format:
companyNameand fine-grained location are leftnullrather than force-split from a headline that was never meant to be parsed. - Every result is deduplicated across all 6 sources before it is counted or charged.
- No personal data: contact details of individuals are stripped from descriptions; only companies are named.
Who uses it
- Recruiting agencies and HR teams watch which companies hire, for which roles and at which salary, in their market.
- Job boards and aggregators feed their own site with fresh postings in a stable schema, without maintaining a parser.
- B2B sales and lead generation: a company that is hiring is a company that is buying. Filter postings by role to spot prospects early.
- Labour-market research: salaries, skills in demand, remote share and hiring volume over time.
Pricing
Pay per result: $1.20 per 1,000 postings, plus $0.01 per run start with the default memory. For example, 100 postings cost about $0.13. You only pay for the postings you receive, and platform usage is included in that price. Store discounts apply automatically on paid Apify plans: up to 20% off every event on the higher tiers.
Run it from your code
JavaScript:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('bibian/north-america-jobs-scraper').call({keywords: 'engineer',maxItems: 50,});const { items } = await client.dataset(run.defaultDatasetId).listItems();
Python:
from apify_client import ApifyClientclient = ApifyClient(token="<APIFY_TOKEN>")run = client.actor("bibian/north-america-jobs-scraper").call(run_input={"keywords": "engineer","maxItems": 50})items = client.dataset(run["defaultDatasetId"]).list_items().items
Monitor new postings daily and connect your tools
- Schedule it. Save a task, set its publication date filter to the shortest window, and schedule it daily with Apify Schedules. Deduplicate on the
idfield if you keep your own copy. Tick Only new results in the input and each run returns, and charges, only the postings that earlier runs of the same search did not deliver. - Push the results where you work. Add an Apify integration or a webhook to the task: Google Sheets, Slack, Make, Zapier, n8n or your own endpoint, triggered at the end of every run.
- Call it from your stack. The API and the JavaScript and Python clients return the dataset as JSON, CSV or Excel.
- Let an AI agent use it. Through the Apify MCP server, assistants such as Claude or ChatGPT can search the Store, read this page and run the actor as a tool.
Frequently asked questions
Do I need an account, cookies or a proxy? No. The actor reads publicly visible pages only.
Which formats can I export? JSON, CSV, Excel, XML, HTML table or RSS, from the dataset page or through the API.
Is it legal to scrape? The actor collects publicly visible postings and respects the robots.txt rules of each site. How you use the data is your responsibility: check the site's terms and the laws that apply to you, for example the GDPR.
Something does not work? Open an issue in the Issues tab. Every public actor is test-run daily and the broken ones are repaired.
Did this save you time? A short review on the Store page helps other people find the actor, and tells me what to improve next.