# North America Jobs Scraper · USA & Canada, 6 Boards, One Schema (`bibian/north-america-jobs-scraper`) Actor

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.

- **URL**: https://apify.com/bibian/north-america-jobs-scraper.md
- **Developed by:** [Vivien MORVAN](https://apify.com/bibian) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.96 / 1,000 job postings

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?

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

## North America Jobs Scraper · USA & Canada, 6 Boards, One Schema

Extract job postings from 6 major US and Canadian job boards in a single run — [Job Bank](https://www.jobbank.gc.ca) (the Government of Canada's official board), [The Muse](https://www.themuse.com), [Built In](https://builtin.com), [Dice](https://www.dice.com), [Wellfound](https://wellfound.com) and [Hacker News "Who is Hiring"](https://news.ycombinator.com) — 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`, `location` and `countries` apply the same way across all 6 sources.
- **Compare pay across boards**: every record shares the same `salaryMin`/`salaryMax` and `employmentType` fields, whichever site it came from.
- **Monitor new postings daily**: schedule it with `onlyNew` checked and `publishedWithinDays: 1` to 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

- `country` is 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.
- `employmentType` is 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 left `unknown` rather than guessed when nothing matches.
- Hacker News "Who is hiring?" postings are free text with no enforced format: `companyName` and fine-grained location are left `null` rather 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:

```js
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:

```python
from apify_client import ApifyClient

client = 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

1. **Schedule it.** Save a task, set its publication date filter to the shortest window, and schedule it daily with Apify Schedules. Deduplicate on the `id` field 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.
2. **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.
3. **Call it from your stack.** The API and the JavaScript and Python clients return the dataset as JSON, CSV or Excel.
4. **Let an AI agent use it.** Through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp), 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.

### More job scrapers by the same author

- [Remote Jobs Worldwide Scraper (8 boards)](https://apify.com/bibian/remote-jobs-worldwide-scraper)
- [Europe Jobs Scraper (12 boards, 7 countries)](https://apify.com/bibian/europe-jobs-scraper)
- [Latin America Jobs Scraper (4 networks, 18 countries)](https://apify.com/bibian/latin-america-jobs-scraper)
- [Dice Jobs Scraper](https://apify.com/bibian/dice-jobs-scraper)
- [Wellfound Jobs Scraper](https://apify.com/bibian/wellfound-jobs-scraper)
- [Built In Jobs Scraper](https://apify.com/bibian/builtin-jobs-scraper)

# Actor input Schema

## `keywords` (type: `string`):

Job title, skill or trade, for example "backend engineer" or "warehouse associate". Leave empty to get every posting.

## `location` (type: `string`):

City, province or state, used only by the sources that support it; ignored by the others.

## `remote` (type: `string`):

Keep only postings matching this work mode (best effort, based on whatever the source itself publishes). "Any" keeps every posting.

## `countries` (type: `array`):

Keep only postings in these countries (best effort, based on whatever location the source itself publishes).

## `sources` (type: `array`):

Job boards to query in this run.

## `publishedWithinDays` (type: `integer`):

Keep only postings published in the last N days. Use 1 for a daily monitoring run. Leave empty for no limit.

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

The run stops once this many postings are saved, across all sources combined.

## `includeDescriptions` (type: `boolean`):

Add the job description as plain text. Off by default to keep the default run fast.

## `onlyNew` (type: `boolean`):

For scheduled runs. Skip the results that an earlier run of this same search already delivered, so each run returns, and charges, only what is new. The memory is kept in a key-value store of your account named "only-new-memory-bibian-" followed by the ID of this Actor.

## Actor input object example

```json
{
  "keywords": "engineer",
  "remote": "any",
  "countries": [
    "US",
    "CA"
  ],
  "sources": [
    "jobbank",
    "themuse",
    "builtin",
    "dice",
    "wellfound",
    "hackernews"
  ],
  "maxItems": 50,
  "includeDescriptions": false,
  "onlyNew": false
}
```

# Actor output Schema

## `postings` (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": "engineer",
    "location": "",
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("bibian/north-america-jobs-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 = {
    "keywords": "engineer",
    "location": "",
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("bibian/north-america-jobs-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 '{
  "keywords": "engineer",
  "location": "",
  "maxItems": 50
}' |
apify call bibian/north-america-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bibian/north-america-jobs-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/KbbpO5cEdblSp0jvN/builds/i9x52Q75hv3DNXZ3Y/openapi.json