# Lever Jobs Scraper — Job Boards & Postings (`tortuga/lever-jobs-scraper`) Actor

Scrape Lever jobs from any Lever job board (jobs.lever.co) or company career site built on Lever. Every job posting with title, team, location, commitment, salary, posted date, full description and apply URL; filter by keyword, location or team. Monitor new job postings on a schedule.

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

## Pricing

$1.50 / 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

## Lever Jobs Scraper: Job Boards & Postings

Scrape Lever jobs from any Lever job board (jobs.lever.co) or company career site built on Lever. Paste board links, a single posting, or a company's careers page, and the Actor reads Lever's **public postings API** and returns one clean row per job posting: title, company, department and team, locations and country, remote / hybrid / on-site, commitment, **salary range** when the company publishes one, posted date, job and apply links, and the **full description**. Filter by keyword, location or team, and monitor new job postings on a schedule.

No login, no API key, no browser: it is the same JSON feed that companies use to embed their Lever job board on their own websites, so runs finish in seconds and cost a fraction of a cent per job. EU boards (`jobs.eu.lever.co`) are handled automatically.

Typical uses: job alerts for target companies, hiring signals for sales and recruiting (who is hiring which roles, where), salary benchmarking, and feeding a job board or an LLM pipeline with Lever job postings.

### What data does Lever Jobs Scraper extract?

| Field | Description |
|---|---|
| `jobId`, `atsJobId` | Stable unique id `lever:<board>:<posting id>` and Lever's own posting id |
| `ats` | Always `lever` (the row layout matches our Career Site Jobs Scraper, so the two can be mixed) |
| `companyName`, `companySlug`, `careerSiteUrl` | Company name as the board page shows it (e.g. "Octopus Energy Group"), board slug and board URL |
| `title` | Job title |
| `department`, `team` | Lever's department and team categories (department falls back to the team) |
| `location`, `locations` | Location as the company writes it, plus every location of multi-location postings |
| `country`, `countryCode` | ISO country from Lever's own country field, or read from the location text |
| `workplaceType`, `isRemote`, `isHybrid` | `remote` / `hybrid` / `onsite` as the company set it in Lever (null when unspecified), plus flags |
| `employmentType` | Lever's commitment: Full-time, Part-time, Contract, Internship, Fixed Term Contract ... |
| `seniority` | Lever's level category, when the company uses it |
| `salaryText`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salarySource` | Pay range from Lever's salary-range field (`salarySource: "ats"`) or the first pay range written in the description (`"description"`, e.g. "$164,000 - $261,500 annually") |
| `postedAt` | When the posting was published (UTC, ISO 8601) |
| `url`, `applyUrl` | Posting page and application form on jobs.lever.co |
| `description`, `descriptionHtml` | Full description (opening, body, bullet lists, closing section) as readable text and as HTML |
| `sourceUrl`, `scrapedAt` | Which input produced the job, and when |
| `changeType` | `new` in monitoring mode (see below) |

Lever's API does not name the company, so the Actor reads the name from the board page's title ("Octopus Energy Group" for `octoenergy`, "Palantir Technologies" for `palantir`); a name you pass with a slug (`{"slug": "octoenergy", "companyName": "Octopus Energy"}`) or the site name of the careers page the board was found on wins, and if the board page cannot be read the slug is written out ("Octoenergy").

### How to scrape Lever jobs

1. Paste URLs into **Lever job board or careers page URLs**: `https://jobs.lever.co/palantir`, `https://jobs.lever.co/octoenergy`, a single posting such as `https://jobs.lever.co/palantir/6ed76ce8-4156-4b60-b120-403538bd66cd` (the whole board is scraped), or a company careers page / homepage.
2. Or list boards you already know under **Lever company slugs**: `palantir`, `octoenergy`, `eu/acme` for a board on Lever's EU instance.
3. Optional filters: **Title keywords**, **Locations**, **Departments / teams**, **Remote jobs only**, **Posted within (days)**, **Max jobs per company**, **Max jobs (total)**.
4. Click **Start**. Jobs appear in the **Output** tab, newest first per company; export JSON, CSV or Excel, or read them through the API.

### Input example

```json
{
  "startUrls": [
    { "url": "https://jobs.lever.co/palantir" },
    { "url": "https://jobs.lever.co/octoenergy" }
  ],
  "boards": ["eu/acme"],
  "keywords": ["engineer", "product manager"],
  "locations": ["London", "Remote"],
  "postedWithinDays": 14,
  "includeDescription": true,
  "maxItemsPerCompany": 50,
  "maxItems": 500
}
```

### Output example

