Lever.co Jobs Scraper & API — Any Company Board

Scrape any company's Lever job board on demand through the official public postings API — company slugs, board URLs or plain careers-page URLs in, clean structured postings out.

Claude / Codex skill to describe and setup this actor: SKILL.md

Unlike pre-crawled Lever job indexes, this Actor hits the board live at run time: any company on Lever works, including boards added five minutes ago, with no index lag and no ghost jobs.

Input

Field	Type	Default	Description
companies	array	—	Company slugs as used on jobs.lever.co/<slug> — full board URLs and plain careers-page URLs (e.g. acme.com/careers) are also accepted; the Lever board is auto-detected from the page. Leave empty to run a built-in default list of well-known Lever boards (palantir, spotify, aircall, qonto, contentsquare).
keyword	string	—	Case-insensitive substring match on the job title.
titleExclude	array	—	Drop postings whose title contains any of these substrings (case-insensitive).
locationFilter	string	—	Case-insensitive substring match on the location.
postedWithin	string	any	Keep only jobs published inside this window. Use any for no date filter, or a duration — 1h, 24h, 3d, 2w, 6m. Jobs the source gave no date for are dropped rather than guessed at. Replaces postedSince, still accepted for existing integrations.
remoteOnly	boolean	false	Keep only postings Lever flags workplaceType == "remote".
includeDescription	boolean	true	Include a plain-text description snippet per posting.
includeRawJson	boolean	false	Attach the untouched Lever posting payload as a raw field on every record — for power users who want fields this Actor doesn't map.
outputProfile	string	full	How much of each posting to output: full (all fields), compact (drops the heavy snippet/raw text), or minimal (essentials only).
maxItemsPerCompany	integer	100	Cap postings returned per company (0 = no cap). Each result is a billed event. If the cap actually cuts postings for a company, one extra dataset row flags it (warnings: ["truncated ..."]) — see "Warning rows".
maxItems	integer	200	Hard cap on total postings returned (0 = no cap). Each result is a billed event. If the cap actually cuts postings, one extra dataset row flags it (warnings: ["truncated ..."]) — see "Warning rows".
concurrency	integer	8	Companies fetched in parallel (advanced).

What Lever jobs data does this scraper extract?

Published postings follow nomad-agent-job-row-v1. The shared fields carry source identity, title and company, parsed locations, dates, the complete plain-text body when available, source markup when usable, and work type. Unavailable scalar facts are null; no parsed location is []. Source-only facts appear in versioned custom.data only when mapped there. See the Output example section for the exact dataset fields and diagnostic rows.

How to scrape Lever jobs with this Actor

