# Lever Jobs Scraper - Postings, Salary & Apply Links (`haketa/lever-jobs-scraper`) Actor

Scrape every open role from any company's Lever (jobs.lever.co) board: title, team, department, location, remote/hybrid/onsite, salary, full description & direct apply URL. No API key, no login. Filter by keyword, location, team, workplace type & country.

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

## Pricing

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

Scrape **every open job** from any company that hosts its careers page on **Lever** (`jobs.lever.co/{company}`). Lever publishes each board as a public JSON feed, so this actor needs **no API key, no login and no browser** — just give it the companies you care about and get a clean, flat, analysis-ready row per role.

Perfect for **job boards and aggregators**, **recruiters and sourcers** building talent pipelines, **market / competitive intelligence** (who's hiring, for what, where), and **hiring analytics**.

### What you get per job

| Field | Description |
|---|---|
| `title` | Role title |
| `company` | Lever company slug |
| `department`, `team` | Org placement |
| `commitment` | Full-time / Contract / Intern / Permanent … |
| `location`, `allLocations`, `country` | Where the role is based |
| `workplaceType`, `isRemote` | `remote` / `hybrid` / `onsite` + boolean flag |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval` | Pay range **when the board publishes it** (common on US pay-transparency roles) |
| `postedAt`, `postedTimestamp` | When the role was posted |
| `descriptionText`, `sections` | Full description + responsibility / requirement sections as clean text |
| `url`, `applyUrl` | Public posting URL and the direct apply link |

### Input

```json
{
  "companies": ["spotify", "https://jobs.lever.co/ro", "gopuff"],
  "searchTerm": "engineer",
  "workplaceType": "remote",
  "location": "London",
  "country": "GB",
  "maxItems": 200
}
```

- **companies** — slugs or any `jobs.lever.co` URL, one per line. You can paste a full board URL and the slug is parsed out automatically.
- **searchTerm / location / team / department / commitment / workplaceType / country** — optional filters, all applied client-side (substring, case-insensitive; `workplaceType` and `country` are exact).
- **includeDescription** — set `false` for a lean dataset (title, location, salary & links only).
- **maxItems** — total cap across all boards (`0` = no limit).

### How to find the companies

Lever does **not** offer a global search across companies — each board lives at its own slug. Bring your own list: a target-account or competitor list, a VC/accelerator portfolio page, a "we're hiring" tweet, or a Google Sheet. If a company's careers page redirects to `jobs.lever.co/<something>`, that `<something>` is the slug.

### Notes

- No key and no anti-bot, but running through **Apify Proxy** (default) spreads requests across IPs and avoids Lever's occasional rate-limiting on large boards.
- Boards that don't exist (the company isn't on Lever, or the slug is wrong) are skipped with a warning — they don't fail the run.
- Each posting already carries its full description in the board feed, so there are **no extra per-job requests** — big boards are fetched in just a few paginated calls.

# Actor input Schema

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

Companies whose Lever board you want to scrape. Paste the slug (e.g. `spotify`) or any jobs.lever.co URL (e.g. `https://jobs.lever.co/spotify`) — one per line. Lever has no cross-company search, so bring your own list (a target/competitor list, a VC portfolio page, a Google Sheet …). Find slugs at jobs.lever.co/{company}.

## `searchTerm` (type: `string`):

Keep only roles whose title, team, department or description contains this text (case-insensitive). Leave empty for all roles.

## `location` (type: `string`):

Keep only roles whose location (or any of its listed locations) contains this text, e.g. `London`, `New York`, `Remote`. Case-insensitive substring match.

## `team` (type: `string`):

Keep only roles whose team contains this text, e.g. `Engineering`, `Marketing`. Case-insensitive.

## `department` (type: `string`):

Keep only roles whose department contains this text. Case-insensitive.

## `commitment` (type: `string`):

Keep only roles whose commitment contains this text, e.g. `Full`, `Contract`, `Intern`, `Permanent`. Case-insensitive.

## `workplaceType` (type: `string`):

Keep only roles with this workplace type.

## `country` (type: `string`):

Keep only roles in this country, given as a 2-letter ISO code, e.g. `US`, `GB`, `DE`. Case-insensitive.

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

Include the full job description text and the responsibility/requirement sections in each row. Turn off for a lean dataset (title, location, salary & links only).

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

Maximum number of jobs to save across all boards. 0 = no limit (scrape everything that matches).

## `maxConcurrency` (type: `integer`):

How many company boards to fetch in parallel.

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

Proxy settings. Apify Proxy (default) spreads requests across IPs and keeps Lever's occasional rate-limiting at bay.

## Actor input object example

```json
{
  "companies": [
    "spotify",
    "https://jobs.lever.co/ro",
    "gopuff"
  ],
  "searchTerm": "engineer",
  "location": "London",
  "workplaceType": "any",
  "country": "US",
  "includeDescription": true,
  "maxItems": 200,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

Job postings scraped from the Lever boards — role, team, location, workplace type, salary, description and apply links.

# 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",
        "ro"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("haketa/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",
        "ro",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("haketa/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",
    "ro"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call haketa/lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

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