Lever Jobs Scraper

---

🎯 What this scrapes

Any employer running its careers page on Lever serves the entire board from one endpoint: https://api.lever.co/v0/postings/{token}. This Actor hits it directly — hand it one or more company tokens (the {token} in https://jobs.lever.co/{token}, e.g. palantir) and it pulls every currently-open posting for that employer in a single response, no pagination to chase, and normalizes it into one row schema. We've verified it end to end against real boards ranging from a zero-posting tenant to a 388-posting demo board, so the same code path holds whether a company has zero reqs open or hundreds.

🔥 Features

• 🔑 Keyless public API — no OAuth, no token, no per-company setup; the same JSON endpoint Lever's own hosted careers page renders from.
• 🏢 Multi-company in one run — pass many tokens; rows come back identically shaped, tagged with company.
• 🧭 Token or full URL, either works — paste a bare company token or the full https://jobs.lever.co/{token} link and we extract the right identifier from the URL path.
• 🎛️ Server-side filtering — narrow by team, department, location, or commitment before the payload is even sent, instead of pulling everything and filtering client-side.
• 🚫 Clean invalid-token detection — an unknown or unused token gets a plain 404, and we skip that company and keep going instead of choking on it or the run silently producing nothing.
• 🧩 Independent team + department fields — never collapsed into a single fallback like a shallower multi-ATS integration might do; both fields, and the full remote / on-site / hybrid workplace-type enum, come through untouched.
• 📋 Full requirement lists — the lists[] responsibilities/requirements blocks ship HTML-stripped to plain text, alongside the complete job description.
• 🔁 Retries with backoff + fingerprint rotation — curl-cffi presents a real browser handshake and retries transient 429/5xx responses with exponential backoff up to 5 attempts, so a large multi-company batch finishes instead of dying on the first hiccup.
• 🌐 Proxy-routed through Apify Proxy — every request runs through a rotating session, with a fresh exit IP requested the moment anything looks off — the same infrastructure we lean on harder the day a target tightens up.
• 🧊 Clean, typed rows — Pydantic-validated, ISO-8601 timestamps, stable posting IDs. Export JSON / CSV / Excel straight from the Apify Console.
• 💰 Pay only for postings that land — a company with an invalid token or zero open reqs never gets billed for rows it didn't produce.

💡 Use cases

• Recruiting & talent intelligence — track what a Lever-hosted employer is hiring for, on which team, in which department, and under what workplace arrangement.
• Job-board aggregation — add Lever coverage alongside Greenhouse / Ashby / Workday / Teamtailor in one pipeline.
• Labor-market research — sample hiring demand across an industry or region by team, department, and commitment type.
• Hiring-intent signals for BD/SDR teams — a sudden spike in open reqs at a target account is a lead qualifier.
• HR-tech data pipelines — wire structured job rows, including full requirement text, into your CRM, dashboard, or n8n / Make workflow on a schedule.

⚙️ How to use it

1. Click Try for free at the top of the Store listing.
2. Add one or more Companies — the {token} from a https://jobs.lever.co/{token} careers URL (e.g. palantir), or paste the full URL.
3. Optionally set Team, Department, Location, or Commitment to filter server-side before any data is fetched.
4. Optionally adjust Max items per company (default 200) if a board has more open reqs than you need.
5. Click Start. Each company's full board comes back in one fetch and rows stream into the dataset.
6. Export from Storage → Dataset as JSON, CSV, or Excel — or pull via the Apify API.

📥 Input

Field	Type	Required	Default	Notes
companies	array	✅	—	Lever company tokens (the {token} in https://jobs.lever.co/{token}, e.g. palantir), or full https://jobs.lever.co/{token} URLs — either form works.
team	string	no	—	Optional server-side exact-match filter on categories.team, applied to every company in this run.
department	string	no	—	Optional server-side exact-match filter on categories.department, applied to every company in this run.
location	string	no	—	Optional server-side exact-match filter on categories.location, applied to every company in this run.
commitment	string	no	—	Optional server-side exact-match filter on categories.commitment (e.g. "Full-time"), applied to every company in this run.
maxItems	integer	no	200	Cap on rows emitted per company, applied client-side after the full board is fetched (no server-side limit param exists on this vendor).
proxyConfiguration	object	no	{"useApifyProxy": true}	Apify Proxy configuration.

Example input

{
  "companies": ["leverdemo", "plaid"],
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true }
}

📤 Output

One dataset item per open job posting.