1. Enter one or more company slugs (palantir, spotify, qonto) — or just the company's careers-page URL (acme.com/careers) and the Actor finds the jobs.lever.co/<slug> board on the page itself.
2. Optionally set keyword / titleExclude / locationFilter / postedWithin / remoteOnly / caps.
3. Run and export JSON, CSV or Excel — or call it over the API:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("nomad-agent/lever-jobs-scraper").call(run_input={
    "companies": ["palantir", "spotify", "qonto"],
    "keyword": "engineer",
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["company"], "|", item["title"], item["url"])

curl -X POST \
  "https://api.apify.com/v2/acts/nomad-agent~lever-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["palantir", "spotify", "qonto"]}'

Output example

Every row follows nomad-agent-job-row-v1, the one shape shared by all of this fleet's job Actors. A row carries every field; null means the source did not publish that fact, and locations: [] means no usable location was parsed from the posting. Nothing is guessed.

{
  "schemaVersion": "nomad-agent-job-row-v1",
  "recordType": "posting",
  "source": "lever",
  "id": "a1b2c3",
  "url": "https://example.com/lever/jobs/a1b2c3",
  "title": "Senior Backend Engineer",
  "company": "Example Company",
  "locations": [
    "Bilbao",
    "Spain"
  ],
  "postedAt": "2026-09-02T00:00:00Z",
  "deadline": "2026-10-15",
  "description": "The complete posting body as plain text, exactly as the source published it — never truncated.",
  "descriptionHtml": "<p>The complete posting body as the source's own markup.</p>",
  "workType": "remote",
  "custom": {
    "schemaId": "nomad-agent-job-custom-lever-v1",
    "data": {
      "globalId": "…",
      "department": "…",
      "raw": "…"
    }
  }
}

Field	Meaning
schemaVersion	Always "nomad-agent-job-row-v1".
recordType	"posting" for a job, "diagnostic" for a row reporting something about the run itself.
source	Which job source the posting came from, from the collector registry's vocabulary — not the Actor name.
id	Stable identifier for the posting within source.
url	Canonical public URL of the posting on the source site.
title	Job title exactly as the source publishes it, untruncated.
company	Employer name as published.
locations	Places the role is based, most specific first — e.g. ["Bilbao", "Spain"].
postedAt	When the source published the posting, ISO-8601 UTC (YYYY-MM-DDTHH:MM:SSZ).
deadline	Closing date for applications as an ISO-8601 calendar date (YYYY-MM-DD).
description	The complete posting body as plain text — never truncated, never summarised.
descriptionHtml	The posting body as the source's own markup, preserving lists, headings and links.
workType	Working arrangement: "remote", "hybrid" or "onsite".
custom	Facts only this source publishes, as {"schemaId", "data"}.

A run also emits diagnostic rows — recordType: "diagnostic" with a warnings array — when it has something to report, such as a source returning nothing. They are never billed and are easy to filter out on recordType.

Warning rows

Diagnostic rows use schemaVersion: "nomad-agent-job-row-v1", recordType: "diagnostic", a warnings array and optional docs. They carry no posting fields and are not billed as job results. A dataset consumer can filter them by recordType:

Trigger	Example warnings
A requested company slug 404'd (or hard-failed) on every ATS probed	["not found on any ATS probed (lever): 'acme-corp' (404 on every probe)"]
maxItemsPerCompany actually cut postings for one company	["truncated for 'acme-corp': maxItemsPerCompany=100 returned 100 of 137 matching postings — raise maxItemsPerCompany to get the rest"]
maxItems actually cut the total run	["truncated: maxItems=200 returned 200 of 340 matching postings — raise maxItems to get the rest"]

None of these rows are billed as a result event — only genuine postings are. Pass 50 company slugs in one run and you can tell exactly which ones need fixing straight from the dataset, instead of hunting through the run log.

Integrations

Export results as JSON, CSV or Excel/XLSX, or pipe them straight into Make, Zapier or n8n. Call this Actor synchronously with run-sync-get-dataset-items, or plug it into any AI agent through the Apify MCP server.

Pricing

Pay per event: $0.005 per Actor start and $0.002 per posting returned. 100 postings ≈ $0.21. No subscription — pay only for what you fetch.

Use cases

• Track hiring at specific Lever-powered companies
• Aggregate startup careers pages into one feed
• Recruiting and competitive-hiring intelligence
• Reliable ATS-direct data for job boards and agents

FAQ

Is it legal to scrape Lever jobs? The data comes from the ATS providers' official, public, unauthenticated JSON APIs — the same data any visitor sees on the company's careers page. Review the providers' terms for your use case.

Do I need an API key or login? No. These are public job-board APIs — no authentication of any kind.

What if a company isn't found? The run continues with the other companies and emits an unbilled diagnostic row whose warnings names the missing slug and whether it was a clean 404 or a fetch failure. Full board URLs are also accepted and reduced to slugs automatically. See "Warning rows".

Can remote actually be false, or only true/null? It can be all three. remote is true when Lever states workplaceType: "remote", false when Lever states any other workplace type (on-site, hybrid), and null only when Lever didn't state a workplace type at all.

How fresh is the data? Every run hits the ATS APIs live. No caching layer in between.

Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and fixes ship fast.

Finding this Actor useful? A short review on the Actor's Reviews tab helps other users find it — it takes a minute and is genuinely appreciated.

Related Actors

• Greenhouse Jobs Scraper — Company Job Boards
• Ashby Jobs Scraper — Company Job Boards API
• Workable Jobs Scraper — Company Job Boards
• Company Careers Scraper — Greenhouse Lever Ashby
• Web Developer Jobs Scraper — 10 Boards in One
• LinkedIn Jobs Scraper — No Login, No Cookies

---

From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.