# Lever Jobs API - Career Page Scraper, Every Row Dated (`starbright_overlap/lever-jobs-scraper`) Actor

Lever jobs API and career page scraper. Read live postings from any Lever job board or careers page, or search thousands of known Lever ATS boards in one run. Every row carries a real publish timestamp, so freshness filters mean what they say.

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

## Pricing

from $2.00 / 1,000 job 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/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 Jobs API — 1,917 Career Pages, Every Row Dated

Lever is an applicant tracking system used by technology and growth-stage employers, and its
postings API is open. Every posting carries a real publish timestamp, which is not true of most
platforms in this family.

Point it at a company, or leave the list empty and search a bundled registry of **1,917 live
Lever career pages** carrying **63,622 open postings**.

```json
{ "keywords": ["engineer"], "postedWithinDays": 7, "maxJobs": 200 }
```

```json
{ "companies": ["https://jobs.lever.co/netflix"] }
```

No login, no cookies, no proxies, no API key.

### Dates on every row

Measured across **every live board in this registry — 46,005 postings from 1,880 boards**:

| Field | Fill rate |
|---|---|
| `postedAt` | **100%** |
| `department` | **99.7%** |
| `descriptionText` | **94.7%** |
| `employmentType` | **92.9%** |
| `remote` | 4.8% |
| `salary` | **0%** — Lever does not expose pay on this endpoint |

`postedWithinDays` works properly here. A 7-day window returns what actually appeared in the last
seven days, rather than keeping undated rows the way it has to on Workday, Rippling, Pinpoint and
BambooHR.

### What you get

| Field | Description |
|---|---|
| `provider` | Always `lever` — the same schema the multi-ATS Actors below emit |
| `company` / `companySlug` | Employer board name |
| `jobId` | Lever posting id — stable, so it works as a dedupe key across runs |
| `title` | Job title |
| `location` | Location as the employer entered it |
| `department` | Lever's team field |
| `employmentType` | Lever's commitment field — full-time, contract, intern |
| `remote` | Inferred from the location string, because Lever has no remote field — see below |
| `postedAt` | Publish timestamp, on every row |
| `applyUrl` | Direct link to the posting |
| `descriptionText` | Full posting text as readable plain text, on 94.7% of rows |
| `salary` | Always `null` here. Lever does not publish pay on this endpoint |
| `scrapedAt` | When this row was read |

### Two honest limitations

**No pay data.** Lever's postings endpoint has no compensation field, so `salary` is `null` on
every row. That is the source, not the Actor. For pay, use **Recruitee** or **Pinpoint** (structured
numbers) or **Ashby** (a prose summary) — all linked below.

**`remote` is a guess.** Lever has no remote flag, so this Actor pattern-matches the location
string, and only **4.8%** of rows come back marked. A role described as "Anywhere" or one whose
remoteness is only stated in the body text will be missed. Where the employer's own checkbox
matters, **Ashby** marks 85.1% of its rows and **Recruitee** marks 100%.

### Input

| Option | What it does |
|---|---|
| `keywords` | Keep only titles containing one of these. Case-insensitive. |
| `excludeKeywords` | Drop titles containing any of these, e.g. `senior`, `intern`. |
| `locations` | Keep only locations containing one of these. |
| `remoteOnly` | Keep only postings whose location string says remote. See the caveat above. |
| `postedWithinDays` | Freshness filter. Every Lever row has a real date, so this works properly. |
| `companies` | Board names or board URLs. Leave empty to search all 1,917. |
| `maxBoards` | How many boards to scan, largest-first. |
| `maxJobs` | Hard cap on rows, so a run costs what you expect. |

### Finding a company slug

The board lives at `jobs.lever.co/<slug>`, so the slug is the last path segment. Paste the whole URL
and the Actor extracts it. Or run without `companies` and read the `companySlug` column.

### Recipes

**A genuinely fresh feed.** `postedWithinDays: 1` run daily gives you yesterday's openings and
nothing else — the date is real, so the filter is real.

