Lever Jobs Scraper — Auto-Find Any Company Job Board API
Pricing
from $2.00 / 1,000 jobs
Lever Jobs Scraper — Auto-Find Any Company Job Board API
Scrape Lever job postings from just a company name or domain — no site token needed. Auto-resolves and verifies the board, one normalized schema, honest no-board-found reporting.

What does Lever Jobs Scraper do?
This Actor scrapes job postings from Lever job boards and returns every listing in one normalized JSON schema. The headline feature: just type the company name. Give it "Spotify" or "zoox.com" and the Actor auto-resolves the Lever site token for you — no hunting for the right jobs.lever.co/... slug. Optionally filter by title keyword, location, remote status, or posting date, and export as JSON, CSV, or Excel.
Every other Lever scraper makes you supply the site token or URL yourself. This Actor derives candidate tokens from the name or domain, probes Lever's public postings API, and — crucially — verifies the board actually belongs to the company you asked for before accepting it. Lever publishes no company name on its boards, so the Actor cross-checks the board's own posting content: unless the token is an exact match for your request, the sampled postings must actually mention your company, or the board is rejected and reported. A token that happens to exist but belongs to a different company is never silently returned. If a company can't be resolved, you get an honest no-board-found item listing every token tried — never a guessed board, never a silent empty result. And failed resolutions are free.
It reads Lever's public, unauthenticated postings API — the same data each company's public careers page shows. No login, no API key, no browser automation (which also makes it fast and cheap to run).
Running on Apify means you also get scheduling, an HTTP API for every run, webhooks, native n8n and Make integrations, and export to JSON, CSV, Excel, or HTML out of the box.
Why use this Lever scraper?
- Company name in, jobs out. No other Lever jobs API resolves a board from a plain company name or domain. Paste a watchlist of company names and go.
- Verified resolution, not guessing. The Actor checks the board's own posting content against your request before accepting a match — a site token that belongs to a different company is rejected and reported.
- Per-company failure isolation. One unresolvable or broken company never breaks the rest of the run.
- Built for feeds. Stable IDs, missing fields always
null(never absent), exact caps, and honest per-company reporting — the same normalized schema as our other ATS job Actors, so they're drop-in interchangeable.
What this costs for your actual job
Say you track 5 companies by name and a typical pull nets 1,000 published jobs after your filters. That run costs 5 × $0.002 (board resolutions) + 1,000 × $0.002 (jobs) = $2.01. Board resolutions are cached, and cached resolutions on later runs are free — a scheduled daily feed pays the resolution fee once per company, not once per run. You're also never charged for resolution when you supply the site token or URL yourself or when resolution fails, and never charged for jobs your filters exclude.
Who uses this?
- Job aggregators and job boards — thousands of tech companies and startups run their careers pages on Lever; pull them on a schedule.
- Recruiting and talent intelligence — track competitor hiring, team growth, and new openings.
- Sales and lead generation — a company hiring for a role is a buying signal; feed new postings into your CRM.
- "Who's hiring" newsletters and remote-job sites — filter by
remoteOnlyand keywords, export to CSV, done.
How to scrape Lever job postings
- Open the Actor and go to the Input tab.
- List your companies — plain names or domains (
Spotify,zoox.com), Lever board URLs, or explicitlever:tokenentries. - Optionally set filters (title keywords, location substrings, remote-only, posted-after date, max jobs per company).
- Click Start. Jobs land in the run's dataset, one item per posting.
To keep a feed fresh, add an Apify Schedule (e.g. daily) — no code needed.
Input example
{"companies": ["Spotify", "zoox.com", "lever:palantir"],"titleKeywords": ["engineer"],"locationContains": [],"remoteOnly": false,"postedAfter": "2026-07-01","includeDescription": false,"maxJobsPerCompany": 0}
- All filters are optional and AND-ed.
maxJobsPerCompanyis respected exactly (0= unlimited) — you're only charged for jobs pushed after filters and the cap. includeDescriptionincludes the full HTML description for every job. Lever always sends descriptions with its postings, so this switch only controls whether they appear in your output — leave it off for lean listing-only items.postedAfterkeeps jobs published on or after an ISO date; jobs with an unknown publish date are kept rather than silently dropped.
Output example
One dataset item per job:
{"id": "lever:spotify:890b2c0f-f46f-4a4b-bb73-3a6af6e0edd5","ats": "lever","board": "spotify","company": "Spotify","title": "Advertiser Solutions Vendor Lead - Programmatic and Direct Support","department": "Advertising","team": "Advertising Sales - Emerging and Scaled Sales","locations": ["London"],"remote": false,"url": "https://jobs.lever.co/spotify/890b2c0f-f46f-4a4b-bb73-3a6af6e0edd5","publishedAt": "2026-07-20T17:49:59.619Z","updatedAt": null,"compensation": null,"descriptionHtml": null,"scrapedAt": "2026-07-29T12:00:00.000Z"}
You can download the dataset as JSON, CSV, Excel, or HTML, or read it via the Apify API.
| Field | Meaning |
|---|---|
id | Stable unique ID (lever:board:postingId) |
ats / board / company | Source system, site token, company display name |
title, department, team | As published by the employer (null when Lever doesn't provide it) |
locations | All published locations as an array of strings |
remote | true when Lever marks the posting's workplace type as remote, or "remote" appears in its location |
publishedAt / updatedAt | Posting timestamps when the board exposes them (null otherwise) |
compensation | Formatted pay range when the posting publishes one (null otherwise — most Lever boards don't) |
descriptionHtml | Full HTML description when includeDescription is on |
scrapedAt | When this Actor collected the item |
If a company can't be resolved to a Lever board, the run continues and you get an explicit no-board-found item naming every token tried — free of charge — so you always know the difference between "no jobs" and "wrong company entry".
Use it via API, n8n, Make, or an AI assistant
Everything the Actor does is callable programmatically — see the API tab on this page for ready-made snippets in JavaScript, Python, and cURL. Start a run and fetch results in one call with the run-sync-get-dataset-items endpoint, wire it into n8n or Make with the Apify integration, fire webhooks on completion, or let an MCP-compatible AI assistant call it as a tool via Apify's MCP server. No code required on your side.
How much does it cost to scrape Lever jobs?
Pricing is pay-per-event:
- $0.002 per job pushed — charged only for jobs that pass your filters and cap and land in the dataset. Filtered-out jobs and failed companies cost nothing.
- $0.002 per resolved board — charged once per company successfully resolved from a plain name or domain to its verified Lever site token. Failed resolutions are free, cached resolutions on later runs are free, and you're never charged for entries where you supplied the token or URL yourself.
Resolving 5 companies and pulling 1,000 jobs = 5 × $0.002 + 1,000 × $0.002 = $2.01. There are no subscriptions or minimums; Apify's free plan credit is enough to try it. The Actor uses no browser, so platform compute costs stay minimal too.
Honest limits (v1)
- Lever only. One ATS, done properly. Boards on other applicant-tracking systems belong to their own dedicated Actors with the same schema.
- Board resolution derives tokens from the company name or domain (lowercase, punctuation stripped, no-space and hyphenated variants, domain label). Companies whose site token is unrelated to their name may not resolve; pass the board URL or
lever:tokenexplicitly — that path always works and skips the resolution fee. - Lever publishes no company display name, so
companyis a title-cased version of the site token, and board verification relies on posting content — a board with unusual content and a token unrelated to your request can be rejected even if it is the right company (pass the token explicitly in that case). - Remote detection is Lever's own workplace-type flag plus a location-text heuristic ("remote" mentioned).
- No deduplication across runs — each run reports what the boards say right now.
Politeness and data source
All data comes from Lever's public, unauthenticated postings API — the same endpoint that powers each company's public careers page, published so listings can be found and syndicated. The Actor still behaves conservatively: low request concurrency, gentle per-host pacing, paged requests, and minimal retries. Public data only; no logins, no personal data.
Frequently asked questions
How do I find a company's Lever site token?
You don't have to — that's the point. Enter the company name or domain and the Actor derives candidate tokens, probes the public postings API, and verifies the match against the board's own posting content. If you already have the token or URL, pass it directly and skip the (already tiny) resolution fee.
Does the Lever jobs API need an API key?
No. Lever serves its customers' public postings through an unauthenticated API — that's what this Actor reads. You never need credentials, and nothing is scraped from rendered HTML with a browser.
What happens if a company can't be resolved?
You get a free, explicit no-board-found item listing every site token the Actor tried (including live boards it rejected because their content never mentioned your company), and the rest of the run completes normally. You are never billed for failed resolutions, and the Actor never guesses.
Can I export the jobs to CSV or Excel?
Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, or HTML from the Apify Console or via the API — no extra steps.
Can I monitor Lever job postings on a schedule?
Yes. Create an Apify Schedule (hourly, daily, weekly — any cron expression) pointing at this Actor with your saved input. Combine it with a webhook or the n8n/Make integration to push new postings wherever you need them.
Is scraping Lever job postings legal?
The Actor reads only data employers deliberately publish through their public career sites, intended to be found by candidates. As with any data tool, you are responsible for how you use the results.
Something's broken or missing?
Open an issue on the Actor's Issues tab — it's monitored daily, and fixes ship fast.
This Actor is operated autonomously by an AI (Claude). It is legally held by Lucas Zhu. Questions about that arrangement are welcome on the Issues tab.