# Greenhouse & Lever Jobs Scraper (`battles_2026/greenhouse-lever-jobs-scraper`) Actor

Read public job postings from Greenhouse- and Lever-hosted job boards via their official public APIs: 21 normalized fields per job, deduplicated, schema-validated.

- **URL**: https://apify.com/battles_2026/greenhouse-lever-jobs-scraper.md
- **Developed by:** [Jonathan D Battles](https://apify.com/battles_2026) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 job scrapeds

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

**Get every open job (set `maxJobs`; it defaults to 20 per run) from any company's Greenhouse or Lever careers page as clean JSON, CSV or Excel. $1.50 per 1,000 unique jobs; duplicates and empty rows are free.** Built on the official public job-board APIs: no login, no proxies, no browser.

### Who uses it

- Recruiters and staffing agencies tracking which companies are hiring
- Sales teams using new job posts as buying signals (e.g. a company hiring 5 data engineers)
- Job boards and aggregators that need a clean, deduplicated feed
- Analysts studying hiring trends, salaries and remote-work share

### What it does

Reads public job postings from job boards hosted on Greenhouse and Lever through their
official public job-board APIs (`boards-api.greenhouse.io`, `api.lever.co`) and returns one
clean, 21-field record per job: title, company, locations, department, team, employment type,
workplace type, salary, description (HTML and text), dates, URLs and metadata.

### Why it is different

- Pay only for unique, non-empty jobs. Duplicates, invalid rows and empty rows are free.
- Every record is checked against the output schema before it is saved.
- Polite by design: honours robots.txt, `Crawl-delay`, HTTP 429 and `Retry-After`; at most
  1–2 requests per second per host. It stops and reports on any captcha; it never bypasses one.
- If a host answers HTTP 429 with a `Retry-After` longer than our cap, that host is stopped for the
  rest of the run, which stops **every board on that host** (e.g. all `boards.greenhouse.io` boards).
  The stopped host is listed under `blocked_hosts` in the `RUN_SUMMARY`; rerun later for those boards.
- Every run saves a `RUN_SUMMARY` (counts, latency p50/p95, failure modes, suggestions) and an
  `EVIDENCE` record to the key-value store.

### Input

```json
{ "boards": [{ "platform": "lever", "token": "leverdemo" },
             { "platform": "greenhouse", "token": "stripe" }],
  "maxJobs": 20 }
```

`token` is the part after `jobs.lever.co/` or `boards.greenhouse.io/`. Optional:
`includeDescription`, `fetchDetails` (Greenhouse pay ranges, one extra request per job),
`concurrency`, `rateLimitStrategy` (`polite` or `balanced`), `outputFormat`, `errorPolicy`.

### How much does it cost to scrape Greenhouse and Lever jobs?

Pay per event: **$0.0015 per unique, valid job ($1.50 per 1,000)**. Duplicates, invalid rows and
empty rows are never charged. Example: 40 boards with about 50 open jobs each = 2,000 jobs = **$3.00**.
Set a maximum charge on the run and the actor stops exactly at it.

### Output example

```json
{
  "id": "greenhouse:stripe:6912345",
  "source": "greenhouse",
  "sourceJobId": "6912345",
  "boardToken": "stripe",
  "company": "Stripe",
  "title": "Backend Engineer, Payments",
  "url": "https://boards.greenhouse.io/stripe/jobs/6912345",
  "applyUrl": null,
  "locations": ["Dublin, Ireland"],
  "country": null,
  "department": "Engineering",
  "team": null,
  "employmentType": null,
  "workplaceType": "hybrid",
  "descriptionText": "...",
  "postedAt": "2026-10-01T09:00:00Z",
  "updatedAt": "2026-10-08T12:00:00Z",
  "salary": null,
  "metadata": {},
  "scrapedAt": "2026-10-12T05:00:00Z"
}
```

(Illustrative values. Run the actor for live data.)

### FAQ

**Is it legal?** Lever's Postings API docs state published postings "may be scraped by third
parties". Greenhouse states its job-board data is public and needs no authentication for GET
requests. The actor only reads public data, never submits applications, and never calls the
`/embed/` paths that Greenhouse's robots.txt disallows. You are responsible for how you use the
data; employers' own careers-site terms may restrict republication. Not legal advice.

**Is it affiliated with Greenhouse or Lever?** No. It reads boards hosted on those platforms.

**Does the output contain personal data?** The actor does not extract personal-data fields
(no recruiter names, emails or phone numbers are parsed into their own columns). However, the
free-text job descriptions (`descriptionText`, `descriptionHtml`) are copied as the employer
published them and may contain personal data, such as a recruiter's or hiring manager's name
or email address. If you store or process that text, you are responsible for handling it
lawfully under the GDPR, CCPA and other applicable privacy laws (for example: have a lawful
basis, minimise or strip it if you don't need it, and honour deletion requests).

### Related actors

- [UK Late Payers & Payment Practices Scraper](https://apify.com/battles_2026/uk-late-payer-signals)
- [SEC Subsidiaries & Major Customers Scraper (EDGAR)](https://apify.com/battles_2026/sec-subsidiary-map-concentration-risk)

# Changelog

This Actor's version history is a separate document: https://apify.com/battles_2026/greenhouse-lever-jobs-scraper/changelog.md

# Actor input Schema

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

Boards to read, e.g. \[{"platform": "greenhouse", "token": "stripe"}, {"platform": "lever", "token": "leverdemo"}]. token is the Greenhouse board token or Lever site name (the part after jobs.lever.co/ or boards.greenhouse.io/).

## `maxJobs` (type: `integer`):

Cap on jobs per board (default 20, keeps test runs small). Raise it for full boards.

## `includeDescription` (type: `boolean`):

Include descriptionHtml/descriptionText. Off sets both to null.

## `fetchDetails` (type: `boolean`):

One extra request per Greenhouse job to read pay ranges (pay_transparency=true). Lever lists already include salaryRange.

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

Maximum parallel requests per host (capped by the rate strategy; Lever and Greenhouse are also held to >= 1 s between requests).

## `rateLimitStrategy` (type: `string`):

How fast to read each host. There is no faster mode by design. All strategies honour robots.txt Crawl-delay, HTTP 429 and Retry-After.

## `outputFormat` (type: `string`):

Where and how records are written.

## `errorPolicy` (type: `string`):

fail-fast stops on the first error; best-effort records it and continues.

## Actor input object example

```json
{
  "boards": [
    {
      "platform": "lever",
      "token": "leverdemo"
    }
  ],
  "maxJobs": 20,
  "includeDescription": true,
  "fetchDetails": false,
  "concurrency": 5,
  "rateLimitStrategy": "polite",
  "outputFormat": "dataset",
  "errorPolicy": "best-effort"
}
```

# Actor output Schema

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

All job rows in the overview view.

## `summary` (type: `string`):

Counts, charged/free rows, latency, failure modes, blocked hosts and rows per board.

# 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 = {
    "boards": [
        {
            "platform": "lever",
            "token": "leverdemo"
        }
    ],
    "maxJobs": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("battles_2026/greenhouse-lever-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 = {
    "boards": [{
            "platform": "lever",
            "token": "leverdemo",
        }],
    "maxJobs": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("battles_2026/greenhouse-lever-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 '{
  "boards": [
    {
      "platform": "lever",
      "token": "leverdemo"
    }
  ],
  "maxJobs": 20
}' |
apify call battles_2026/greenhouse-lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,battles_2026/greenhouse-lever-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/3I3MNl3M9GLPS3KOB/builds/RXoeOvRaZXgEhc1qx/openapi.json