Field	Type	Notes
posting_id	string	Stable Lever posting ID.
company	string	Normalized token you supplied — kept stable across repeat runs.
title	string	Job title.
team	string | null	Team label; independent of department, never collapsed into it.
department	string | null	Department label; null when the employer didn't set one.
location	string | null	Primary free-text location.
workplace_type	string | null	One of "remote", "on-site", "hybrid"; null when unset or unrecognized.
commitment	string | null	Freeform employment type as published (e.g. "Full-time", "Scholarship"); never a fixed enum.
hosted_url	string	The real, working posting page — used verbatim, never reconstructed.
apply_url	string	The real, working apply page — used verbatim.
created_at	string	ISO-8601 timestamp the posting was created.
description	string	Full plain-text job description.
lists	array	Requirement/responsibility blocks, each {text, content}, HTML-stripped to plain text.
scraped_at	string	UTC ISO-8601 fetch timestamp.

Example output

{
  "posting_id": "ac978161-6f46-4f6b-ad9e-a258e642751c",
  "company": "palantir",
  "title": "Administrative Business Partner",
  "team": "Administrative",
  "department": null,
  "location": "London, United Kingdom",
  "workplace_type": "hybrid",
  "commitment": "Full-time",
  "hosted_url": "https://jobs.lever.co/palantir/ac978161-6f46-4f6b-ad9e-a258e642751c",
  "apply_url": "https://jobs.lever.co/palantir/ac978161-6f46-4f6b-ad9e-a258e642751c/apply",
  "created_at": "2024-03-25T22:30:16.463Z",
  "description": "A World-Changing Company\n...",
  "lists": [
    {"text": "What We Require", "content": "At least three years...\nExcellent digital literacy..."}
  ],
  "scraped_at": "2026-07-29T15:00:00Z"
}

💰 Pricing

Pay-Per-Event — you're charged only when these fire:

Event	USD	What it covers
actor-start	$0.005	One-off warm-up per run
result	$0.0015	Per job posting written to the dataset

Example: 1 000 postings ≈ $1.51. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

🚧 Limitations

• Public postings only — the openly published careers board, not authenticated internal/employee views.
• Company tokens, not company names — you supply the Lever token from the careers URL; a display name like "Palantir" may not match its actual token.
• No multi-location breakout — location returns the primary posting location; the full allLocations[] array for multi-location postings isn't row-exploded in v1.
• Salary is not modeled — some Lever tenants expose salary text, others don't; this Actor doesn't parse or emit it in v1 either way.
• Point-in-time snapshot — returns the board as it stands right now; schedule recurring runs to track changes.
• No anti-bot wall observed on this vendor today — Lever's public API hasn't shown rate-limiting or blocking in our testing, but the retry, backoff, and fingerprint-rotation stack ships anyway and takes over the moment that changes, so a future tightening doesn't turn into a broken run.

❓ FAQ

Do I need a Lever account or API key?

No — every field comes from Lever's own public JSON API, the same one the careers page itself renders from.

How do I find a company's token?

It's in the careers URL: https://jobs.lever.co/{token}. Paste that {token} (e.g. palantir), or just paste the full URL — we extract it either way.

Can one run cover several employers?

Yes — put multiple tokens in companies and every row comes back identically shaped, tagged with company.

What happens if I typo a token or it doesn't exist?

Lever returns a clean 404 for an unknown or unused token. We detect that, skip the company, and report it plainly in the run's status message — the rest of your batch still completes.

Can I filter to just one team or department before I pay for rows I don't need?

Yes — set team, department, location, or commitment and Lever narrows the results server-side before the response is ever sent.

Is this legal?

We fetch public, unauthenticated job-posting data that employers publish for candidates. No login, no private endpoints.

💬 Your feedback

Spotted a bug, hit a company that behaves differently, or need an extra field? Open an issue on the Actor's Issues tab in Apify Console — we ship fixes weekly and read every report.

---

🔗 Related Devil Scrapes Actors

Hiring intel across the whole ATS landscape? These siblings cover the other major job-board platforms — same keyless, pay-per-result approach:

• Breezy HR Jobs Scraper — postings from any Breezy HR-powered career board
• Teamtailor Jobs Scraper — postings from any Teamtailor-powered career site
• BambooHR Jobs Scraper — postings from any BambooHR-hosted careers page
• Recruitee Jobs Scraper — postings from any Recruitee-powered career site
• Multi-ATS Jobs Scraper — one normalized feed across Greenhouse, Lever & Ashby

Browse the full fleet at apify.com/DevilScrapes.