Lever jobs API

Every Lever posting carries a real publish timestamp. That sounds unremarkable until you compare it with the four platforms here that publish no date at all.

The endpoint

GET https://api.lever.co/v0/postings/{company}?mode=json

No key, no login. The slug is the path segment in jobs.lever.co/{company}.

curl -s 'https://api.lever.co/v0/postings/acme?mode=json'

What it returns, measured

Measured across every live Lever board in our registry — 46,005 postings from 1,917 boards, not a sample. yes means 99.5% or more; no means the field does not exist on this endpoint.

Field	Lever
Posting date	yes
Description	94.7%
Pay	no
Marked remote	4.8%

Title, company, location and an apply URL come back on every row.

What it is good at

100% of postings are dated with a real timestamp, so a "posted in the last 7 days" filter means exactly that. Descriptions come back on 94.7%, and the department field (Lever calls it team) is present on 99.7%.

Where it falls short

No compensation field, and no work-arrangement field — only 4.8% of rows resolve to remote, and that is a regular expression over the location string rather than anything the employer ticked.

Mistakes that cost us time

Responses are large.: Lever inlines the full description in the list response, so a board with hundreds of postings is a multi-megabyte payload. Measuring all 1,917 boards took six times longer than Ashby with a third of the rows.
mode=json matters.: Without it the endpoint answers with a rendered page rather than the array you want.
categories holds three different things.: Location, team and commitment all live under one nested object rather than as top-level fields.

So should you use it

Yes, for freshness. If your product promises "posted today", this is the platform where that claim survives scrutiny.

No, for remote filtering and pay. Both have to come from somewhere else.

How Lever compares with the other eleven on the same four fields is on the comparison page. If you would rather not write and maintain a client, this Actor reads Lever and emits the same row shape as the other eleven, and ATS Database is a free lookup for finding which platform a given company is on.

Finding the boards

Lever is the clearest example of a coverage gap that was an artefact of the source rather than a fact about the platform. Common Crawl does not crawl jobs.lever.co at all — one URL, domain-wide — so an early count showed 40 Lever boards against Greenhouse's 2,996 and looked like Lever was tiny. The Wayback CDX index has 367 pages of it, which yielded 1,917 live boards. Always check whether a gap is the crawler's blind spot before concluding the segment is small.