# Lever Job Board Scraper (`sourcesauce/lever-job-feeds`) Actor

Fresh job postings straight from Lever-hosted career pages. Full posting content, team, location, commitment and dates for any company on Lever - compliance-safe output with no personal contact data. Ideal for job-board backfill and hiring-trend analysis.

- **URL**: https://apify.com/sourcesauce/lever-job-feeds.md
- **Developed by:** [Source Sauce](https://apify.com/sourcesauce) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 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.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Lever Job Board Scraper

Pull fresh job postings from any **Lever-hosted career page** — the same public
Postings API behind `jobs.lever.co` company sites. Give it a list of company board
tokens and get every open role as structured records with the full posting HTML and
structured salary ranges, straight from the source with no database staleness.

Sample output (live run, 2026-08-04):

| board\_token | title | location | workplace\_type | salary\_range | created\_at |
|---|---|---|---|---|---|
| palantir | Administrative Business Partner | London, United Kingdom | hybrid | - | 2024-03-25 |
| qonto | Anti-Financial Crime Officer (France) | Paris | hybrid | - | 2026-02-26 |
| zoox | Autonomy System Test Engineer | Foster City, CA | hybrid | USD 143,000-177,000 | 2026-05-04 |

Built for **job board backfill**, job aggregator feeds, **hiring trend analysis**,
competitor hiring monitoring, and jobs-posted-by-company datasets. One board = one
company; a watchlist of tokens gives you a daily multi-company feed of open positions.

### Why this one

- **Direct from the API, every run.** No cached database between you and the source —
  `created_at` and the posting body come from Lever itself, so freshness is the API's,
  not a crawler's.
- **Structured salary data.** Lever publishes `salaryRange` (currency, interval, min,
  max) on postings that carry it — delivered as a structured object, not text to parse.
- **Compliance-safe by construction.** No hiring-manager names, no AI-extracted contact
  enrichment, no personal data fields — email addresses, phone numbers AND personal
  profile links inside posting text are redacted before delivery. The output schema is
  a fixed allowlist you can audit below.
- **Honest billing.** You pay per delivered job posting. Unknown or dead board tokens
  return an uncharged error row instead of failing the run, so long watchlists are safe.
- **Polite to the source.** Fetches honor the API host's published crawl delay.

### Output

| field | type | description |
|---|---|---|
| board\_token | string | The Lever board the posting came from (your input token). |
| id | string | Lever posting id (UUID). |
| title | string | Posting title. |
| team | string or null | Team, as the employer categorized it. |
| department | string or null | Department, when the employer sets one. |
| location | string or null | Primary location line. |
| all\_locations | array of strings | Every location the employer listed. |
| commitment | string or null | Employment type (e.g. Full-time). |
| country | string or null | ISO country code. |
| workplace\_type | string or null | on-site, hybrid or remote. |
| created\_at | string (ISO datetime) | When the posting was created. |
| salary\_range | object or null | `{currency, interval, min, max}` when published. |
| posting\_url | string | The public posting page (`jobs.lever.co/...`). |
| apply\_url | string | The public application URL. |
| content | string (HTML) | Full posting body — intro, all sections, closing and salary text — renderable HTML, contacts redacted. |
| content\_chars | integer | Length of the delivered content. |

### Input

| field | required | prefill | description |
|---|---|---|---|
| boardTokens | yes | palantir, qonto, zoox | Lever board tokens — the company slug in career-page URLs like `jobs.lever.co/palantir`. |
| maxRecords | no | 150 | Stop after this many rows in total (0 = no cap). |

**Finding a board token:** open the company's careers page; if applications go through
Lever the URL contains `jobs.lever.co/<token>`. The token is usually the company name
in lowercase.

### Notes

- A board token that is not on Lever returns one **uncharged** error row naming the
  token, and the rest of the watchlist still delivers.
- A company with zero published roles is a valid empty result, not an error (measured:
  roughly a third of live Lever boards have no open published postings on a given day).
- Postings are delivered per run (stateless). Dedupe across runs on `id` or
  `posting_url` on your side.

***

This is an **unofficial** tool and is **not affiliated** with, endorsed or sponsored by
Lever (Employ Inc.). It reads only the public, unauthenticated Lever Postings API and
delivers employer-published job postings.

# Actor input Schema

## `boardTokens` (type: `array`):

Lever board tokens — the company slug in careers URLs like jobs.lever.co/palantir. One board = one company. Unknown tokens return an uncharged error row, so a long watchlist is safe.

## `maxRecords` (type: `integer`):

Stop after this many rows in total (0 = no cap). Postings are charged per delivered record.

## Actor input object example

```json
{
  "boardTokens": [
    "palantir",
    "qonto",
    "zoox"
  ],
  "maxRecords": 150
}
```

# 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 = {
    "boardTokens": [
        "palantir",
        "qonto",
        "zoox"
    ],
    "maxRecords": 150
};

// Run the Actor and wait for it to finish
const run = await client.actor("sourcesauce/lever-job-feeds").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 = {
    "boardTokens": [
        "palantir",
        "qonto",
        "zoox",
    ],
    "maxRecords": 150,
}

# Run the Actor and wait for it to finish
run = client.actor("sourcesauce/lever-job-feeds").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 '{
  "boardTokens": [
    "palantir",
    "qonto",
    "zoox"
  ],
  "maxRecords": 150
}' |
apify call sourcesauce/lever-job-feeds --silent --output-dataset

```

## MCP server setup

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

```

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/eLGEnSKhoZy97z2ui/builds/gwe6bk3axMVSXbgbL/openapi.json