# Job Board Scraper - 10 ATS Career Sites (`data_foundry/job-board-scraper`) Actor

Scrape open roles from 10 ATS career sites (Greenhouse, Ashby, Lever, Workable, Rippling and more) and get a diff of what opened and closed since your last run.

- **URL**: https://apify.com/data_foundry/job-board-scraper.md
- **Developed by:** [Data Foundry](https://apify.com/data_foundry) (community)
- **Categories:** Business, Automation, Marketing
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 20.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 companies

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

## Job Board Scraper - 10 ATS Career Sites

Scrape every open role from a company's own career page - Greenhouse, Ashby, Lever, Workable, Rippling and five more - without touching LinkedIn. Run it again and get a diff: which roles opened, which closed, which teams are growing.

<table>
<tr>
<th>What you get</th>
<th>Built for</th>
</tr>
<tr>
<td valign="top">

🏢 **10 ATS platforms** behind one input <br>
💼 **Every open role**: title, team, location, department, URL <br>
🆕 **Diff per company** - opened and closed since last run <br>
🎯 **Auto-discovery** - the board URL is found from the company name <br>
🔔 **Webhook on change**, HMAC signed <br>
🛡️ **Per-company isolation** - one broken board never kills the run

</td>
<td valign="top">

💸 **Sales triggers** - who is hiring the team that buys from you <br>
📈 **Hiring velocity** as a growth signal <br>
🕵️ **Competitor headcount** moves, team by team <br>
🧭 **Recruiting intel** - roles, locations, comp ranges <br>
🤖 **LLM-ready JSON**, one row per role <br>
🔗 **API, schedules, webhooks** via Apify

</td>
</tr>
</table>

### What data do I get?

One dataset record per open role, plus a `HIRING_SIGNALS` summary per company.

| Field | Meaning |
|---|---|
| `company` | the slug you passed |
| `title` | role title |
| `department` / `team` | where the role sits, when the ATS exposes it |
| `location` | as published, including "Remote" variants |
| `url` | direct application link |
| `postedAt` | first seen timestamp (from the actor, not the ATS) |
| `platform` | greenhouse, ashby, lever, workable, smartrecruiters, recruitee, personio, rippling, breezy, teamtailor |

The signal adds `openRoles`, `openedSinceLastRun`, `closedSinceLastRun`, `isFirstRun` and `suspicious`.

### How much does it cost?

Pay per event: **$10 per 1,000 companies scanned** ($0.01 each). Every role on the board is included - a company with 5 roles and one with 500 cost the same. Companies that fail are **not charged**.

| You track | Runs | Monthly cost |
|---|---|---|
| 100 companies, daily | 3,000 | **$30.00** |
| 100 companies, weekly | 430 | **$4.30** |
| 500 companies, daily | 15,000 | **$150.00** |

### How do I use it?

1. [Create](https://console.apify.com/sign-up) a free Apify account.
2. Open **Job Board Scraper** in Apify Console.
3. Paste company slugs (`stripe`, `ramp`, `vercel`) - the actor finds each company's board. Use `companyPlatforms` to pin a platform when detection picks the wrong one.
4. Run once as a baseline, then schedule it daily.
5. Set `webhookUrl` and let the diff come to you.

### Input

| Field | Type | Description |
|---|---|---|
| `companies` | array | Company slugs. The board is discovered across all 10 platforms. |
| `companyPlatforms` | object | Pin a slug to a platform, e.g. `{"stripe": "greenhouse"}`. |
| `maxCompanies` | integer | Cap on companies per run (default 500). |
| `includeDescriptions` | boolean | Include the role description text (larger records). |
| `maxJobsPerCompany` | integer | Cap per company, for very large boards. |
| `webhookUrl` | string | Optional https endpoint, called only when something changed. |
| `webhookSecret` | string | Optional. Adds `X-Signature-256: sha256=...`. |
| `concurrency` | integer | Companies scanned in parallel. |
| `timeoutSecs` | integer | Per-company budget. |

```json
{
  "companies": ["stripe", "ramp", "vercel", "linear"],
  "webhookUrl": "https://hooks.slack.com/services/..."
}
```

### Output

```json
{
  "company": "ramp",
  "platform": "ashby",
  "jobId": "6a1f...",
  "title": "Revenue Operations Manager",
  "department": "Revenue",
  "location": "New York, NY",
  "remote": false,
  "employmentType": "Full-time",
  "url": "https://jobs.ashbyhq.com/ramp/...",
  "postedAt": "2026-11-06T09:12:00+00:00"
}
```

### Notes and exceptions

- **The first run is a baseline.** Diffs start from the second run.
- **Company slugs, not URLs.** The actor checks the supported ATS platforms and uses the board that best matches the company, so a namesake with one job does not win over the real company.
- **No LinkedIn.** These are the companies' own career sites - the same data LinkedIn aggregates, without the login wall.
- **A board that goes dark is flagged `suspicious`**, not reported as "all roles closed".
- **The webhook fires when roles opened or closed**, matching the diff the actor reports.
- **Descriptions** are mapped from every adapter that publishes them when `includeDescriptions` is on; otherwise the field is removed from rows.
- **Careers pages that are custom-built** (not on a supported ATS) are out of scope.

### What can I do with the data?

**Sales triggers.** A company posting five RevOps roles is standing up a revenue operation. Four security engineers means a compliance programme. That lands in Slack the morning it happens.

**Hiring velocity.** `openRoles` over time is a growth proxy that updates before headcount announcements.

**Competitor mapping.** Which teams are growing, in which offices, at what level.

### Related Actors

- **[Review Scraper](https://apify.com/data_foundry/review-scraper)** - reviews across 11 sources with a diff.
- **[ASO App Rank Tracker](https://apify.com/data_foundry/aso-app-rank-tracker)** - chart rank and rating changes.
- **[Pricing Page Monitor](https://apify.com/data_foundry/pricing-page-monitor)** - competitor price changes.

### FAQ

**Do I need LinkedIn cookies or a login?** No - the actor reads company career sites directly.

**How is the board found?** The actor checks the supported ATS platforms and uses the board that best matches the company.

**Can I track a company on two platforms?** Only one board is used per company. If detection picks the wrong one, pin the right platform with `companyPlatforms`.

### Changelog

- **0.11** - `companyPlatforms` / `maxCompanies` inputs, descriptions from all adapters, closed-role webhooks, safer empty-board diffs.
- **0.9** - related actors, store copy.
- **0.8** - per-company pricing, webhook diffing.
- **0.1** - First release.

# Actor input Schema

## `companies` (type: `array`):

Board slugs, e.g. 'stripe', 'ramp', 'vercel'. The ATS is detected automatically. Use 'companyPlatforms' to pin a platform and skip detection.

## `companyPlatforms` (type: `object`):

Paste a JSON object mapping a board slug to its ATS when auto-detection picks the wrong one, e.g. {"stripe": "greenhouse"}. Allowed: greenhouse, ashby, lever, workable, smartrecruiters, recruitee, personio, rippling, breezy, teamtailor.

## `maxCompanies` (type: `integer`):

Hard cap on how many companies one run scans. Default 500, maximum 2000.

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

Include the full HTML description. Off by default: it makes responses much larger without changing the hiring signal.

## `maxJobsPerCompany` (type: `integer`):

0 means all open roles.

## `webhookUrl` (type: `string`):

If set, the actor POSTs a JSON digest to this URL whenever roles opened or closed since the previous run. Must be https. Nothing is sent when there is no change.

## `webhookSecret` (type: `string`):

When set, every webhook request carries X-Signature-256: sha256=HMAC_SHA256(secret, raw body). Verify it to be sure the payload came from this run.

## `concurrency` (type: `integer`):

How many companies to query at once. Board endpoints are lightweight; 4-8 is fine.

## `timeoutSecs` (type: `integer`):

How long to wait for a single board before giving up on it.

## Actor input object example

```json
{
  "companies": [
    "stripe",
    "ramp"
  ],
  "maxCompanies": 500,
  "includeDescriptions": false,
  "maxJobsPerCompany": 0,
  "concurrency": 4,
  "timeoutSecs": 30
}
```

# Actor output Schema

## `jobs` (type: `string`):

One record per open role: company, ATS, title, department, location, remote flag, posting date, URL.

## `signals` (type: `string`):

Per company: open roles, new and closed roles since the previous run, 30-day postings, remote share, top departments and locations.

# 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 = {
    "companies": [
        "stripe",
        "ramp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("data_foundry/job-board-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 = { "companies": [
        "stripe",
        "ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("data_foundry/job-board-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 '{
  "companies": [
    "stripe",
    "ramp"
  ]
}' |
apify call data_foundry/job-board-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,data_foundry/job-board-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/HgPi12tIeaD7gjZ6K/builds/jdYMxwtDVg0wpElLy/openapi.json