# Lever Jobs Scraper: Any Board, No API Key (`glitchbound/lever-jobs-scraper`) Actor

Every open role from any Lever job board, by company domain or board token. Titles, locations, teams, commitment type and full descriptions as clean JSON. No API key and no proxy: give it a domain and it finds the board itself.

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

## Pricing

from $1.50 / 1,000 job postings

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 Scraper: Any Board, No API Key

**Every open role from any Lever job board, by company domain or board token. Titles, locations, teams, commitment type and full descriptions as clean JSON. No API key and no proxy: give it a domain and it finds the board itself.**

### What people use this for

Hiring data is not really about jobs. It is the earliest public signal a
company gives that something changed, and it is why three different kinds of
buyer end up on the same dataset:

- **Sales and go-to-market.** A company that opens six engineering roles this
  month is a company with new budget. Job postings say which team is growing
  and in which city, weeks before anything shows up in a funding announcement.
- **Investors and market research.** Headcount by function, tracked over time,
  across a whole portfolio or a whole sector. Every row carries the company,
  the team and the date, so a weekly run is a time series.
- **Recruiting and talent.** Where a competitor is hiring, which roles they have been trying to fill for months, and how fast a team is growing. Lever does not publish pay, so no row here claims to know it.

Run it once for a snapshot. Run it on a schedule and the same rows become a
record of who started growing and when.

### You do not need the board token

```json
{ "companies": ["palantir.com"] }
```

Every other lever Actor asks you for a board token, and there is no directory
mapping a company to its token. This one derives candidates from the domain and
**verifies each against the live API**, which is sound because lever answers
`404` for a board that does not exist and `200` for one that exists with nothing
open. A `200` is proof, not a maybe.

Measured across 30 companies, deriving and verifying resolved 90% against
50% for reading the careers page for a link. Stripe's careers page is a
JavaScript app that names no board at all, and it still resolves.

### What makes lever different

- Measured: `palantir` 302 open roles, `spotify` 105, `walkme` 53.

- **Lever answers with a bare JSON array**, not an object with a `jobs` key like every other system here. A client written for Greenhouse reads that as zero results.

- Lever carries `commitment` (full time, intern, contract) and a plain-text description, so no HTML parsing is needed at all.

### Filters that cost you nothing

```json
{
  "boards": ["palantir"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true
}
```

Filtered rows are **not charged**. Keywords match as plain text, so `c++` and
`node.js` mean exactly that rather than being read as regular expressions.

### What you get

| Field | |
|---|---|
| `title` | the role as the company wrote it |
| `location` | as published, not normalised |
| `url` | the public posting, ready to open |
| `jobId` | the ATS's own id, stable across runs |
| `postedAt` | ISO 8601 UTC |
| `departments` | list |
| `offices` | list |
| `description` | opt in, off by default because it is expensive at the source |
| `employmentType` | full time, contract, intern, as the source says |
| `company` | what you asked for, echoed back |
| `atsPlatform` | which system it came from |
| `boardToken` | the board id used |
| `boardUrl` | the public board this came from |

### Looking for an Indeed or Glassdoor API? There isn't one, and this is why you don't need it

Indeed has no public jobs API. Neither does Glassdoor, ZipRecruiter or LinkedIn
Jobs, and all four block you at the edge. Measured from an ordinary residential
address on 2026-08-01, with normal browser headers:

```
indeed.com/jobs          403      0 bytes
glassdoor.com/Job/...    403      0 bytes
ziprecruiter.com         403      0 bytes
upwork.com/nx/search     403      0 bytes
```

Zero bytes. Cloudflare rejects the request before it reaches an application, so
there is nothing to parse and no proxy budget that fixes it.

**But none of those four originate job data.** They aggregate it from company
career pages, and those pages run on systems like lever that publish a free,
keyless, public API, because companies want their openings indexed. That API
answered with real jobs from the same connection, in the same minute.

Going to the source is also fresher. An aggregator shows you its last crawl.
This shows you the board.

### Notes

- The source is a public API that companies publish deliberately. Nothing here
  is behind a login, a paywall or a bot wall.
- An empty board is a real answer and is reported as one.
- Errors are per company. One bad token does not end the run, and error rows
  are not charged.

# Actor input Schema

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

Company domains or names, one per line, e.g. palantir.com. The Actor derives the likely lever board token and verifies it against the live API before reading it, so you do not need to know the token.

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

Board tokens to read, one per line, e.g. palantir. A platform:token form is also accepted and the platform is ignored.

## `titleKeywords` (type: `array`):

Keep only roles whose title contains any of these, one per line, e.g. security or staff engineer. Matched as plain text, case-insensitive, so c++ and node.js mean exactly that. Filtered rows are not charged.

## `locationKeywords` (type: `array`):

Keep only roles whose location contains any of these, one per line, e.g. London or Israel. Filtered rows are not charged.

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

Keep only roles flagged remote by the ATS, or whose title or location says remote or anywhere.

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

Fetch the description text as well. Off by default because it is expensive at the source rather than here: Greenhouse returns 111 KB for a board without it and 1.97 MB with, an 18x difference for the same jobs. Rippling's board API returns no description at any setting.

## `maxResultsPerCompany` (type: `integer`):

Ceiling on roles taken from any single board.

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

A hard ceiling on rows for the entire run, across every company. The per-company limit above caps each one separately, so fifty companies at a thousand each is still fifty thousand rows; this caps the total. The run stops cleanly when it is reached and nothing beyond that point is fetched or charged. Leave empty for no ceiling.

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

Proxy settings. Every source here is a public API a company publishes on purpose so its openings get indexed, and none of them block datacenter addresses, so the default is fine.

## Actor input object example

```json
{
  "companies": [
    "palantir.com"
  ],
  "remoteOnly": false,
  "includeDescription": false,
  "maxResultsPerCompany": 1000,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All rows this run produced, as JSON.

# 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": [
        "palantir.com"
    ],
    "maxResultsPerCompany": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("glitchbound/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": ["palantir.com"],
    "maxResultsPerCompany": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("glitchbound/lever-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": [
    "palantir.com"
  ],
  "maxResultsPerCompany": 1000
}' |
apify call glitchbound/lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=glitchbound/lever-jobs-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HPrF0lQhYHUtxkezE/builds/SSgZb6ogIw83AvtV1/openapi.json