**Watch a competitor's hiring.** One slug on a schedule, diff `jobId` between runs. `department`
is present on 99.7% of rows, so you can see *where* they are growing, not just how much.

**Full-text search.** Descriptions come back as plain text on 94.7% of rows.

### Pricing

Pay per result — you are charged per job row delivered. A board that fails or returns nothing costs
you nothing. Platform usage is included rather than billed on top.

### Beyond Lever

Companies move between applicant tracking systems, and most job-data projects need more than one:

- **[Career Site Job Feed](https://apify.com/starbright_overlap/ats-job-feed)** — the same engine
  across every platform in this family, in one run, with an identical output schema.
- **[New Job Alerts](https://apify.com/starbright_overlap/new-jobs-feed)** — the same coverage, but
  each run returns only what appeared since the previous run.
- **[Ashby Jobs API](https://apify.com/starbright_overlap/ashby-jobs-scraper)** — a real remote
  flag on 85.1% of rows, and more than half of postings marked remote.

### Notes

- **A dead slug never aborts the run.** Failures land in a `FAILED_BOARDS` record in the key-value
  store, with the reason for each.
- **`companySlug:jobId` is a stable key**, safe for detecting what opened and closed between runs.
- **No login, no proxies, no API key.** Lever publishes this endpoint openly.

# Actor input Schema

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

Keep only jobs whose title contains at least one of these. Case-insensitive. Leave empty for every job.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these, e.g. `senior`, `intern`.

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

Keep only jobs whose location contains one of these, e.g. `london`, `new york`, `germany`.

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

Keep only postings flagged remote by the ATS or with a remote-looking location.

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

Freshness filter. Defaults to 90 days because some employers leave postings open for years — measured across the registry, 15% of Greenhouse and about half of the largest SmartRecruiters boards are over a year old. Set a large number such as 3650 to include everything. Postings with no publication date (most Workday rows) are always kept.

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

Board slugs, e.g. `tsmg`. Leave empty to search all 1,917 known lever employers.

## `maxBoards` (type: `integer`):

Boards are scanned largest-first, so a capped run still returns the most jobs. Raise it to sweep all 1,917 boards.

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

Hard cap on results, so a run costs what you expect. Defaults to 500 — enough to evaluate the feed on free-tier credits. Clearing the box falls back to that, so type a large number such as 500000 to sweep everything.

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

Fetch the full description text. Available on Greenhouse, Workable, Ashby and Breezy. SmartRecruiters and Workday do not expose descriptions on their listing endpoints, so those rows return null however this is set. Turning it off makes runs several times faster.

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

Higher is faster but more likely to hit ATS rate limits.

## `maxJobsPerCompany` (type: `integer`):

Keeps one huge employer from filling the whole run. Boards are scanned largest-first, so without this the first few boards use up the entire result budget. Raise it when you want depth on a few employers rather than breadth across many.

## Actor input object example

```json
{
  "keywords": [
    "engineer"
  ],
  "remoteOnly": false,
  "postedWithinDays": 90,
  "maxBoards": 300,
  "maxJobs": 500,
  "includeDescription": true,
  "concurrency": 8,
  "maxJobsPerCompany": 25
}
```

# Actor output Schema

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

Every posting matching your filters, normalized across all six ATS platforms.

## `failedBoards` (type: `string`):

Written only when a board was unreachable or rate-limited. The run itself is unaffected.

# 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 = {
    "keywords": [
        "engineer"
    ],
    "postedWithinDays": 90,
    "maxJobs": 500,
    "maxJobsPerCompany": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("starbright_overlap/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 = {
    "keywords": ["engineer"],
    "postedWithinDays": 90,
    "maxJobs": 500,
    "maxJobsPerCompany": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("starbright_overlap/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 '{
  "keywords": [
    "engineer"
  ],
  "postedWithinDays": 90,
  "maxJobs": 500,
  "maxJobsPerCompany": 25
}' |
apify call starbright_overlap/lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

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