# Lever Jobs Scraper — Company Job Boards (`adderleydata/lever-jobs-scraper`) Actor

Every open role on any company's Lever job board as structured data: title, department and team, location with country, work type, pay range where stated, created date, full text on request. One request per board, one stable schema. Incremental mode charges only for what changed. No personal data.

- **URL**: https://apify.com/adderleydata/lever-jobs-scraper.md
- **Developed by:** [Adderley Data](https://apify.com/adderleydata) (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.45 / 1,000 posting saveds

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

### What does Lever Jobs Scraper do?

Lever Jobs Scraper reads every open role on any company's public Lever job board and returns it as structured data you can load straight into a spreadsheet, a database or a model. Thousands of companies run their careers page on Lever; if the "Apply" button leads to jobs.lever.co or jobs.eu.lever.co, this Actor reads it.

Give it a site name (`acme`) or any Lever link for the company, and for each posting you get the title, the department and team, every location it lists with the country Lever records for it, the employment type and workplace type in the company's own terms, the pay range where the company states one, the date the posting was created, and a link to the posting — and, if you ask for it, the full text of the posting.

What makes it different:

- **One request per board.** The whole board, and every posting's full text with it, comes back in a single call to Lever's public Postings API. No HTML parsing, no page-by-page crawling, nothing to break when a careers page is redesigned. A thousand postings across fifty companies is fifty requests.
- **Pay ranges as numbers.** Where a company fills in Lever's salary range, it comes back as `min`, `max`, `currency` and `period`, with the posting's own wording kept beside them. Where it does not, but the posting's text states a range, that range is read and its sentence kept in `salary.raw`. Where no range is stated anywhere, the fields are `null`; nothing is estimated.
- **Incremental mode.** Put the Actor on a schedule and each run returns only postings that are new, changed, back again or gone. Lever publishes no last-modified time, so the Actor compares each posting with the last run — title, locations, team, employment type, workplace type, pay and every word of the text. Unchanged postings are skipped and **not charged**.
- **One stable schema.** Every row has every field, every time. Unknown is `null`, never a missing key, so nothing downstream breaks on a sparse posting. The schema is versioned (`job.v1`) and every Adderley Data jobs Actor uses it, so a Lever board, a Greenhouse board and a job board sit in the same table.
- **No personal data.** Lever's public feed has no recruiter fields and this Actor has nowhere to put one. Contact details inside posting text are redacted by default.
- **Bounded cost.** You set a maximum number of results; the run stops there. It also stops at the spending limit you set on the run in Apify.

### What Lever data can you extract?

| Field | What it holds |
| --- | --- |
| `id` | Stable across runs: `source:market:sourceJobId`. Use it as your primary key. |
| `title` | Job title as listed. |
| `company.name` | The hiring company, where the listing names one. |
| `advertiser.name` | The business that placed the listing — often a recruitment agency. Never a person. |
| `location.raw` | Location text as listed. Several locations are joined with `\|`. |
| `location.suburb` | Suburb, when the listing states one. |
| `location.city` | City or area, when the listing states one. |
| `location.region` | State or region, e.g. `VIC`. |
| `location.postcode` | Postcode, when the source provides it. |
| `location.country` | ISO 3166-1 alpha-2 country code. |
| `workArrangement` | `on_site`, `hybrid`, `remote` or `unknown`. |
| `employmentTypes` | Normalised: `full_time`, `part_time`, `contract`, `casual`, `temporary`, `internship`, `volunteer`. |
| `salary.raw` | The salary text exactly as shown, or null when the listing shows none. |
| `salary.min` | Lower bound as a number, when the text contains one. |
| `salary.max` | Upper bound as a number. Equal to min for a single figure. |
| `salary.currency` | ISO 4217. Taken from the text, otherwise the market default. |
| `salary.period` | `hour`, `day`, `week`, `month` or `year`; null when the text does not say. |
| `salary.includesSuper` | true / false when the text says so ("plus super", "inc. super"); otherwise null. |
| `classifications` | The source's category and subcategory pairs. |
| `teaser` | The short summary shown on the results page. |
| `bulletPoints` | Selling points shown on the results page. |
| `postedAt` | When the listing was posted, ISO 8601 UTC. |
| `updatedAt` | The source's own last-modified time, ISO 8601 UTC. Published by ATS and API sources; null where the site does not show one. |
| `expiresAt` | Expiry, ISO 8601 UTC, where the source states one. |
| `isPromoted` | true for paid placements. A listing shown both promoted and organic is returned once. |
| `url` | Link to the listing. |
| `description` | Null unless requested. `text`, optional sanitised `html`, and `contactsRedacted`. |
| `changeType` | Incremental runs: `NEW`, `UPDATED`, `REAPPEARED`, `EXPIRED` (or `UNCHANGED` if you ask for those). Otherwise null. |
| `firstSeenAt` | Incremental runs: when this monitor first saw the listing. |
| `contentHash` | SHA-256 over the fields that define a change. Compare it to detect edits yourself. |
| `scrapedAt` | When this row was produced, ISO 8601 UTC. |
| `source` | Source key, e.g. `seek`. |
| `market` | Market key, e.g. `au`, `nz`. |
| `sourceJobId` | The source's own identifier for the listing. |
| `company.sourceCompanyId` | The source's identifier for the company, when exposed. |
| `company.url` | The company's page on the source site, when exposed. |
| `advertiser.sourceAdvertiserId` | The source's identifier for the advertiser. |
| `schemaVersion` | Always `job.v1`. Breaking changes ship as `job.v2` in a new Actor version, never silently. |

How Lever's fields fill the schema:

- `company.name` is the board's Lever site name, e.g. `employ`. Lever's feed carries no company name, so none is looked up or guessed.
- `location.raw` lists every location the posting names, the primary one first, joined with `|`. `location.country` is Lever's own country code for the posting; where Lever gives none, it comes from what the location text states, never from a city name.
- `classifications` holds Lever's department as `category` and its team as `subcategory`.
- `employmentTypes` comes from Lever's commitment field ("Full-time", "Contract", "Intern"); `workArrangement` from its workplace type (on-site, hybrid, remote).
- `postedAt` is when the posting was created in Lever. `updatedAt` is always `null`: Lever does not publish a last-modified time.
- `market` is always `global`: a Lever board is the company's, not a country's.

### How much does it cost to scrape Lever job boards?

You pay per posting saved to your dataset — **$1.75 per 1,000 postings** on Apify's Starter plan — plus $0.005 each time a run starts. There is no monthly rental.

| Apify plan | Price | Per listing |
| --- | --- | --- |
| Free | $1.75 per 1,000 listings | $0.00175 |
| Starter (Bronze) | $1.75 per 1,000 listings | $0.00175 |
| Scale (Silver) | $1.60 per 1,000 listings | $0.00160 |
| Business (Gold) | $1.45 per 1,000 listings | $0.00145 |

Plus $0.005 per run start. Compute and proxy are included in these prices.

| What you run | Cost (USD, Starter plan) |
| --- | --- |
| 100 listings, one run | $0.18 |
| 1,000 listings, one run | $1.75 |
| 10,000 listings, one run | $17.50 |
| 50,000 listings, one run | $87.50 |
| A daily incremental monitor finding about 150 new or changed listings a day, for a month | $8.03 |

Descriptions cost nothing extra here: they arrive in the same request as the listing. Use incremental mode for anything you run more than once — after the first run you pay only for what changed.

### How to scrape a Lever job board

1. Find the company's board. On its careers page, the "Apply" link or the job list points at `jobs.lever.co/<site>`, or `jobs.eu.lever.co/<site>` for a board hosted in the EU. The site name is what you need; the whole link works too.
2. Open the Actor in Apify Console and go to the **Input** tab. Paste one site name or link per line into **Job boards**. Up to 500 boards per run.
3. Optionally filter: **Title keywords**, **Locations**, **Departments or teams**, **Created within (days)**.
4. Set **Maximum results**. This is also your cost cap.
5. Press **Start**. When the run finishes, open the **Output** tab and export as JSON, CSV, Excel, XML or HTML, or read the dataset through the Apify API.

A posting that matches more than one board or filter is returned once.

### Input

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| `boards` | array | — | One entry per company: the site name (the first part of the path in https://jobs.lever.co/acme is "acme"), or any jobs.lever.co, jobs.eu.lever.co or api.lever.co link. Site names are case-sensitive. A bare site name is read from Lever's global instance; give the jobs.eu.lever.co link for a board hosted in the EU. Up to 500 boards per run; each is one request. |
| `keywords` | array | — | Keep postings whose title contains every word of any keyword, in any order — "engineer data" matches "Senior Data Engineer". Leave empty for all titles. |
| `locations` | array | — | Keep postings with a location containing this text ("Melbourne", "London"), in this country by Lever's own country code ("Australia", "United States"), or with this workplace type ("Remote", "Hybrid", "On-site"). Leave empty for all locations. |
| `departments` | array | — | Keep postings whose department or team contains this text, e.g. "Engineering". Leave empty for all departments and teams. |
| `postedWithinDays` | integer | — | Keep postings created in Lever in the last N days. Leave empty for any time. |
| `maxResults` | integer | `100` | The run stops once this many postings are saved. You are charged per posting saved, so this is also your cost cap. |
| `includeDescription` | boolean | `false` | On: the full posting text — description, lists, pay note and closing section — comes back with each row, read from the same request as the listing, so it costs no extra requests. Off: listing fields only. |
| `descriptionFormat` | `text`, `text_and_html` | `"text"` | Plain text, or plain text plus sanitised HTML. |
| `redactContacts` | boolean | `true` | On by default: email addresses and phone numbers inside description text are replaced with \[redacted]. This Actor never outputs recruiter names or contact fields. |
| `incremental` | boolean | `false` | Remember what earlier runs saw and save only postings that are new, changed or gone. Unchanged postings are skipped and not charged. Put the Actor on a schedule with this on. |
| `stateKey` | string | — | Optional name for this monitor, e.g. "competitor-engineering". Runs with the same key share memory. Left empty, a key is derived from the boards and filters themselves. |
| `emitExpired` | boolean | `true` | Incremental mode only. When a complete run no longer finds a posting it saw before, save one row with changeType EXPIRED. |
| `emitUnchanged` | boolean | `false` | Incremental mode only. Saves (and charges for) every posting, labelled UNCHANGED where nothing moved. |
| `proxyConfiguration` | object | `{"useApifyProxy":true}` | Apify Proxy, automatic group, is the default and is what this Actor is tested with. |
| `maxConcurrency` | integer | `4` | Parallel requests. The default is deliberately modest. |
| `maxRequestsPerMinute` | integer | `90` | An upper bound on request rate across the whole run. |

A typical input:

```json
{
  "boards": [
    "employ"
  ],
  "maxResults": 100
}
```

### Output

One row per posting. This is a synthetic example in the exact shape the Actor returns:

```json
{
  "schemaVersion": "job.v1",
  "id": "lever:global:7d0c9e52-0000-4000-8000-000000000001",
  "source": "lever",
  "market": "global",
  "sourceJobId": "7d0c9e52-0000-4000-8000-000000000001",
  "url": "https://jobs.lever.co/example-freight/7d0c9e52-0000-4000-8000-000000000001",
  "title": "Data Analyst",
  "company": {
    "name": "example-freight",
    "sourceCompanyId": "example-freight",
    "url": "https://jobs.lever.co/example-freight"
  },
  "advertiser": {
    "name": "example-freight",
    "sourceAdvertiserId": "example-freight"
  },
  "location": {
    "raw": "Melbourne, Australia | Sydney, Australia",
    "suburb": null,
    "city": "Melbourne",
    "region": null,
    "postcode": null,
    "country": "AU"
  },
  "workArrangement": "hybrid",
  "employmentTypes": [
    "full_time"
  ],
  "salary": {
    "raw": "The salary range for this role is A$95,000 – A$110,000 per year plus super.",
    "min": 95000,
    "max": 110000,
    "currency": "AUD",
    "period": "year",
    "includesSuper": false
  },
  "classifications": [
    {
      "category": "Data",
      "subcategory": "Analytics"
    }
  ],
  "teaser": null,
  "bulletPoints": [],
  "postedAt": "2026-09-20T22:14:05.000Z",
  "updatedAt": null,
  "expiresAt": null,
  "isPromoted": false,
  "description": null,
  "changeType": "NEW",
  "firstSeenAt": "2026-09-21T19:30:12.000Z",
  "contentHash": "1c6f7d4d4a67a28dc113c5a591bd65c184bca51ccc6358685d26fe5d013fc3c3",
  "scrapedAt": "2026-09-21T19:30:12.000Z"
}
```

The Output tab has two table views: **Overview** (the fields most people want, flattened) and **Changes** (for incremental runs).

### Incremental mode: monitor new roles across companies

Turn on **Incremental mode** and run the same input on a schedule — hourly, daily, weekly. The Actor keeps a small record of what it has seen and every row tells you what happened:

| `changeType` | Meaning |
| --- | --- |
| `NEW` | First time this monitor has seen the posting |
| `UPDATED` | Seen before, and the title, locations, department or team, employment type, workplace type, pay range, created date or any word of the posting text has changed |
| `REAPPEARED` | Was reported as expired and is back |
| `EXPIRED` | Seen before and no longer on the board. One row, once |
| `UNCHANGED` | Only if you turn on **Also save unchanged postings** |

How it behaves, so there are no surprises:

- The first run returns everything as `NEW`. From the second run you pay only for the difference.
- Lever publishes no last-modified time, so a change is found by comparing the posting itself. An edit to the text counts: a corrected typo is reported as `UPDATED` and charged like any other change. A change of formatting alone does not count.
- `EXPIRED` is only ever reported by a complete run. If a run hits your result cap or your spending limit, or a board cannot be read, nothing is declared expired — a posting on a board the run never read is not gone.
- Each board is read in one response, so a run compares whole boards, never pages read seconds apart.
- Runs share memory when they share a **State key**. Leave it empty and the key is derived from the boards and filters themselves, so the same input always continues the same monitor. Name it (`competitor-engineering`) if you want to change filters later without starting again.
- A posting not seen for 45 days is forgotten.

### Descriptions and contact details

Full descriptions are off by default. Turn on **Include full descriptions** and each row carries `description.text` (and sanitised `description.html` if you choose that format): the posting's description, each of its lists under its heading, the company's note on pay and the closing section, in the order Lever's own page shows them. Because Lever returns the posting text in the same response as the listing, this costs no extra requests and no extra time.

Postings sometimes contain a recruiter's email address or phone number. With **Redact contact details** on — the default — those are replaced with `[redacted]` and `description.contactsRedacted` is `true`; so is a personal profile address (linkedin.com/in/…). Neither `description.text` nor the optional HTML carries the address behind a link: the HTML keeps each link's words and drops its address, and drops images. The Actor never returns recruiter names or contact details as fields, under any setting: Lever's public feed has no such fields, and the schema has nowhere to put one. If your use case is contacting individuals, this is the wrong tool.

### What people use it for

- **Competitor and market hiring signals.** Which companies are opening which roles, in which teams and locations, and how often — a daily monitor across a list of boards is one scheduled run.
- **Pay-transparency datasets.** Stated ranges across companies, roles and locations, as numbers with their currency and period, and the company's own wording kept.
- **Job aggregators and alert products.** A clean feed of new postings from a curated list of employers, deduplicated and labelled by change.
- **Sales and partnership research at company level.** Growth signals from hiring, without collecting anything about the individuals involved.
- **Research and teaching.** A clean, repeatable dataset with a documented schema.

### Using the API

Run it from code with the Apify client, using your own API token:

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('adderleydata/lever-jobs-scraper').call({"boards":["employ"],"maxResults":100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]?.classifications);
```

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("adderleydata/lever-jobs-scraper").call(run_input={"boards":["employ"],"maxResults":100})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], item["location"]["raw"], item["postedAt"])
```

Schedules, webhooks and the Make, Zapier, n8n and Google Sheets integrations all work the way they do for any Apify Actor. The Actor runs with limited permissions and is priced per event, so AI agents can call it through Apify's MCP server as well.

### Is it legal to scrape Lever job boards?

The Actor reads Lever's public Postings API — the feed Lever documents for companies building their own careers pages, with no login, no key and no rate tricks — and returns facts about job postings. It does not log in, does not solve CAPTCHAs, and does not collect personal information.

What you do with the data is your responsibility. Each company's postings are its own copyright — analyse them, do not republish them. If your project touches personal information, privacy law applies to you wherever you are. This is general information, not legal advice.

### Questions

**Where do I find a company's site name?** On its careers page, follow any job's link: the address is `jobs.lever.co/<site>/<posting id>`. Paste either the whole link or just the site name. Site names are case-sensitive, so copy it as the link shows it.

**The company's board is on jobs.eu.lever.co.** Lever runs a separate EU instance. Give the `jobs.eu.lever.co` link and the Actor reads Lever's EU API. A bare site name is read from the global instance only: the same site name can belong to a different board on each.

**A board I gave came back as "not found".** Lever answers "Document not found" when the site name does not exist on the instance asked, when its capitalisation differs, or when the company has closed its public job site. The run log names the board, and the other boards in the run are unaffected. Check the link on the company's careers page. A missing board is asked for once, not retried, and a run in which every board is missing finishes with an empty dataset and a message naming each one.

**Does it need a Lever login or API key?** No. The Postings API is public.

**Why is `employmentTypes` sometimes empty?** Lever's commitment field is free text chosen by each company. "Full-time", "Part-time", "Contract" and "Intern" are read; values such as "Permanent" or a program name state no employment type, so none is given. Where the commitment says nothing, a title that says "Intern" or "Contractor" is taken at its word. Nothing else is guessed.

**Why is `updatedAt` always `null`?** Lever does not publish when a posting was last edited. Incremental mode finds edits itself by comparing each posting from one run to the next.

**Can I get recruiter emails or phone numbers?** No, by design.

**How current is the data?** It is read from Lever while your run is in progress. `postedAt` is when the posting was created in Lever; `scrapedAt` records when the row was produced.

**The field I need is not there.** Open an issue on the **Issues** tab. Fields are added to the schema without breaking existing ones.

### Support

Use the **Issues** tab on this page. We read it every day. Include the run ID and what you expected to see.

### Other Adderley Data Actors

Every Actor in a vertical returns the same fields, so adding a source needs no new code on your side.

- [Ashby Jobs Scraper — Company Job Boards](https://apify.com/adderleydata/ashby-jobs-scraper) — same `job.v1` fields
- [Breezy HR Jobs Scraper — Company Job Boards](https://apify.com/adderleydata/breezy-jobs-scraper) — same `job.v1` fields
- [Greenhouse Jobs Scraper — Company Job Boards](https://apify.com/adderleydata/greenhouse-jobs-scraper) — same `job.v1` fields
- [Recruitee Jobs Scraper — Company Job Boards](https://apify.com/adderleydata/recruitee-jobs-scraper) — same `job.v1` fields
- [Rippling Jobs Scraper — Company Job Boards](https://apify.com/adderleydata/rippling-jobs-scraper) — same `job.v1` fields
- [Workday Jobs Scraper — Company Job Boards](https://apify.com/adderleydata/workday-jobs-scraper) — same `job.v1` fields

### About

Made by Adderley Data, Melbourne — https://adderleydata.com. Not affiliated with, endorsed by or sponsored by Lever or Employ Inc. Lever is a trade mark of its owner and is used here only to describe what this Actor reads.

# Changelog

This Actor's version history is a separate document: https://apify.com/adderleydata/lever-jobs-scraper/changelog.md

# Actor input Schema

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

One entry per company: the site name (the first part of the path in https://jobs.lever.co/acme is "acme"), or any jobs.lever.co, jobs.eu.lever.co or api.lever.co link. Site names are case-sensitive. A bare site name is read from Lever's global instance; give the jobs.eu.lever.co link for a board hosted in the EU. Up to 500 boards per run; each is one request.

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

Keep postings whose title contains every word of any keyword, in any order — "engineer data" matches "Senior Data Engineer". Leave empty for all titles.

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

Keep postings with a location containing this text ("Melbourne", "London"), in this country by Lever's own country code ("Australia", "United States"), or with this workplace type ("Remote", "Hybrid", "On-site"). Leave empty for all locations.

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

Keep postings whose department or team contains this text, e.g. "Engineering". Leave empty for all departments and teams.

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

Keep postings created in Lever in the last N days. Leave empty for any time.

## `maxResults` (type: `integer`):

The run stops once this many postings are saved. You are charged per posting saved, so this is also your cost cap.

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

On: the full posting text — description, lists, pay note and closing section — comes back with each row, read from the same request as the listing, so it costs no extra requests. Off: listing fields only.

## `descriptionFormat` (type: `string`):

Plain text, or plain text plus sanitised HTML.

## `redactContacts` (type: `boolean`):

On by default: email addresses and phone numbers inside description text are replaced with \[redacted]. This Actor never outputs recruiter names or contact fields.

## `incremental` (type: `boolean`):

Remember what earlier runs saw and save only postings that are new, changed or gone. Unchanged postings are skipped and not charged. Put the Actor on a schedule with this on.

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

Optional name for this monitor, e.g. "competitor-engineering". Runs with the same key share memory. Left empty, a key is derived from the boards and filters themselves.

## `emitExpired` (type: `boolean`):

Incremental mode only. When a complete run no longer finds a posting it saw before, save one row with changeType EXPIRED.

## `emitUnchanged` (type: `boolean`):

Incremental mode only. Saves (and charges for) every posting, labelled UNCHANGED where nothing moved.

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

Apify Proxy, automatic group, is the default and is what this Actor is tested with.

## `maxConcurrency` (type: `integer`):

Parallel requests. The default is deliberately modest.

## `maxRequestsPerMinute` (type: `integer`):

An upper bound on request rate across the whole run.

## Actor input object example

```json
{
  "boards": [
    "employ"
  ],
  "maxResults": 20,
  "includeDescription": false,
  "descriptionFormat": "text",
  "redactContacts": true,
  "incremental": false,
  "emitExpired": true,
  "emitUnchanged": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "maxConcurrency": 4,
  "maxRequestsPerMinute": 90
}
```

# Actor output Schema

## `postings` (type: `string`):

One row per posting in the job.v1 schema; every key is always present and unknown is null. In incremental runs each row carries a changeType of NEW, UPDATED, REAPPEARED or EXPIRED.

## `runSummary` (type: `string`):

Requests made, first-attempt success, rows saved and skipped, rows that failed validation, and contact details redacted.

# 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": [
        "employ"
    ],
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("adderleydata/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 = {
    "boards": ["employ"],
    "maxResults": 20,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("adderleydata/lever-jobs-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 '{
  "boards": [
    "employ"
  ],
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call adderleydata/lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

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