# Lever Jobs Scraper - jobs.lever.co to CSV & JSON (`maydit/lever-jobs-scraper`) Actor

Scrape live job postings from any Lever job board. Team, department, commitment, workplace type, location and country normalized, full descriptions as plain text. No API key.

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

## Pricing

from $0.60 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 - export jobs.lever.co boards to CSV, JSON & Excel

Scrape live job postings from any **Lever** job board (`jobs.lever.co`) and get clean, flat rows you can open in Excel, load into a sheet, or pipe into your own tooling. Give the Actor a list of Lever company slugs - or just paste the board URLs - and it returns every public posting on those boards with Lever's full category block normalized: **team, department, commitment, workplace type (remote / hybrid / onsite), location, all locations and country**, plus the full job description as readable plain text.

It talks to Lever's own public postings API (`https://api.lever.co/v0/postings/{company}?mode=json`), so there is **no API key, no login and no browser** involved. A whole board comes back in one request with no pagination, so keeping a job feed, an ATS dataset or a recruiting CRM up to date costs one request per company. Turn on **Only postings new since the last run** and a scheduled run gives you just the new roles.

This Actor covers Lever only, on purpose: one platform, done properly. If you need several ATS platforms at once (Greenhouse, Ashby, SmartRecruiters, Recruitee, Workable), use our **ATS Job Postings Scraper**.

### What you get

One row per job posting.

| Field | Type | Description |
| --- | --- | --- |
| `company` | string | The Lever company slug the posting came from. |
| `jobId` | string | Lever's posting ID (a UUID). Stable - good as a primary key. |
| `title` | string | Job title, e.g. `Senior Product Manager - User Platform`. |
| `team` | string | Lever category `team`, e.g. `Platform`. Null when the employer leaves it blank. |
| `department` | string | Lever category `department`, e.g. `Engineering`. |
| `commitment` | string | Lever category `commitment`, e.g. `Full-time`, `Permanent`, `Intern`. |
| `workplaceType` | string | `remote`, `hybrid` or `onsite`, as published by the employer. Null if not set. |
| `location` | string | Primary location, e.g. `London`. |
| `allLocations` | string | Every location on the posting, `; ` separated, e.g. `London; Stockholm`. |
| `country` | string | Two-letter ISO country code, e.g. `GB`, `US`. |
| `descriptionText` | string | The job description as plain text (up to 20,000 characters). |
| `listsText` | string | Lever's structured sections ("What You'll Do", "Responsibilities", "Who You Are"...) flattened into headed bullet lists. |
| `hostedUrl` | string | Public posting page on `jobs.lever.co`. |
| `applyUrl` | string | Direct link to the application form. |
| `createdAt` | ISO 8601 | When the posting was created (Lever returns epoch milliseconds; converted here). |
| `scrapedAt` | ISO 8601 | When this row was collected. |

A `SUMMARY` record is written to the run's key-value store with the companies requested, which ones succeeded, which returned nothing, the department / workplace-type / country breakdowns, and whether the run stopped on its time limit.

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `companies` | array of strings | `["spotify", "wealthfront", "palantir"]` | Lever company slugs or full board URLs. `spotify`, `https://jobs.lever.co/spotify` and `https://jobs.lever.co/spotify/<job-id>` all resolve to the same board. |
| `maxResultsPerCompany` | integer | `200` | Cap on rows saved per company. Postings are sorted newest first, so a low cap keeps the freshest roles. |
| `onlyNewSinceLastRun` | boolean | `false` | Save only postings not seen in an earlier run. IDs are kept in a named key-value store (`lever-jobs-baseline`). The first run per company records the baseline and returns everything. |
| `maxRunSeconds` | integer | `240` | Wall-clock budget. On reaching it the Actor stops cleanly, keeps what it saved and logs what it skipped, instead of dying on a timeout. |

The slug is the path segment in `https://jobs.lever.co/<slug>`. A slug with no Lever board returns HTTP 404; that company is reported in the log and in `SUMMARY` and the run continues with the rest. If every company fails, the run fails loudly with the reason rather than handing you an empty dataset.

### Example output

A real row from a default run (description and section text truncated here for readability):

```json
{
  "company": "wealthfront",
  "jobId": "4d469c84-f50e-479f-bc29-80b573cd6336",
  "title": "Market Commentary Writer + Social Editor",
  "team": "Communications",
  "department": "Communications",
  "commitment": "Full-time",
  "workplaceType": "remote",
  "location": "San Francisco, CA",
  "allLocations": "San Francisco, CA; New York City, NY",
  "country": "US",
  "descriptionText": "Opportunity:\nWealthfront is looking for an experienced financial writer and/or editor (or audio reporter/producer with writing experience) to support our growing market commentary vertical and newsletter... [truncated here]",
  "listsText": "Responsibilities:\n- Monitor market and macroeconomic news daily and generate high-quality, timely content ideas that help young professionals navigate market trends and build their financial confidence... [truncated here]",
  "hostedUrl": "https://jobs.lever.co/wealthfront/4d469c84-f50e-479f-bc29-80b573cd6336",
  "applyUrl": "https://jobs.lever.co/wealthfront/4d469c84-f50e-479f-bc29-80b573cd6336/apply",
  "createdAt": "2026-09-16T17:42:52.563Z",
  "scrapedAt": "2026-09-24T00:50:57.581Z"
}
```

