# Lever Jobs Scraper: Live Board Data (`b2b_leads/lever-boards-real-time-data-scraper`) Actor

Live job openings from any Lever-powered career board (jobs.lever.co): keyword search across companies, location, department and remote filters, full descriptions, and direct job links. Streams structured rows to your dataset in real time.

- **URL**: https://apify.com/b2b_leads/lever-boards-real-time-data-scraper.md
- **Developed by:** [Emmanuel](https://apify.com/b2b_leads) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

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 Boards Real-Time Data

> **Free trial:** runs on the Apify free plan return a 2-result sample per run. Upgrade to a paid Apify plan for full, unlimited exports.

Live job openings from any company career board hosted on Lever (`jobs.lever.co`) — board listings, keyword search, location and department filters, remote-only mode, full descriptions, and direct job links. Every row streams to your dataset the moment it is collected, and can also be pushed to a webhook in real time.

### Who this is for

- **Recruiters & sourcers** building talent pipelines from live openings at target companies
- **Staffing agencies** monitoring hiring activity across dozens of Lever-powered employers
- **Job-board & career-site operators** keeping listings fresh without manual research
- **Market researchers** tracking hiring trends by company, department, location, and workplace type
- **Founders & HR teams** benchmarking competitor hiring and role definitions
- **AI agents & automation builders** feeding structured, up-to-date postings into CRMs, alerts, and workflows

### Features

| Mode | What you get |
|---|---|
| 💼 Board jobs (default on) | Keyword search across one or more company boards: title, company, location, all locations, department, team, commitment, workplace type, country, posting date, descriptions, job + apply links |
| 🎯 Enrich with full details (toggle) | Refreshes each row with the latest full description and posting metadata. Adds a little extra time per record; off = fast board cards |
| 🔗 Job links | Paste individual Lever job URLs to collect the same structured row per link |
| ⚙️ Output & delivery | Streaming dataset writes, JSON or Slack webhooks, global max-items cap |
| 🌐 Connection | Apify residential US proxy on by default for reliable high-volume runs |

### Input reference

**Board jobs**

| Field | Type | Default | Notes |
|---|---|---|---|
| `enableBoardJobs` | checkbox | `true` | Master switch for board collection |
| `companySlugs` | string list | `["spotify"]` | Board names from `jobs.lever.co` URLs (e.g. `spotify` for `jobs.lever.co/spotify`). Accepts full board URLs too |
| `jobKeywords` | string list | `["engineer"]` | Matched against title, department, team, location, and description. Empty = all openings |
| `jobLocation` | text | `""` | Partial match on location (e.g. `New York`, `Remote`, `London`) |
| `jobDepartment` | text | `""` | Partial match on department or team (e.g. `Engineering`, `Design`) |
| `remoteOnly` | checkbox | `false` | Keep only jobs marked remote |
| `jobDatePosted` | select | `any` | `any` / `month` / `week` / `day` |
| `jobsPerCompany` | number | `10` | Cap per company/keyword combination (1–200) |
| `searchFetchFullDetails` | checkbox | `false` | Enrich every row in place (`detailsFetched: true`). Same row — never duplicated or dropped |

**Job links**

| Field | Type | Default | Notes |
|---|---|---|---|
| `enableScrapeByUrl` | checkbox | `false` | Master switch for URL mode |
| `jobUrls` | string list | `[]` | `jobs.lever.co/COMPANY/ID` links (US and EU boards supported) |

**Output & delivery**

| Field | Type | Default | Notes |
|---|---|---|---|
| `webhookUrl` | text | `""` | Optional HTTPS URL; each record is always saved to the dataset first |
| `webhookFormat` | select | `json` | `json` = full record, `slack` = compact message |

**Connection**: standard Apify proxy object (Residential US by default).

Example — backend engineers in New York at two companies:

```json
{
  "enableBoardJobs": true,
  "companySlugs": ["spotify", "ro"],
  "jobKeywords": ["backend engineer"],
  "jobLocation": "New York",
  "remoteOnly": false,
  "jobsPerCompany": 20,
  "searchFetchFullDetails": true
}
```

### Output fields

One row per posting: `featureType`, `jobId`, `companySlug`, `title`, `company`, `companyUrl`, `location`, `allLocations`, `department`, `team`, `commitment`, `workplaceType` (onsite / remote / hybrid / flexible), `country`, `jobUrl`, `applyUrl`, `descriptionText`, `descriptionHtml`, `postedAt`, `detailsFetched`, `searchQuery`, `searchCompany`, `sourceUrl`, `position`, `scrapedAt`.

The run summary (counts, paywall status, spending-limit state) is stored in the key-value store under `OUTPUT`.

### Webhooks

Set `webhookUrl` to receive one POST per record **in addition** to the dataset write. Use `json` for pipelines (CRM, Zapier, Make, Sheets) or `slack` for an incoming Slack webhook. Delivery is fire-and-forget — a failed webhook never stops the run.

### MCP / AI-agent usage

Pair this Actor with the Apify MCP server to query live postings conversationally. Example prompt for your agent:

> "Using the Lever Boards actor, find remote designer openings at Spotify and summarize the teams hiring."

### FAQ

- **Which companies are supported?** Any employer whose careers page lives on `jobs.lever.co` (US and EU boards). Paste the board name from the URL.
- **How fresh is the data?** Every run reads the live boards, so rows reflect currently published openings.
- **Do I need a proxy?** Apify residential proxy is on by default and recommended for large runs. Small runs work without one.
- **What does the free trial include?** 2 results per run on the Apify free plan — enough to verify shape and fit. Paid plans are uncapped.
- **How am I charged?** Pay-per-event on the `result` event (one per exported row), subject to your run's max-spend limit. When the limit is hit the run stops gracefully and keeps everything collected so far.

# Actor input Schema

## `enableBoardJobs` (type: `boolean`):

Collect live job openings from Lever company boards. Enabled by default.

## `companySlugs` (type: `array`):

Company board names as they appear in jobs.lever.co URLs (e.g. spotify for jobs.lever.co/spotify). One search runs per company.

## `jobKeywords` (type: `array`):

Search terms matched against job title, department, team, location, and description (e.g. engineer, designer, marketing). Empty = all openings on the selected boards.

## `jobLocation` (type: `string`):

Optional filter on the job location (e.g. New York, Remote, London). Partial match.

## `jobDepartment` (type: `string`):

Optional filter on the department or team (e.g. Engineering, Design, Marketing). Partial match.

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

Keep only jobs marked as remote.

## `jobDatePosted` (type: `string`):

Only return jobs posted within this window.

## `jobsPerCompany` (type: `integer`):

Maximum jobs to return per company/keyword combination (1-200). Default 10 for fast demo runs.

## `searchFetchFullDetails` (type: `boolean`):

Refreshes each row with the latest full job description, sections, and posting dates. Adds a little extra time per record. Off = fast cards from the board listing.

## `enableScrapeByUrl` (type: `boolean`):

Collect structured data from individual Lever job page URLs.

## `jobUrls` (type: `array`):

Lever job page URLs (https://jobs.lever.co/spotify/223f9722-3579-4ff2-b123-e4cc7b0c1a64) to collect.

## `webhookUrl` (type: `string`):

Optional HTTPS URL. Each record is always saved to the dataset — the webhook sends an additional real-time POST per job (CRM, Slack, Zapier, Make, custom pipelines).

## `webhookFormat` (type: `string`):

json = full job record. slack = compact Slack incoming-webhook message.

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

Apify proxy configuration. Residential US proxy is recommended for consistent results on large runs.

## Actor input object example

```json
{
  "enableBoardJobs": true,
  "companySlugs": [
    "spotify"
  ],
  "jobKeywords": [
    "engineer"
  ],
  "jobLocation": "",
  "jobDepartment": "",
  "remoteOnly": false,
  "jobDatePosted": "any",
  "jobsPerCompany": 10,
  "searchFetchFullDetails": false,
  "enableScrapeByUrl": false,
  "jobUrls": [],
  "webhookUrl": "",
  "webhookFormat": "json",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

## `allResults` (type: `string`):

Complete dataset with every job field from this run.

## `overview` (type: `string`):

Core job fields table view.

## `full` (type: `string`):

All job fields including descriptions.

# 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 = {
    "enableBoardJobs": true,
    "companySlugs": [
        "spotify"
    ],
    "jobKeywords": [
        "engineer"
    ],
    "jobLocation": "",
    "jobDepartment": "",
    "remoteOnly": false,
    "jobDatePosted": "any",
    "jobsPerCompany": 10,
    "searchFetchFullDetails": false,
    "enableScrapeByUrl": false,
    "jobUrls": [],
    "webhookUrl": "",
    "webhookFormat": "json",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "US"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("b2b_leads/lever-boards-real-time-data-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 = {
    "enableBoardJobs": True,
    "companySlugs": ["spotify"],
    "jobKeywords": ["engineer"],
    "jobLocation": "",
    "jobDepartment": "",
    "remoteOnly": False,
    "jobDatePosted": "any",
    "jobsPerCompany": 10,
    "searchFetchFullDetails": False,
    "enableScrapeByUrl": False,
    "jobUrls": [],
    "webhookUrl": "",
    "webhookFormat": "json",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "US",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("b2b_leads/lever-boards-real-time-data-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 '{
  "enableBoardJobs": true,
  "companySlugs": [
    "spotify"
  ],
  "jobKeywords": [
    "engineer"
  ],
  "jobLocation": "",
  "jobDepartment": "",
  "remoteOnly": false,
  "jobDatePosted": "any",
  "jobsPerCompany": 10,
  "searchFetchFullDetails": false,
  "enableScrapeByUrl": false,
  "jobUrls": [],
  "webhookUrl": "",
  "webhookFormat": "json",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}' |
apify call b2b_leads/lever-boards-real-time-data-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,b2b_leads/lever-boards-real-time-data-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/UPBXKzj7J4QCVwuYg/builds/bl9g9b9hy7pG1yXNH/openapi.json