Lever Jobs API

Every open job on a company's Lever job board as JSON: titles, teams, locations, commitment, full descriptions

The Lever Jobs API returns every open job on a company's Lever job board (jobs.lever.co/<company>) as JSON: id, title, link, location and all locations, department, team, employment type (Lever's commitment), workplace type (on-site, hybrid or remote), posted date, apply link and the full description as HTML and plain text, with Lever's separate sections (responsibilities, requirements, closing text) joined into one.

endpoints
2
credit per call
1

1 credit per call≈ $1/1,000 calls1,000 free credits, no card

2 active endpoints. Every call is 1 credit.

  • POST/lever/v1/company_jobs1 credit
  • POST/lever/v1/job_detail1 credit
Try it live

Run the call yourself, on the real endpoint

Change a parameter and press Try it. The response on the right is what your code will receive.

Lever Jobs API

2 of 2 endpoints, ready to run

View docs ↗

Every open job on one company's Lever board, full descriptions included, in one call

1 credit1 required · 1 optional
POST/lever/v1/company_jobs
idle
// Press "Try it" and this pane shows exactly what the
// live site returned this second — including an empty
// result, if that is the truth. No key, no account.

Try every endpoint in the playground

Endpoints

What Lever Jobs endpoints does ReefAPI ship?

2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.

2 endpoints

company_jobs

1 cr

Every open job on one company's Lever board → jobs[] (id, title, url, company, location, loca…

required
company
optional
limit, cursor, page

job_detail

1 cr

One Lever posting in full by company + job_id.

required
company, job_id
optional
—

Every parameter, every allowed value →

Missing a Lever Jobs endpoint, or need a source we don't have yet?Contact us real people · same-day reply.
How it works

How the Lever Jobs API works

Lever Jobs is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.

01
Authenticate
x-api-key header

No OAuth app, no request signing, no per-site account. One key covers all 746 engines.

02
Call
POST /lever/v1/…

Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.

03
Pay
1 credit per call

Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.

04
Read
{ ok, data, meta, error }

One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.

Recipe

From a company's Lever board to every open role by team and city

Read the whole board once, then open single postings when you need them again. Old POST /ats-jobs/v1/... calls keep working unchanged; the call for Lever on its own is POST /lever/v1/<action>.

01company_jobs
POST/lever/v1/company_jobs
{"company": "spotify"}

On 2026-11-21 Spotify's Lever board held 91 open jobs; 20 came back in 2.0 seconds with limit 20, each with title, team, department, location, commitment, workplace type, posted date, apply link and the full description.

02job_detail
POST/lever/v1/job_detail
{"company": "spotify", "job_id": "2a55d6c9-c564-443a-be3e-a3851db5a93b"}

One posting in full. A job id works only while the role is open: of 3 older ids sent by a customer, 1 answered and 2 were NOT_FOUND because the roles had closed.

The company's own list of open roles with team, department, city, commitment, on-site/hybrid/remote, posted date and full description.

request
curl -X POST https://api.reefapi.com/lever/v1/company_jobs \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"company":"spotify"}'
response envelope
{
  "ok": true,
  "data": { … },
  "meta": {
    "api": "lever",
    "endpoint": "company_jobs",
    "mode": "live",
    "latency_ms": …,
    "record_count": …
  },
  "error": null
}
Fields

What a Lever job field contains

Fields that read differently from how they look. Each row was measured on Spotify's Lever board through this API on 2026-11-21.

FieldWhat it holds
company (request)The company slug from the board's link (spotify in jobs.lever.co/spotify). A pasted Lever link is accepted. A wrong slug answers NOT_FOUND.
idLever's posting id, a lowercase UUID (2a55d6c9-c564-443a-be3e-a3851db5a93b). Valid only while the role is open.
department, teamLever's two category levels, both filled on 20 of 20 Spotify rows (Operations and Business Support / Platform).
employment_typeLever's commitment: full_time on 17 of 20 Spotify rows, empty on 2, "short term" on 1. Non-standard commitments are passed as written.
workplace_type, remoteon-site, hybrid or remote as Lever states it (hybrid 12, remote 4, on-site 4 on Spotify); remote is true only for remote.
posted_dateLever's creation time in UTC to the millisecond (2026-10-23T15:00:40.768+00:00).
description_textLever's intro, list sections and closing text joined in order: 3,340 to 5,929 characters on Spotify's rows.
requisition_idLever's requisition code when the employer sets one. Empty on all 20 Spotify rows.

count is the number of rows in the response, total the number of open jobs on the board (20 and 91 for Spotify with limit 20).

Coverage

What a Lever board returns, measured

Every number below was read through this API on 2026-11-21.

One board, one call

Spotify: 91 open jobs on the board. company_jobs returns the whole board without paging; limit caps how many rows come back.

Fields on every row

On 20 Spotify rows: title, link, location, department, team, workplace type, posted date, apply link and full description (3,340 to 5,929 characters of text) on 20 of 20; employment type on 18 of 20 (17 full time).

Cities and workplace

