# Greenhouse & Lever Jobs Scraper | Structured JSON Export (`verrr/ats-jobs-scraper`) Actor

Scrape job postings from any public Greenhouse or Lever careers board. One clean JSON record per job with company, title, location, department, employment type, full description text, posted and updated dates, and the apply link. Works from board names, no login and no proxy needed.

- **URL**: https://apify.com/verrr/ats-jobs-scraper.md
- **Developed by:** [VER RR](https://apify.com/verrr) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 job results

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

## Greenhouse & Lever Jobs Scraper | Structured JSON Export

Scrape job postings from any public Greenhouse or Lever careers board and get one clean, identically shaped JSON record per job: company, title, location, department, employment type, full description text, posted and updated dates, and the apply link.

### What data you get

- `id`: the job's ID on its board (string, unique within a board and source).
- `source`: `greenhouse` or `lever`.
- `board`: the board token or company slug you entered, so you can group and re-query.
- `company`: company name. Greenhouse returns it; for Lever it is derived from the slug (`big-co` becomes `Big Co`).
- `title`: job title.
- `location`: location text as the board shows it, or `null`.
- `department`: department (Greenhouse: first listed department, Lever: department), or `null`.
- `employmentType`: for example `Full-time`. Lever publishes it. Greenhouse only publishes it on boards that add an employment-type custom field, so it is often `null`.
- `url`: the public job page.
- `description`: the full posting as plain text (HTML removed, lists kept as `-` lines).
- `postedAt`: first publication date, ISO 8601 UTC.
- `updatedAt`: last update date, ISO 8601 UTC. Greenhouse only. Lever does not publish it, so it is always `null` for Lever.

Every record has all twelve keys. Missing values are `null`, never omitted.

### Input

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `boards` | array of strings | yes | - | Greenhouse board tokens or Lever company slugs (1 to 200). From `boards.greenhouse.io/stripe` use `stripe`, from `jobs.lever.co/spotify` use `spotify`. |
| `source` | string | no | `auto` | `auto` tries each board on Greenhouse and Lever and keeps the one that exists. `greenhouse` or `lever` skips the other lookup. |
| `maxItems` | integer | no | 1000 | Stop after this many jobs across all boards (1 to 100,000). Also your spending cap. |

### Pricing

Pay-Per-Event:

| Event | Price |
|---|---|
| `job-result` | $2.00 per 1,000 jobs ($0.002 per job) |

You are charged once for each job saved to the dataset, and nothing else. Boards that do not exist, failed requests and jobs beyond `maxItems` are not charged.

Free plan: up to 100 jobs per run. When the cap is reached the Actor logs `Free tier limit reached; upgrade for full export` and finishes cleanly.

### Sample output

Shortened description for readability; the real field holds the whole posting.

```json
{
  "id": "30ccddec-5437-4eb3-9294-5ecd86996281",
  "source": "lever",
  "board": "rover",
  "company": "Rover",
  "title": "Business Analyst, Finance Analytics",
  "location": "Seattle",
  "department": "Accounting & Finance",
  "employmentType": "Full-time",
  "url": "https://jobs.lever.co/rover/30ccddec-5437-4eb3-9294-5ecd86996281",
  "description": "Who we are:\nAt Rover, pets and their people are at the heart of everything we do. We connect pet parents with trusted pet care across the U.S., Canada, Europe, and Australia.\n...",
  "postedAt": "2026-10-15T16:54:42.011Z",
  "updatedAt": null
}
```

### Integrations

Call it from n8n, Make or Zapier with the Apify integration, or via the Apify API (replace `VERRR` with the Actor owner's username shown on this page's API tab):

```bash
curl -X POST "https://api.apify.com/v2/acts/VERRR~ats-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{ "boards": ["<board-name>"], "maxItems": 100 }'
```

Schedule it daily and compare `id` values with the previous run to find new postings, or watch `updatedAt` for changed ones.

### Use cases

- Greenhouse jobs scraper for recruiting and sourcing pipelines: pull every open role of the companies you track.
- Lever jobs scraper for market research: count openings by department and location over time.
- Job board and aggregator feeds: normalized records from many companies with one input list.
- New-jobs alerts: run on a schedule and send fresh `id` values to Slack, email or a spreadsheet.
- Hiring-signal data for sales and investors: which companies are growing which teams.

### Limits and FAQ

- **Which systems are covered?** Greenhouse and Lever, through their public job-board APIs. Workday and Ashby are not covered yet.
- **How do I find a board name?** Open the company's careers page. If the job links go to `boards.greenhouse.io/<name>` or `job-boards.greenhouse.io/<name>` (Greenhouse) or `jobs.lever.co/<name>` (Lever), `<name>` is what you enter. Careers pages on a company's own domain often embed one of these, and the job links show which.
- **What if a board name is wrong?** The Actor logs a warning for that board and carries on with the others. If no board returns any job, the run fails with a clear message instead of reporting a silent empty success.
- **Does it filter by keyword, location or date?** No. It returns every open job on each board; filter the dataset afterwards.
- **Does Lever's EU region work?** Not yet. Only boards served from the main Lever API are supported.
- **Do I need a proxy or login?** No. Both APIs are public and unauthenticated.
- **How big can a board be?** Each board is fetched in a single request. Very large boards (thousands of postings, tens of MB) work but can take a couple of minutes.
- **What if the API changes?** This Actor is monitored weekly and repaired automatically.

### Legal note

This Actor collects publicly available data only. You are responsible for using the output in compliance with applicable laws and the target site's terms.

# Actor input Schema

## `boards` (type: `array`):

Required. Greenhouse board tokens or Lever company slugs, one per entry. Take it from the careers URL: boards.greenhouse.io/stripe or job-boards.greenhouse.io/stripe gives "stripe", jobs.lever.co/spotify gives "spotify".

## `source` (type: `string`):

Which job-board system to read. "auto" tries every board on both Greenhouse and Lever and keeps the one that exists. Pick one system to skip the other lookup.

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

Stop after this many jobs across all boards. Each saved job is billed once, so this is also your spending cap. Free-plan runs are limited to 100 jobs.

## Actor input object example

```json
{
  "boards": [],
  "source": "auto",
  "maxItems": 1000
}
```

# Actor output Schema

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

All job postings found on the requested boards: id, source, board, company, title, location, department, employmentType, url, description, postedAt, updatedAt.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("verrr/ats-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("verrr/ats-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 '{}' |
apify call verrr/ats-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,verrr/ats-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/BrY1LPvFl7fVZdAbl/builds/HKPdtJq6p5WuI51JA/openapi.json