# Jobs API for Lever: Job Board Scraper & New Job Alerts (`lepidata/lever-jobs`) Actor

Every open job from any company's public Lever job board (US-hosted boards), as clean JSON. No API key. Run on a schedule to get only jobs that are new, changed or closed since your last run. Title, team, location, dates and full description.

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

## Pricing

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

## Jobs API for Lever: Job Board Scraper & New Job Alerts

### What it does

Give it one or more Lever board names (the part after jobs.lever.co/), and it returns each open job with title, department, location, posting URL, publish date, and the full description.

### Two modes

- **Full pull (default):** every open job on each board.
- **New since last run** (`onlyNewSinceLastRun`): only jobs that were added, removed, or updated since your previous run. A job counts as changed when its title, location or description text changes. A new date on the posting alone doesn't count. Built for hiring-signal monitoring, so you aren't paying to re-download the same jobs every day.

### Who uses it

- Sales and recruiting teams watching which companies are hiring for which roles
- Job boards and newsletters that aggregate postings
- Researchers tracking hiring trends at specific companies

### Input

- `boards`: list of Lever board names, e.g. `spotify`, `palantir` (US-hosted boards only)
- `onlyNewSinceLastRun`: return only jobs that are new or updated since your previous run (default off)
- `includeRemoved`: also return free rows for jobs removed since your previous run (default off)
- `startFromNow`: the first run records the jobs open now without returning or charging for them (one free `baseline-saved` row per company); later runs return only new or changed jobs. Ignored for companies already tracked under the same `stateKey` (default off)
- `stateKey`: name for the saved state, so separate monitors don't overwrite each other (default `default`)
- `titleKeyword` / `locationKeyword`: optional filters on title and location
- `includeDescriptions`: include full job descriptions (default on)
- `maxJobsPerBoard`: cap per board (default 5,000)
- `emailPolicy`: `keep-role` (default) keeps company role addresses like accommodations inboxes; `strip-all` removes every email

### Output (one item per job)

source, board, jobId, title, department, location, url, updatedAt (the publish time; Lever does not expose edit times), firstPublished, description, changeType (`new` / `updated` / `unchanged` / `removed`; `updated` means a title, location or description text change; a new date alone doesn't count). Removed rows carry only the ID and change type.

### Example

Input:

```json
{
  "boards": [
    "tala",
    "greenlight",
    "zeta"
  ],
  "onlyNewSinceLastRun": false,
  "includeDescriptions": true
}
```

Output (five real rows from our test run on Apify, Oct 11 2026; descriptions shortened here, full text in the actual output):

```json
[
  {
    "source": "lever",
    "board": "tala",
    "jobId": "848e6f75-9b40-45d2-b5b8-82de6670b0ed",
    "title": "Analytics Platforms Architect",
    "department": "Technology, Data & Platform",
    "office": null,
    "location": "US",
    "url": "https://jobs.lever.co/tala/848e6f75-9b40-45d2-b5b8-82de6670b0ed",
    "updatedAt": "2026-09-09T20:51:55.558Z",
    "firstPublished": "2026-09-09T20:51:55.558Z",
    "description": "About Tala Tala is the AI-native credit infrastructure that connects global capital to the global majority. We combine proprietary risk intelligence with an…",
    "changeType": "new"
  },
  {
    "source": "lever",
    "board": "tala",
    "jobId": "414d3726-20bc-4a89-9f82-66620943febb",
    "title": "Manager, Machine Learning Engineering",
    "department": "Technology, Data & Platform",
    "office": null,
    "location": "US",
    "url": "https://jobs.lever.co/tala/414d3726-20bc-4a89-9f82-66620943febb",
    "updatedAt": "2026-09-17T14:46:03.922Z",
    "firstPublished": "2026-09-17T14:46:03.922Z",
    "description": "About Tala Tala is the AI-native credit infrastructure that connects global capital to the global majority. We combine proprietary risk intelligence with an…",
    "changeType": "new"
  },
  {
    "source": "lever",
    "board": "tala",
    "jobId": "e7b55498-33ed-48fa-ae8c-261082f66906",
    "title": "Senior Backend Engineer",
    "department": "Technology, Product Engineering",
    "office": null,
    "location": "IN",
    "url": "https://jobs.lever.co/tala/e7b55498-33ed-48fa-ae8c-261082f66906",
    "updatedAt": "2026-10-07T02:10:38.185Z",
    "firstPublished": "2026-10-07T02:10:38.185Z",
    "description": "Tala is the AI-native credit infrastructure that connects global capital to the global majority. We combine proprietary risk intelligence with an expanding…",
    "changeType": "new"
  },
  {
    "source": "lever",
    "board": "tala",
    "jobId": "83a306f8-674f-4818-b181-2b880d07f23b",
    "title": "Senior Credit Risk Manager",
    "department": "Risk Management, Risk Management",
    "office": null,
    "location": "PH",
    "url": "https://jobs.lever.co/tala/83a306f8-674f-4818-b181-2b880d07f23b",
    "updatedAt": "2026-10-09T03:30:32.039Z",
    "firstPublished": "2026-10-09T03:30:32.039Z",
    "description": "About Tala Tala is the AI-native credit infrastructure that connects global capital to the global majority. We combine proprietary risk intelligence with an…",
    "changeType": "new"
  },
  {
    "source": "lever",
    "board": "tala",
    "jobId": "a391ff08-acf0-456b-84a1-46f3dd98afdb",
    "title": "Senior Manager Expansion Risk",
    "department": "Risk Management, Risk Management",
    "office": null,
    "location": "IN",
    "url": "https://jobs.lever.co/tala/a391ff08-acf0-456b-84a1-46f3dd98afdb",
    "updatedAt": "2026-06-23T12:43:15.661Z",
    "firstPublished": "2026-06-23T12:43:15.661Z",
    "description": "About Tala Tala is the AI-native credit infrastructure that connects global capital to the global majority. We combine proprietary risk intelligence with an…",
    "changeType": "new"
  }
]
```

### Why use this one

- **Health-checked daily** against real company boards. If something breaks, the listing is flagged within a day.
- **Failures are free and visible.** Anything we can't fetch comes back as a free `board-error` row with the reason, never a silent gap.
- **Exact price, no surprises.** You pay only for the jobs delivered, at the price shown below.

### Pricing

$1.20 per 1,000 jobs, the same on every Apify plan, with no start fee. Removed-job alerts are free.

Free-plan accounts get up to 100 results per run to try it out; the run ends with one free row explaining the limit. Paid Apify plans get full results.

If you set a maximum charge per run, the run stops cleanly when it's reached and you're never billed past it. The last row is a free `charge-limit-reached` row showing how many jobs were delivered, and jobs you didn't receive are still marked new on your next run.

### Data source and limits

Uses Lever's documented public Postings API. It only sees boards a company has made public, and covers US-hosted Lever boards only (boards on Lever's EU servers return not found). An unknown board name comes back as a free `board-error` row with the reason in the `error` field, not a crash. Lever asks crawlers to wait 1 second between requests, so we fetch Lever boards one at a time, 1 second apart. A run over many Lever boards takes about a second per board longer; it doesn't change the price.