### FAQ

**How do I find a company's Lever slug?**
Open the company's careers page. If the postings live on `jobs.lever.co/<something>`, that `<something>` is the slug. You can paste the whole URL into `companies` - the Actor extracts the slug itself.

**The company I want returns "no Lever board". What now?**
Not every employer uses Lever, and a 404 from `api.lever.co` means exactly that: there is no Lever board under that slug. Check the careers page to see which ATS the employer actually uses. For example, Thumbtack's public board is on Ashby, not Lever (checked 2026-09-23) - our *ATS Job Postings Scraper* covers Ashby, Greenhouse, SmartRecruiters, Recruitee and Workable.

**A company responded but returned zero postings. Is that a bug?**
No. Lever answers `200` with an empty list when the board exists but has nothing public right now. That case is logged and listed in `SUMMARY` under `companiesWithNoPostings`, so it is easy to tell apart from a wrong slug.

**How do I get only new jobs on a schedule?**
Set `onlyNewSinceLastRun` to `true` and schedule the Actor. The first run records every posting ID it sees and returns them all; later runs return only postings that were not in the baseline. A run with nothing new finishes successfully with an empty dataset.

**How fast is it, and how many companies can I pass?**
One HTTP request per company, no pagination, plus the one-second crawl delay that `api.lever.co/robots.txt` publishes. On 2026-09-23 the default three-company run saved 298 postings end to end in 4 to 7 seconds across repeated runs (Lever's own response time is the variable part). Board sizes change day to day, so treat that as the shape of it rather than a fixed number. Budget roughly a second per extra company, and raise `maxRunSeconds` (and the run timeout in Run options) for long lists so the run is not cut short.

**Does it return salary data?**
Only if the employer publishes it in the description text - Lever's public postings API does not expose a structured salary field on these boards, so this Actor does not invent one.

### Data source / access / limits

- **Source:** Lever's public postings API, `https://api.lever.co/v0/postings/{company}?mode=json`. This is the same feed that renders a company's public `jobs.lever.co` board.
- **Access:** no API key, no account and no cookies. Only postings the employer has made public are returned; nothing behind a login is touched.
- **Coverage:** Lever boards only. Companies on other ATS platforms are out of scope for this Actor by design.
- **Freshness:** whatever the board shows at the moment of the run. `createdAt` is the posting's creation time from Lever; `scrapedAt` is when the row was collected.
- **Rate limits and robots:** `api.lever.co/robots.txt` allows this path and publishes `Crawl-delay: 1`, which the Actor honours by waiting a second between companies. Lever documents no request quota for this endpoint. The Actor sends one request per company and retries `429` and `5xx` responses with exponential backoff.
- **Billing:** this Actor is paid per result on the Apify platform - you are charged for the rows it saves. The `maxResultsPerCompany` cap and `onlyNewSinceLastRun` both exist so you can keep that number where you want it.
- **Your responsibility:** job postings are published by employers for public consumption, but how you store and use the data (including any personal data in a description) is up to you and your jurisdiction.

# Actor input Schema

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

One entry per company. Paste the Lever company slug or the full board URL - both work. The slug is the path segment in https://jobs.lever.co/<slug> (for example 'spotify'); links to a single posting such as https://jobs.lever.co/spotify/<job-id> are accepted too and the slug is taken from them. A slug with no Lever board returns HTTP 404 and is reported per company rather than failing the whole run.

## `maxResultsPerCompany` (type: `integer`):

Upper bound on rows saved for each company. Postings are sorted newest-created first, so a low cap keeps the freshest roles. Lever returns a whole board in a single response, so raising this costs almost no extra time - a 900-posting board is still one request.

## `onlyNewSinceLastRun` (type: `boolean`):

Save only postings this Actor has not seen before. Job IDs from each successful board are recorded in a named key-value store ('lever-jobs-baseline') and compared on the next run with this option enabled. The FIRST run for a company has no baseline, so it returns every posting and records the baseline; from the second run on you get only new ones. A run with nothing new finishes successfully with an empty dataset.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget for the crawl. When it is reached the Actor stops cleanly, keeps everything already saved, and logs which companies it did not reach - instead of being killed with a failed run. Raise it when you pass a long list of companies.

## Actor input object example

```json
{
  "companies": [
    "spotify",
    "wealthfront",
    "palantir"
  ],
  "maxResultsPerCompany": 200,
  "onlyNewSinceLastRun": false,
  "maxRunSeconds": 240
}
```

# Actor output Schema

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

One row per job posting from each Lever board, with team, department, commitment, workplace type and location.

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

Totals for the run, including how many records were requested versus returned and whether the run stopped early on its time budget.

# 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": [
        "spotify",
        "wealthfront",
        "palantir"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/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 = { "companies": [
        "spotify",
        "wealthfront",
        "palantir",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("maydit/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 '{
  "companies": [
    "spotify",
    "wealthfront",
    "palantir"
  ]
}' |
apify call maydit/lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

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