Lever.co Jobs Scraper & API — Any Company Board
Pricing
from $2.00 / 1,000 job results
Lever.co Jobs Scraper & API — Any Company Board
Scrape any company's Lever job board (jobs.lever.co) on demand — slugs, board URLs or careers-page URLs in, clean JSON out: title, salary, location, remote, apply URL. Delta mode bills only new postings; optional BYOK AI enrichment. No login, no proxies, no HTML parsing.
Pricing
from $2.00 / 1,000 job results
Rating
0.0
(0)
Developer
Nomad.Dev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
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.
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. Pair it with delta mode (onlyNewSinceLastRun) to monitor boards on a schedule and pay only for genuinely new postings, and BYOK AI enrichment (Anthropic or Mistral, your key, your model choice) for skills / seniority / work-arrangement / visa-sponsorship signals at scraper prices.
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. |
postedSince | integer | — | Keep only postings first published within this many days. Postings with no posting date are dropped when this is set. |
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). Opt-in AI/delta fields are always kept. |
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". |
onlyNewSinceLastRun | boolean | false | Delta/monitoring mode: only output postings not seen on a previous run made with this flag on (see "Delta mode / monitoring"). |
aiEnrichment | boolean | false | Adds aiKeySkills/aiExperienceLevel/aiWorkArrangement/aiVisaSponsorship per posting via the Anthropic or Mistral API — BYOK (see "AI enrichment"). |
translateToEnglish | boolean | false | Adds titleEnglish/snippetEnglish per posting, machine-translated via the AI provider — BYOK (see "AI enrichment"). |
companyEnrichment | boolean | false | Adds company-level aiCompanyIndustries/aiCompanySummary per posting, resolved once per company via the AI provider — BYOK (see "AI enrichment"). |
aiProvider | string | anthropic | Which AI provider runs the AI add-ons: anthropic (default, uses anthropicApiKey) or mistral (uses mistralApiKey). |
anthropicApiKey | string (secret) | — | Your Anthropic API key. Only used when aiEnrichment is on and aiProvider is anthropic; billed separately by Anthropic, not by this Actor. |
aiModel | string | claude-haiku-4-5-20251001 | Claude model for AI enrichment (when aiProvider is anthropic): claude-haiku-4-5-20251001 (fast/cheap) or claude-sonnet-4-5 (higher quality). |
mistralApiKey | string (secret) | — | Your Mistral API key. Only used when aiEnrichment is on and aiProvider is mistral; billed separately by Mistral, not by this Actor. |
mistralModel | string | mistral-small-latest | Mistral model for AI enrichment (when aiProvider is mistral): mistral-small-latest (default, fast/cheap — matches larger Mistral models on this task), mistral-medium-latest, or mistral-large-latest. |
concurrency | integer | 8 | Companies fetched in parallel (advanced). |
What Lever jobs data does this scraper extract?
One flat JSON record per live posting:
| Field | Meaning |
|---|---|
ats | Which ATS served the posting (always "lever" here) |
company | Real company display name, resolved from Lever's own job-board page (falls back to the input slug if unresolvable) |
id | Lever's internal posting ID |
title | Job title as posted |
department | Team as categorized by Lever |
location | Location text (may include remote hints) |
url | Direct link to the posting |
postedAt | First-published date (YYYY-MM-DD) where provided |
employmentType | Commitment type (Full-time / Part-time / Contract etc.) where provided, otherwise null |
remote | true/false/null — true when Lever's workplaceType is "remote", false for any other stated value (on-site, hybrid), null only when Lever didn't state a workplace type at all |
snippet | Plain-text description excerpt (optional) |
salary | Compensation display text (e.g. "120,000-180,000 USD year"), or the posting's free-text salary note when no numeric range is given; null when neither is present |
salaryMin / salaryMax | Structured salary range bounds from Lever's salaryRange, or null |
salaryCurrency | 3-letter currency code (e.g. "USD"), or null |
salaryPeriod | Pay period the range covers ("year", "hour", etc.), or null |
globalId | Stable composite id <ats>:<company-slug>:<id> — unique across the whole ATS-actor family, handy for merging with the Greenhouse/Ashby/Workable Actors or the Company Careers Bundle |
raw | Only present when includeRawJson is on — the untouched Lever posting payload (dropped by the compact/minimal output profile) |
warnings | Array of data-quality notes for this record (e.g. ["postedAt missing"]); empty array when there's nothing to flag |
isNew | Only present when onlyNewSinceLastRun is on — always true (already-seen postings are dropped, never emitted with isNew: false) |
aiKeySkills | Only present when aiEnrichment is on — array of skills/technologies explicitly named in the posting text, never invented |
aiExperienceLevel | Only present when aiEnrichment is on — one of entry/mid/senior/lead/unknown |
aiWorkArrangement | Only present when aiEnrichment is on — one of onsite/hybrid/remote/unknown |
aiVisaSponsorship | Only present when aiEnrichment is on — true/false only if the posting explicitly states a policy, otherwise null |
titleEnglish / snippetEnglish | Only present when translateToEnglish is on — the title / description machine-translated into English (unchanged if already English) |
aiCompanyIndustries / aiCompanySummary | Only present when companyEnrichment is on — industry labels and a one-sentence summary for the posting's company, resolved once per company; empty when the model doesn't recognise the company (never guessed) |
How to scrape Lever jobs with this Actor
- Enter one or more company slugs (
palantir,spotify,qonto) — or just the company's careers-page URL (acme.com/careers) and the Actor finds thejobs.lever.co/<slug>board on the page itself. - Optionally set
keyword/titleExclude/locationFilter/postedSince/remoteOnly/ caps. - Run and export JSON, CSV or Excel — or call it over the API:
from apify_client import ApifyClientclient = 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
{"ats": "lever","company": "Palantir Technologies","id": "0bbfd4f4-41ff-4ec6-b73f-5200efd5d4d3","title": "Administrative Business Partner - Security","department": "Administrative","location": "Palo Alto, CA","url": "https://jobs.lever.co/palantir/0bbfd4f4-41ff-4ec6-b73f-5200efd5d4d3","postedAt": "2026-05-12","employmentType": "Full-time","remote": false,"snippet": "Palantir builds the world's leading software for data-driven decisions...","salary": null,"salaryMin": null,"salaryMax": null,"salaryCurrency": null,"salaryPeriod": null,"globalId": "lever:palantir:0bbfd4f4-41ff-4ec6-b73f-5200efd5d4d3","warnings": []}
Only a minority of Lever-hosted companies publish a numeric salaryRange (mostly ones bound by US/EU pay-transparency laws). When they do, salary/salaryMin/salaryMax/salaryCurrency/salaryPeriod look like:
{"salary": "95,000-115,000 USD year","salaryMin": 95000,"salaryMax": 115000,"salaryCurrency": "USD","salaryPeriod": "year"}
Delta mode / monitoring
Set onlyNewSinceLastRun: true to turn this Actor into a "what's new" monitor. Postings already seen on a previous run made with this flag on are dropped before push — you are not billed for them, so pairing this with an Apify schedule (cron) means every run only returns, and only charges for, postings that showed up since the last flagged run.
How it works: seen postings are tracked in a dedicated key-value store, keyed by each posting's globalId, capped at roughly 50,000 entries (oldest evicted first). The first run made with the flag on has nothing to compare against yet, so it emits everything — all isNew: true. Every emitted record gets isNew: true stamped on it; there's no isNew: false in the output, since unseen postings just aren't included.
Runs made with the flag off never read or write this cache — turning it on and off between runs is safe and has no side effects on normal runs.
AI enrichment
Turn on aiEnrichment and supply your own anthropicApiKey (or mistralApiKey, with aiProvider: "mistral") to add four AI-extracted fields to every posting:
| Field | Meaning |
|---|---|
aiKeySkills | Specific skills/technologies/tools explicitly named in the title or description — the model is instructed to never invent one. |
aiExperienceLevel | One of entry / mid / senior / lead / unknown. |
aiWorkArrangement | One of onsite / hybrid / remote / unknown. |
aiVisaSponsorship | true / false only when the posting explicitly states a sponsorship policy, otherwise null. |
The extraction prompt is explicit about never guessing: when the text doesn't clearly support a value you get "unknown" / null / an empty array, not a fabricated answer. Pick the model with aiModel (Anthropic: claude-haiku-4-5-20251001 default, fast/cheap, or claude-sonnet-4-5 higher quality) or mistralModel (Mistral: mistral-small-latest default — matches larger Mistral models on this task, mistral-medium-latest, mistral-large-latest).
Postings are batched (~12 per call) through whichever provider's API you picked (aiProvider). Your Anthropic or Mistral API key is billed separately by that provider, not by this Actor. Rough cost with Haiku or Mistral Small: enriching 100 postings runs well under $0.05 in provider token spend (short prompts, small JSON replies); Sonnet/Mistral Large cost roughly 4-5x that for the same batch.
Enrichment needs a posting's description text even when you have includeDescription off — this Actor fetches it internally for enrichment either way, then still honors your includeDescription choice for what actually ends up in the output snippet field.
If aiEnrichment is on but no matching key is available (anthropicApiKey/ANTHROPIC_API_KEY for aiProvider: "anthropic", or mistralApiKey/MISTRAL_API_KEY for aiProvider: "mistral"), enrichment is skipped: you get one extra dataset row explaining why (warnings: ["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]), a run status message, and every other posting is still returned normally, just without the ai* fields.
This is the same class of field fantastic-jobs' career-site-api prices a whole tier on (ai_key_skills, work arrangement, visa signals) — comparable output here, opt-in and BYOK instead of bundled into every row's price.
Translate to English (translateToEnglish)
Turn on translateToEnglish (with the same BYOK Anthropic/Mistral key) to add titleEnglish and snippetEnglish to every posting — the title and description machine-translated into English. Lever hosts many non-US/EU boards (French, German, …) where this is useful; postings already in English pass through unchanged. If a batch fails, that record keeps its original text (never a fabricated translation) with a note in warnings. It reuses the same batching/provider path as enrichment, so no separate MT service or key is needed.
Company enrichment (companyEnrichment)
Turn on companyEnrichment (same BYOK key) to add company-level aiCompanyIndustries (array) and aiCompanySummary (one sentence) to every posting. These are resolved once per company (one LLM call covers all of a company's rows, so it stays cheap on large boards) and grounded in the company's own postings. Companies the model doesn't recognise get an empty array / empty string rather than a guessed industry or fabricated summary. This approaches jobo.world's nested company object while staying opt-in and BYOK.
Output profile (outputProfile)
Independent of the AI add-ons: set outputProfile to compact to drop the two heaviest text fields (snippet, raw) or minimal to keep only the essentials (title, company, location, remote, salary, url, postedAt, globalId). Any opt-in field you turned on (AI fields, isNew, English translations, company enrichment) is always kept. full (default) returns everything.
Warning rows
Alongside normal posting records, this Actor can push a handful of extra rows that are all null except company/ats/warnings — same flat schema as a posting record, so a dataset-only consumer (no access to the run log) still sees every problem:
| 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"] |
aiEnrichment requested but no API key available | ["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"] |
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.
If you turn on aiEnrichment, your Anthropic or Mistral key is billed separately by that provider for the enrichment calls themselves — see "AI enrichment" above for a rough per-100-postings cost estimate. Delta mode (onlyNewSinceLastRun) only reduces cost: already-seen postings are dropped before the billed push step.
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 — since 2026-07 — you also get one dataset row for it: {"company": "<slug>", "ats": "...", "warnings": ["not found on any ATS probed (...): '<slug>' (404 on every probe)"]} (or "fetch failed on every ATS probed ..." for a network/5xx failure rather than a clean 404). Previously this was only visible in the run log, easy to miss across a 50-slug batch. 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.