```json
{
  "jobId": "lever:palantir:bd7766c4-6aea-4b37-8d47-a8864bb9bd69",
  "atsJobId": "bd7766c4-6aea-4b37-8d47-a8864bb9bd69",
  "ats": "lever",
  "companyName": "Palantir Technologies",
  "companySlug": "palantir",
  "title": "Finance Operator Intern",
  "department": "Finance",
  "team": "Finance",
  "location": "New York, NY",
  "locations": ["New York, NY"],
  "country": "United States",
  "countryCode": "US",
  "isRemote": false,
  "isHybrid": true,
  "workplaceType": "hybrid",
  "employmentType": "Internship",
  "seniority": null,
  "salaryText": "$135,000 - $200,000",
  "salaryMin": 135000,
  "salaryMax": 200000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salarySource": "description",
  "postedAt": "2026-10-31T00:15:34Z",
  "url": "https://jobs.lever.co/palantir/bd7766c4-6aea-4b37-8d47-a8864bb9bd69",
  "applyUrl": "https://jobs.lever.co/palantir/bd7766c4-6aea-4b37-8d47-a8864bb9bd69/apply",
  "careerSiteUrl": "https://jobs.lever.co/palantir",
  "description": "A World-Changing Company\n\nPalantir builds the world’s leading software for data-driven decisions and operations. By bringing the right data to the people who need it, our platforms empower our partners to develop lifesaving drugs, ...",
  "descriptionHtml": "<div><strong><span style=\"font-size: 18px;\">A World-Changing Company</span></strong></div> ...",
  "sourceUrl": "https://jobs.lever.co/palantir",
  "scrapedAt": "2026-11-01T18:50:18Z"
}
```

A posting whose company filled in Lever's salary-range field carries it as `"salaryText": "€50,000 - 57,000 per year"`, `"salaryMin": 50000`, `"salaryMax": 57000`, `"salaryCurrency": "EUR"`, `"salaryPeriod": "year"`, `"salarySource": "ats"` (Octopus Energy, Senior Financial Accountant); the Palantir example above has its range read from the description text instead.

### Which Lever URLs work?