### Not affiliated

This Actor is an independent, unofficial tool. It is not made, endorsed, or supported by Lever or its parent company. "Lever" is used only to describe the public job boards this tool reads. Phone numbers and personal email addresses are removed. Company role addresses, like accommodations or recruiting inboxes, are kept so applicants can reach them.

# Actor input Schema

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

Board names from jobs.lever.co/<name> (or paste the board URL). Up to 200 per run.

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

Returns only jobs added or changed since your previous run with the same state key. A job counts as changed when its title, location or description text changes. A new date on the posting alone doesn't count. The first run returns everything.

## `startFromNow` (type: `boolean`):

First run records currently open jobs without charging for them; later runs return only new/changed jobs. Ignored for companies already tracked under this stateKey.

## `includeRemoved` (type: `boolean`):

Adds one item per job that disappeared since the last run (changeType = removed).

## `stateKey` (type: `string`):

Name for this monitor. Use different keys to track different board lists separately.

## `titleKeyword` (type: `string`):

Only return jobs whose title contains this text (case-insensitive).

## `locationKeyword` (type: `string`):

Only return jobs whose location contains this text (case-insensitive).

## `includeDescriptions` (type: `boolean`):

Include the plain-text job description. Turn off for smaller output. The description is still read to detect changes, just not returned.

## `maxJobsPerBoard` (type: `integer`):

Upper limit on jobs returned per board.

## `emailPolicy` (type: `string`):

Phone numbers and personal-looking emails are always removed. Choose whether company role addresses such as accommodations@ stay in.

## Actor input object example

```json
{
  "boards": [
    "spotify",
    "palantir"
  ],
  "onlyNewSinceLastRun": false,
  "startFromNow": false,
  "includeRemoved": false,
  "stateKey": "default",
  "includeDescriptions": true,
  "maxJobsPerBoard": 5000,
  "emailPolicy": "keep-role"
}
```

# Actor output Schema

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

All job and status rows from this run.

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

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

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

```

## MCP server setup

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

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/vd98t9sHWHD1F2Yu4/builds/rkdnifdpQv9JRI0nr/openapi.json