# Lever Jobs Scraper & API (`brightgro/lever-jobs`) Actor

Get every open job from the public Lever job sites of the companies you list: title, team, locations, remote or hybrid, publish date, salary where published, links and the description as plain text. Filter by title, location, remote and posting date.

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

## Pricing

$2.00 / 1,000 jobs

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 & API

Give a list of companies that hire through Lever and get every open job on their public Lever job sites. The data comes from Lever's public postings API, one request per company, so a run does not depend on page layouts. Sites on Lever's EU instance are found automatically.

### Input

- Companies: Lever site names or job site URLs, up to 500. The site name is the name in the address: `jobs.lever.co/spotify` has the name `spotify`. `jobs.eu.lever.co/<name>` also works.
- Jobs per company: the most jobs to return for each company, newest first. The default is 1,000.
- Title keyword: only jobs whose title contains this text.
- Location: only jobs whose location or workplace type contains this text, for example `London` or `remote`.
- Fully remote only: only jobs whose workplace type is remote.
- Posted within days: only jobs created in the last N days. Use it to watch for new roles on a schedule.
- Include description: add the description, its lists and the closing section as plain text (on by default).

### Output

One row per job:

| Field | What it holds |
|---|---|
| status | `ok` for a job |
| company, region | The Lever site name and whether it is on the global or EU instance |
| job_id, title | Lever's posting id and the job title |
| team, department, commitment | As the company set them, for example Engineering and Full-time |
| location, all_locations, country | The main location, every listed location and the country code |
| workplace_type, remote | on-site, hybrid or remote, and whether it is remote |
| published_at | When the posting was created |
| salary_min, salary_max, salary_currency, salary_interval, salary_text | Pay, where the company publishes it in Lever's salary fields |
| url, apply_url | The job page and the application page |
| description | The description as plain text |

A company with no public Lever site, or with no job that matches the filters, gets one row with `status` set to `board_not_found` or `no_matching_jobs` and a message. Those rows are free.

### Price

One `job` event for each job returned, at the price shown on this page. Rows that say a site was not found or had no matching jobs cost nothing. When the run's spending limit is reached, the run stops and keeps the jobs it already has.

### Limits

- Only public Lever job sites. Jobs a company does not publish on its site are not included.
- Salary appears only where the company fills Lever's salary fields; many companies write pay in the description instead.
- Lever asks for one request a second, so the actor reads companies one after another: about 1 to 2 seconds a company.

# Actor input Schema

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

Lever site names (the name in jobs.lever.co/<name>) or job site URLs, up to 500. EU sites (jobs.eu.lever.co) work too.

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

The most jobs to return for each company, newest first.

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

Return only jobs whose title contains this text, for example engineer. Not case sensitive.

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

Return only jobs whose location or workplace type contains this text, for example London or remote.

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

Return only jobs whose workplace type is remote (not hybrid or on-site).

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

Return only jobs first published in this many days. Leave empty for every open job.

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

Add the full job description as plain text.

## Actor input object example

```json
{
  "companies": [
    "spotify"
  ],
  "maxJobsPerCompany": 10,
  "remoteOnly": false,
  "includeDescription": true
}
```

# Actor output Schema

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

Get every open job from the public Lever job sites of the companies you list: title, team, locations, remote or hybrid, publish date, salary where published, links and the description as plain text. Filter by title, location, remote and posting date.

# 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"
    ],
    "maxJobsPerCompany": 10
};

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

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

```

## MCP server setup

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