- **Board**: `https://jobs.lever.co/<company>` and `https://jobs.eu.lever.co/<company>` (Lever's EU instance). If a company moved to the EU instance, the Actor finds that out by itself.
- **Posting**: `https://jobs.lever.co/<company>/<posting id>` or its `/apply` page: the whole board is scraped, use the filters to narrow it.
- **API**: `https://api.lever.co/v0/postings/<company>` links copied from an embed script.
- **Company website**: a careers page or homepage. The Actor opens it, looks for Lever links, iframes and embed scripts, follows the "Careers" / "Jobs" link and tries `/careers` and `/jobs` (at most 4 pages). The run's `SUMMARY` (Storage → Key-value store) lists, per input, which board was found and where; sites without a Lever board are reported there and skipped, at no charge.

Wrong or expired slugs are reported in `SUMMARY.notes.boardsNotFound`. A board that returns no postings at all (Lever answers an empty list for some unknown slugs) shows `listed: 0` for that company.

### Does it need a login or API key?

No. Lever publishes every public job board through its unauthenticated postings API so companies can show their jobs on their own websites; the Actor reads that feed and nothing else. No account, no API key, no cookies, no browser. Internal or unlisted postings, candidate data and anything behind a login are never touched.

### Monitor new Lever jobs on a schedule

Turn on **Only new jobs (monitoring)** and save the input as a task with a Schedule (Apify Console → Schedules), e.g. every morning. Each run remembers the jobs that earlier runs of the same input returned and outputs only postings that are **new** since then, with `changeType: "new"`; jobs seen before are not output and not charged. With **Max jobs per company**, monitoring watches that many newest postings per board. Use **Monitoring key** to keep several schedules on the same companies apart. This is the cheapest way to get job alerts or hiring signals for a list of companies that hire through Lever.

### Pricing

Pay per event, no subscription: **$0.0015 per job** saved, every field above and the full description included. Platform usage is included in that price, so 1,000 Lever jobs cost $1.50 and nothing else. Monitoring runs charge only for new jobs; inputs that point to no Lever board cost nothing.

### Proxy note

Lever's API is public, so the Actor connects to it directly (no proxy), which is also by far the fastest: through a datacenter proxy the same API streams very slowly. A proxy you configure is used only to open company careers pages. No residential proxy and no Unblocker are ever needed.

### Integrations and API

Use the results in Make, Zapier, n8n, Google Sheets, Airtable or your CRM, or call the Actor from Python / Node.js with the Apify client (see the **API** tab). A Schedule plus monitoring gives you a daily feed of new postings at the companies you follow.

### Is it legal to scrape Lever job boards?

The Actor reads only job postings that companies publish openly on their Lever job boards through Lever's public postings feed. It does not log in, does not collect candidate or employee data, and does not access anything hidden or internal. Recruiter names that a company chooses to print in a posting stay part of that description. You are responsible for how you use the data and for complying with the sites' terms and applicable law (e.g. the GDPR).

### Support

A board that does not work, a missing field, another ATS? Open an issue in the **Issues** tab; it is usually answered within a day. Greenhouse, Ashby, Workday, Workable, SmartRecruiters, Recruitee, Personio and Teamtailor boards are covered by our Career Site Jobs Scraper, which returns the same row layout.

### Related scrapers

- [Ashby Jobs Scraper](https://apify.com/tortuga/ashby-jobs-scraper): Job Boards & Postings
- [Workday Jobs Scraper](https://apify.com/tortuga/workday-jobs-scraper): Company Career Sites
- [Career Site Jobs Scraper](https://apify.com/tortuga/career-site-jobs-scraper): Greenhouse, Lever, Workday & Ashby
- [Greenhouse Jobs Scraper](https://apify.com/tortuga/greenhouse-jobs-scraper): Job Boards & Postings

### Found it useful?

A ★ review on this Actor's Apify Store page helps other users find it and tells us what to improve. Issues and feature requests are welcome in the Actor's **Issues** tab.

# Actor input Schema

## `startUrls` (type: `array`):

Lever job boards (https://jobs.lever.co/palantir, EU boards on jobs.eu.lever.co, a single posting URL scrapes its whole board, api.lever.co posting URLs work too) or a company careers page / homepage: the Actor looks for the Lever board it embeds or links to, follows the 'Careers' link and tries /careers and /jobs (at most 4 pages per site).

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

Optional: boards you already know, as the company part of the jobs.lever.co URL, e.g. palantir, octoenergy. Write eu/acme for a board on Lever's EU instance (jobs.eu.lever.co/acme); lever:palantir and full URLs are accepted too. Via the API you can also pass objects: {"slug": "palantir", "companyName": "Palantir Technologies"}.

## `keywords` (type: `array`):

Keep only jobs whose title contains at least one of these words or phrases (case-insensitive), e.g. engineer, sales, "product manager". Leave empty for all jobs.

## `locations` (type: `array`):

Keep only jobs whose location text or country contains one of these, e.g. London, Germany, US, Remote. Leave empty for all locations.

## `departments` (type: `array`):

Keep only jobs whose Lever department or team contains one of these, e.g. Engineering, Sales.

## `remoteOnly` (type: `boolean`):

Keep only jobs Lever marks as remote (or whose location says Remote).

## `postedWithinDays` (type: `integer`):

Keep only jobs posted in the last N days (Lever's posting date is exact).

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

Add the full description as plain text and HTML. Lever sends it with the job list, so this costs no extra requests and no extra charge; turn it off for a smaller dataset.

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

Stop after this many jobs in total. Keeps cost predictable.

## `maxItemsPerCompany` (type: `integer`):

Optional cap per board (newest jobs first). With monitoring on, it is the number of newest jobs watched per board.

## `onlyNewOrChanged` (type: `boolean`):

Remember what earlier runs of this input returned and output only jobs that are new since then. Use with a Schedule; jobs seen before are not output and not charged.

## `monitoringKey` (type: `string`):

Name for this watch, so several schedules on the same input stay separate; defaults to a key derived from the input.

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

Not needed: Lever's job-board API is public and direct requests are fastest, so the Actor always reads it directly (through the Apify proxy it streams very slowly). A proxy you configure here is used only to open company careers pages. No residential proxy or Unblocker is ever needed.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://jobs.lever.co/palantir"
    },
    {
      "url": "https://jobs.lever.co/octoenergy"
    }
  ],
  "remoteOnly": false,
  "includeDescription": true,
  "maxItems": 20,
  "maxItemsPerCompany": 10,
  "onlyNewOrChanged": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "startUrls": [
        {
            "url": "https://jobs.lever.co/palantir"
        },
        {
            "url": "https://jobs.lever.co/octoenergy"
        }
    ],
    "maxItems": 20,
    "maxItemsPerCompany": 10,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("tortuga/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 = {
    "startUrls": [
        { "url": "https://jobs.lever.co/palantir" },
        { "url": "https://jobs.lever.co/octoenergy" },
    ],
    "maxItems": 20,
    "maxItemsPerCompany": 10,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("tortuga/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 '{
  "startUrls": [
    {
      "url": "https://jobs.lever.co/palantir"
    },
    {
      "url": "https://jobs.lever.co/octoenergy"
    }
  ],
  "maxItems": 20,
  "maxItemsPerCompany": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call tortuga/lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

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