# Lever Jobs Scraper & New Job Monitor (`nswk_api/lever-jobs-monitor`) Actor

Scrape every open job from any company's Lever job site and monitor new, updated and closed jobs. Salaries included, filters, clean JSON. No login.

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

## Pricing

Pay per event

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 & New Job Monitor

Get every open job from any company that hires with Lever, as clean JSON, with the pay
ranges the company publishes. Run it once for a full snapshot, or schedule it daily in
**changes** mode to get only the jobs that were **added, updated or closed** since the last run.

No login, no cookies, no proxies. It reads Lever's public Postings API, one request per company,
and finds sites hosted in Lever's EU region by itself.

### What you can do with it

- **Job boards and aggregators:** keep a fresh feed of jobs from hundreds of companies.
- **Sales teams:** spot hiring signals ("Acme opened 5 data engineering roles this week").
- **Recruiters and analysts:** track hiring and pay ranges by company, team and location.
- **AI agents:** one-line input, flat output, and you pay only for the jobs you get.

### Quick start

```json
{ "companies": ["spotify", "palantir", "zoox"] }
```

Each entry can be a site name (`spotify`), a site URL (`https://jobs.lever.co/spotify`),
a job URL from that site, an EU site URL (`https://jobs.eu.lever.co/<name>`) or a company name.

### Monitor new jobs

```json
{ "companies": ["spotify", "zoox"], "mode": "changes", "keywords": ["engineer"] }
```

Schedule it daily. Each job comes with `changeType`: `new`, `updated` or `closed`.
If a company fails to load, its jobs are never reported as closed. If you hit your
spending limit, the jobs you did not receive are reported again on the next run.

Use a different `monitorId` for each watch list or set of filters.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `companies` | string\[] | required | Site names, site URLs or company names |
| `mode` | `all` / `changes` | `all` | Full snapshot, or only changes since the last run |
| `keywords` / `excludeKeywords` | string\[] | `[]` | Match on title, department and team, case- and accent-insensitive |
| `locations` | string\[] | `[]` | Match on any of the job's locations, e.g. `remote`, `Germany`, `London` |
| `departments` | string\[] | `[]` | Match on department or team names |
| `remoteOnly` | boolean | `false` | Only jobs marked as remote |
| `postedWithinDays` | number | none | Only jobs created in the last N days |
| `includeDescription` | `text` / `html` / `none` | `text` | Description format. `none` gives the smallest output |
| `maxJobsPerCompany` | number | `1000` | Safety cap per company |
| `monitorId` | string | `default` | Name of the saved state for `changes` mode |
| `emitOnFirstRun` | boolean | `true` | If off, the first `changes` run only saves a baseline |

### Output

One item per job, in the same format as our Greenhouse, Ashby and Workday Actors. Every
field is always present (`null` when unknown), and dates are UTC ISO 8601.

```json
{
  "jobId": "lever:zoox:e8a190f0-7a89-4c11-a6a0-452ff6234749",
  "source": "lever",
  "companyToken": "zoox",
  "companyName": null,
  "title": "Administrative Business Partner, Floater",
  "departments": ["Executive Office"],
  "offices": ["Foster City, CA"],
  "location": "Foster City, CA",
  "countryCode": "US",
  "workplaceType": "hybrid",
  "isRemote": false,
  "employmentType": "full-time",
  "url": "https://jobs.lever.co/zoox/e8a190f0-7a89-4c11-a6a0-452ff6234749",
  "firstPublishedAt": "2026-10-06T17:27:44.932Z",
  "updatedAt": null,
  "requisitionId": null,
  "language": null,
  "salary": { "min": 123000, "max": 168000, "currency": "USD", "period": "year" },
  "descriptionText": "...",
  "descriptionHtml": null,
  "changeType": "new",
  "scrapedAt": "2026-10-25T12:00:00.000Z"
}
```

`departments` holds the department and the team. `salary` is the structured pay range the
company publishes, and `null` when it does not publish one. The description joins the
posting's text, its list sections (for example "Requirements") and its closing text.
Lever's API does not return the company's display name, so `companyName` is `null`; use
`companyToken`. A run summary (companies checked, failed companies with the reason, counts
per change type) is saved in the `OUTPUT` record of the run's key-value store.

### Pricing

Pay per event, no subscription:

- $0.0015 per job returned ($1.50 per 1,000 jobs)
- $0.0005 per company checked

Salaries are included at no extra cost. Filters run **before** you are charged, so you
only pay for jobs that match.

### Is it legal?

This Actor reads Lever's public Postings API, which Lever documents for building job sites.
Reading published postings needs no authentication. It follows the crawl delay in Lever's
robots.txt (one request per second). It returns job postings that employers published.
It does not collect data about individuals: emails and phone numbers inside job descriptions
are masked. You are responsible for how you use the data.

### FAQ

**Why is a company missing?**
It may not use Lever, or its site name differs from its name. Open one of its job postings
and copy the name from the `jobs.lever.co/<name>` link. Custom career domains cannot be
resolved to a site name.

**I changed my filters and got many closed or new jobs.**
The monitor compares against the saved state of that `monitorId`. Use a new `monitorId`
when you change filters.

**Greenhouse, Ashby or Workday?**
See our Greenhouse, Ashby and Workday Actors: same input, same output.

### Use it from an AI agent

Want Claude, Cursor or your own agent to search these jobs directly? The
[Career Site Jobs MCP Server](https://apify.com/nswk_api/career-site-jobs-mcp) exposes Greenhouse,
Ashby, Lever and Workday as MCP tools (`search_jobs`, `get_job_changes`, `get_salary_stats`),
with company names resolved automatically.

# Actor input Schema

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

Lever job site names (e.g. spotify), site URLs (https://jobs.lever.co/spotify) or company names. EU sites (jobs.eu.lever.co) are found automatically.

## `mode` (type: `string`):

"all" returns every matching job. "changes" returns only jobs that are new, updated or closed since the last run with the same monitor ID. Schedule it daily.

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

Keep jobs whose title, department or team contains any of these words. Case- and accent-insensitive.

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

Drop jobs whose title or department contains any of these words.

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

Keep jobs whose location or office contains any of these, e.g. "remote", "United States", "London".

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

Keep jobs in departments whose name contains any of these, e.g. "Engineering".

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

Keep only jobs marked as remote.

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

Keep only jobs first published in the last N days. Leave empty for no limit.

## `includeDescription` (type: `string`):

"none" gives the smallest output, ideal for AI agents.

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

Safety cap on returned jobs per company.

## `monitorId` (type: `string`):

Name of the saved state used by "changes" mode. Use a different ID for each watch list or filter set.

## `emitOnFirstRun` (type: `boolean`):

If off, the first "changes" run only saves a baseline and returns nothing.

## Actor input object example

```json
{
  "companies": [
    "spotify",
    "palantir",
    "zoox"
  ],
  "mode": "all",
  "remoteOnly": false,
  "includeDescription": "text",
  "maxJobsPerCompany": 1000,
  "monitorId": "default",
  "emitOnFirstRun": true
}
```

# Actor output Schema

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

One item per job, in the dataset view.

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

Companies checked, failed companies with the reason, and counts per change type.

# 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",
        "palantir",
        "zoox"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nswk_api/lever-jobs-monitor").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",
        "palantir",
        "zoox",
    ] }

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

```

## MCP server setup

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

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/otONYcnJtz9RvNi5j/builds/CpndI3IEfEL2EZuLg/openapi.json