# ATS Job Boards Scraper (Greenhouse, Lever, Ashby) (`ardent_fork/ats-job-boards`) Actor

Live job postings straight from companies' Greenhouse, Lever and Ashby job boards, normalised into one schema: title, locations, remote/hybrid/onsite, department, employment type, salary range where published, full description, dates, apply URL. No cap, no stale database, no login.

- **URL**: https://apify.com/ardent_fork/ats-job-boards.md
- **Developed by:** [KF P](https://apify.com/ardent_fork) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.80 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## ATS Job Boards Scraper (Greenhouse, Lever, Ashby)

Live job postings straight from the public job-board APIs that thousands of companies' careers pages run on: **Greenhouse**, **Lever** and **Ashby**. Give it company slugs or careers URLs and get every open posting as one normalised row — the same fields whichever ATS the company uses.

Why this one: it reads the boards **live** (no database, no 6-month window, no per-run cap), auto-detects the ATS from a careers URL, exposes **structured salary ranges** where boards publish them (Ashby, Lever), and bills per job delivered.

### Input

| Field | Type | Description |
|---|---|---|
| `companies` | array | Board slugs or URLs (max 500). A bare slug (`stripe`) is tried on all three ATSes; `<ats>:<slug>` (`lever:spotify`) pins one; any `boards.greenhouse.io` / `job-boards.greenhouse.io` / `jobs.lever.co` / `jobs.ashbyhq.com` URL works too. |
| `ats` | array | Restrict auto-detection to some of `greenhouse`, `lever`, `ashby`. Empty = all. |
| `includeDescriptions` | boolean | Keep the full description (HTML + plain text). Default `true`. |
| `maxItems` | integer | Stop after this many jobs (default 500, max 100000). You pay only for pushed jobs. |
| `maxConcurrency` | integer | Parallel requests (default 5, max 10); each API host is also paced ~1 request/s. |
| `proxyConfiguration` | object | Optional; normally not needed. |

The slug is the path segment after the host on the company's careers page: `boards.greenhouse.io/**stripe**`, `jobs.lever.co/**spotify**`, `jobs.ashbyhq.com/**openai**`. Other careers domains (e.g. `careers.example.com`) are not auto-detected — open the page, find the embedded ATS link, and pass that.

```json
{
  "companies": ["stripe", "lever:spotify", "https://jobs.ashbyhq.com/openai"],
  "maxItems": 2000
}
```

### Output

One dataset item per posting:

```json
{
  "ats": "ashby",
  "company": "ramp",
  "id": "4f8c...",
  "title": "Software Engineer, Backend",
  "locations": ["New York", "San Francisco"],
  "workplaceType": "hybrid",
  "isRemote": false,
  "department": "Engineering",
  "team": "Platform",
  "employmentType": "FullTime",
  "compensation": { "min": 211400, "max": 290600, "currency": "USD", "interval": "1 YEAR", "summary": "$211.4K - $290.6K" },
  "descriptionHtml": "<p>...</p>",
  "descriptionText": "...",
  "publishedAt": "2026-08-24T14:44:49.699Z",
  "updatedAt": null,
  "url": "https://jobs.ashbyhq.com/ramp/4f8c...",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/4f8c.../application",
  "raw": { "address": { "addressLocality": "New York", "addressRegion": "New York", "addressCountry": "United States" }, "isListed": true, "compensationTiers": [] }
}
```

`raw` carries ATS-specific extras: Greenhouse `offices`, `metadata`, `requisitionId`, `internalJobId`, `language`, `applicationDeadline`; Lever `country`, `level`, `opening`; Ashby `address`, `isListed`, `compensationTiers`.

### Field coverage by ATS

| Field | Greenhouse | Lever | Ashby |
|---|---|---|---|
| `locations` | split from the board's location string (`•`, `;`, `\|` separators) | `categories.location` + `allLocations` | `location` + `secondaryLocations` |
| `workplaceType` / `isRemote` | derived: per-board metadata ("Workplace Type", "Location Type") or the location string ("Remote - USA", "Hybrid; In-Office", "Distributed"); null when neither says | `workplaceType` | `workplaceType`, `isRemote` |
| `department` / `team` | departments joined with `/` | `categories.department` / `team` | `department` / `team` |
| `employmentType` | per-board metadata ("Employment Type": Regular, Intern, ...) when the board has it, else null | `categories.commitment` | `employmentType` |
| `compensation` | not exposed (sometimes in `raw.metadata`) | `salaryRange` when the board publishes it | `compensation` summary + salary component |
| `publishedAt` / `updatedAt` | `first_published` / `updated_at` | `createdAt` / – | `publishedAt` / – |

### Billing

Pay per event: one `job` event per posting pushed. Postings are de-duplicated per ATS id within a run. If the run's charge limit (`maxTotalChargeUsd`) is reached, it stops cleanly and reports how many jobs were pushed.

### Speed and run timeout

Each board is one API call; a typical company takes 1–3 s, a very large board (800+ postings, ~15 MB) a few seconds more. 100 companies ≈ 2–4 min; large boards dominate (measured on Apify: 5,274 postings with descriptions from 24 boards in 47 s, SpaceX alone 2,281). Set `maxItems` and the run's charge limit together: a 10,000-job request with a $4 limit stops at ~5,000 jobs. A slug with no board on any ATS is reported in the status message under "no board found", not treated as a failure.

### Limitations

- Only Greenhouse, Lever and Ashby boards; other ATSes (Workday, SmartRecruiters, iCIMS, …) are not supported.
- Greenhouse's public API has no salary and no native workplace/employment type (both are derived from location strings and per-board custom metadata, so some boards stay null); Lever's `salaryRange` and Ashby's `compensation` are present only when the company chooses to publish them.
- `locations` strings are passed through as the ATS writes them; they are not geocoded or normalised to country/city.

### Compliance

All three APIs are unauthenticated and documented as public: Greenhouse ("Job Board data is publicly available, so authentication is not required"), Lever (published postings "may be scraped by third parties"), Ashby (public job-posting API). No login, no personal data beyond what the company publishes about its own openings.

# Actor input Schema

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

Company board slugs or URLs (max 500). Accepted: a bare slug ("stripe" — all three ATSes are tried), "<ats>:<slug>" ("lever:spotify"), or any boards.greenhouse.io / job-boards.greenhouse.io / jobs.lever.co / jobs.ashbyhq.com URL. The slug is the path segment after the host on the company's careers page.

## `ats` (type: `array`):

Only query these ATSes when auto-detecting bare slugs (greenhouse, lever, ashby). Empty = all three.

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

Keep the full job description (HTML and plain text) on every row. Turn off for a lighter dataset.

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

Stop after this many jobs have been pushed (1–100000). You are only charged for pushed jobs.

## `maxConcurrency` (type: `integer`):

Parallel requests (1–10). Requests to each API host are additionally spaced ~1 s apart.

## `proxyConfiguration` (type: `object`):

Proxy settings. The ATS APIs answer datacenter IPs fine; leave empty unless you see blocks.

## Actor input object example

```json
{
  "companies": [
    "stripe",
    "lever:spotify",
    "https://jobs.ashbyhq.com/openai"
  ],
  "includeDescriptions": true,
  "maxItems": 500,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Dataset items, one per job posting (ats, company, title, locations, workplace type, department, employment type, compensation, description, timestamps, URLs).

# 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": [
        "greenhouse:figma",
        "greenhouse:cloudflare",
        "lever:palantir",
        "lever:spotify",
        "ashby:notion",
        "ashby:ramp"
    ],
    "maxItems": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("ardent_fork/ats-job-boards").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": [
        "greenhouse:figma",
        "greenhouse:cloudflare",
        "lever:palantir",
        "lever:spotify",
        "ashby:notion",
        "ashby:ramp",
    ],
    "maxItems": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("ardent_fork/ats-job-boards").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": [
    "greenhouse:figma",
    "greenhouse:cloudflare",
    "lever:palantir",
    "lever:spotify",
    "ashby:notion",
    "ashby:ramp"
  ],
  "maxItems": 500
}' |
apify call ardent_fork/ats-job-boards --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ardent_fork/ats-job-boards"
        }
    }
}
```

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/GQ87Ga5LDMYEePKNE/builds/ebOx9clPUDFYoNGKc/openapi.json