Lever Jobs Scraper: Any Board, No API Key

Every open role from any Lever job board, by company domain or board token. Titles, locations, teams, commitment type and full descriptions as clean JSON. No API key and no proxy: give it a domain and it finds the board itself.

What people use this for

Hiring data is not really about jobs. It is the earliest public signal a company gives that something changed, and it is why three different kinds of buyer end up on the same dataset:

• Sales and go-to-market. A company that opens six engineering roles this month is a company with new budget. Job postings say which team is growing and in which city, weeks before anything shows up in a funding announcement.
• Investors and market research. Headcount by function, tracked over time, across a whole portfolio or a whole sector. Every row carries the company, the team and the date, so a weekly run is a time series.
• Recruiting and talent. Where a competitor is hiring, which roles they have been trying to fill for months, and how fast a team is growing. Lever does not publish pay, so no row here claims to know it.

Run it once for a snapshot. Run it on a schedule and the same rows become a record of who started growing and when.

You do not need the board token

{ "companies": ["palantir.com"] }

Every other lever Actor asks you for a board token, and there is no directory mapping a company to its token. This one derives candidates from the domain and verifies each against the live API, which is sound because lever answers 404 for a board that does not exist and 200 for one that exists with nothing open. A 200 is proof, not a maybe.

Measured across 30 companies, deriving and verifying resolved 90% against 50% for reading the careers page for a link. Stripe's careers page is a JavaScript app that names no board at all, and it still resolves.

What makes lever different

• Measured: palantir 302 open roles, spotify 105, walkme 53.

• Lever answers with a bare JSON array, not an object with a jobs key like every other system here. A client written for Greenhouse reads that as zero results.

• Lever carries commitment (full time, intern, contract) and a plain-text description, so no HTML parsing is needed at all.

Filters that cost you nothing

{
  "boards": ["palantir"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true
}

Filtered rows are not charged. Keywords match as plain text, so c++ and node.js mean exactly that rather than being read as regular expressions.

What you get

Field
title	the role as the company wrote it
location	as published, not normalised
url	the public posting, ready to open
jobId	the ATS's own id, stable across runs
postedAt	ISO 8601 UTC
departments	list
offices	list
description	opt in, off by default because it is expensive at the source
employmentType	full time, contract, intern, as the source says
company	what you asked for, echoed back
atsPlatform	which system it came from
boardToken	the board id used
boardUrl	the public board this came from

Looking for an Indeed or Glassdoor API? There isn't one, and this is why you don't need it

Indeed has no public jobs API. Neither does Glassdoor, ZipRecruiter or LinkedIn Jobs, and all four block you at the edge. Measured from an ordinary residential address on 2026-08-01, with normal browser headers:

indeed.com/jobs          403      0 bytes
glassdoor.com/Job/...    403      0 bytes
ziprecruiter.com         403      0 bytes
upwork.com/nx/search     403      0 bytes

Zero bytes. Cloudflare rejects the request before it reaches an application, so there is nothing to parse and no proxy budget that fixes it.

But none of those four originate job data. They aggregate it from company career pages, and those pages run on systems like lever that publish a free, keyless, public API, because companies want their openings indexed. That API answered with real jobs from the same connection, in the same minute.

Going to the source is also fresher. An aggregator shows you its last crawl. This shows you the board.

Notes

• The source is a public API that companies publish deliberately. Nothing here is behind a login, a paywall or a bot wall.
• An empty board is a real answer and is reported as one.
• Errors are per company. One bad token does not end the run, and error rows are not charged.