New York 7, London 4, Stockholm 4, Toronto, Berlin and Seoul 1 each; hybrid 12, remote 4, on-site 4.

Pay

Lever has no salary field in its public board. salary is read from the posting text when it prints a range: 2 of 20 Spotify rows, e.g. USD 87,069 to 124,385.

Dates

posted_date is Lever's creation time in UTC to the millisecond (2026-10-23T15:00:40.768+00:00); Spotify's rows ran from 2026-09-02 to 2026-11-18.

Limits

requisition_id was empty on all 20 Spotify rows. Commitment is passed as the employer wrote it when it is not a standard term ("contractor or consultant via procurement"). No recruiter names, no applicant data, and no cross-company search: you need the company's Lever slug.

Use cases

What people build with Lever Jobs

The jobs this data is most often used for.

2

endpoints

1

credit per call

01

Track new openings at target companies straight from their Lever boards, by team and city.

02

Build a job board or alert from employers' own Lever listings, filtered to remote or hybrid roles.

03

Measure a company's hiring by department, team and office.

04

Merge Lever, Greenhouse, Ashby and Workable boards into one list without remapping fields.

Pricing

What Lever Jobs data costs

The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.

Full pricing →
$0.67–$1.50 / 1,000 credits
  • 1,000 free credits on signup, no card
  • One key, all 746 APIs, one credit pool
  • Failed and blocked calls are never charged
  • Credits roll over and never expire
no credit card1,000 free credits · instant API key · pay by card or crypto
Quickstart

Call it in two lines

Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.

curl
curl -X POST https://api.reefapi.com/lever/v1/company_jobs \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"company":"spotify"}'
python
import os
import requests

REEF_KEY = os.environ["REEF_KEY"]

r = requests.post(
    "https://api.reefapi.com/lever/v1/company_jobs",
    headers={"x-api-key": REEF_KEY},
    json={
        "company": "spotify"
    },
    timeout=90,
)
print(r.json()["data"])
FAQ

Have a question? We got answers.

The questions people actually ask before wiring up Lever Jobs.

Is there a Lever API?▾

Yes. The lever API on ReefAPI returns every open job on a company's Lever board as JSON, with team, department, commitment, workplace type and full description, in the same shape as the Greenhouse, Ashby and Workable APIs. Lever's own postings API is public for reading a board and needs no key. The call is POST /lever/v1/<action>; old POST /ats-jobs/v1/... calls with ats lever keep working unchanged.

What do I pass as company?▾

The company slug: the name in the board's link, spotify in jobs.lever.co/spotify. A wrong slug answers NOT_FOUND rather than another company's jobs.

How many jobs come back per call?▾

The whole board. company_jobs has no paging: Spotify's 91 open jobs come back in one call, and limit (1 to 2,000) caps how many rows you take.

Does it say whether a job is remote or hybrid?▾

Yes, when the employer sets it in Lever. Spotify's rows on 2026-11-21 were hybrid 12, remote 4 and on-site 4, returned as workplace_type.

Does it return salaries?▾

When the posting prints them. Lever's public board has no salary field; salary is read from the text and was present on 2 of 20 Spotify jobs, e.g. USD 87,069 to 124,385.

Can I search across all Lever companies?▾

No. Lever publishes one board per company and no cross-company index, so you need each company's slug. For a keyword search across companies, the workable API searches every company hiring on Workable.

Why does job_detail say NOT_FOUND for an id I saved?▾

The role has closed. A Lever job id is valid only while the posting is open: of 3 older ids a customer sent on 2026-11-21, 1 answered and 2 had closed. Call company_jobs for current ids.

What is the Lever Jobs API?▾

Lever Jobs API is a ReefAPI endpoint group for every open job on a company's lever board in one call: title, team, department, city, commitment, remote or hybrid, full description. It returns live JSON through POST requests under /lever/v1.

Is the Lever Jobs API free to try?▾

Yes. ReefAPI starts with 1,000 free credits, no card required. Lever Jobs calls use the same shared credit balance as every other ReefAPI engine.

Do I need a Lever Jobs login or account?▾

No login to Lever Jobs is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the Lever Jobs data?▾

The page example is captured from a live company_jobs call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the Lever Jobs API use?▾

Lever Jobs actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Can I call Lever Jobs from an AI assistant or MCP client?▾

Yes. Connect ReefAPI once through MCP and your assistant can call lever actions with the same key, credit pool and JSON envelope used by normal REST requests.

Is the Lever Jobs API a Lever Jobs scraper?▾

It is the managed alternative to a DIY Lever Jobs scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same every open job on a company's lever board in one call: title, team, department, city, commitment, remote or hybrid, full description back as clean JSON.

Same key

36 Jobs & Hiring APIs on the same key

One key, one credit pool, one response envelope. If you are pulling Lever Jobs, you are one call away from the rest of the category — no second contract, no second integration.

Already paying for something else?Lever Jobs vs Bright DataLever Jobs vs SerpApi
Contact

Need something this API does not do?

Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.

0/4000

No account needed · we reply from [email protected]

Try it on your own data before you pay anything

The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 745 APIs, and the same envelope everywhere.

Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-21.