Source · LeverLever Jobs API.
Every public Lever posting, one endpoint. Same schema as Workday, Indeed, and 30+ other sources.
Why people are confused about the Lever API
Lever has a documented public Postings API at api.lever.co/v0/postings/<company> - but it has two practical limits. First, you need to know each company's Lever slug in advance (there's no list endpoint that enumerates them). Second, many Lever customers disable the public postings endpoint or use vanity URLs, which means the documented pattern doesn't always work.
JobsPipe indexes every public Lever customer it can identify - including those with vanity URLs and embedded job boards - and normalizes the data into the same schema as our other sources.
Works for customers who haven't disabled the public endpoint and whose company slug you know. There's no list endpoint to discover slugs from.
Possible. Subject to rate limits and HTML drift.
Every public Lever customer, one endpoint, no slug discovery needed.
Lever API documentation
Lever's developer documentation lives at hire.lever.co/developer. The Postings API endpoint that most developers find through search is api.lever.co/v0/postings/<company> - a public, unauthenticated endpoint returning open job postings for a single Lever customer. The catch in production: you must know each company's Lever slug in advance, many customers disable the public endpoint or use vanity URLs, and there's no list endpoint to enumerate Lever customers. JobsPipe's normalized JSON schema is documented at /docs and uses the same shape across Lever, Workday, Greenhouse, and 30+ other sources.
Lever API integration
For a single-tenant Lever integration - sync candidates, post jobs, configure webhooks - you go through Lever's onboarding: get an API key from the customer, scope OAuth permissions, and call api.lever.co/v1. For cross-tenant aggregator integration where you want job postings across many Lever-using companies, JobsPipe is the integration: one API key, every public Lever customer, normalized into the same JSON schema as 30+ other ATSs. Sample request and response are below.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=lever" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "lv_NDg1NzYwMzEtNTk1Yg",
"source": "lever",
"tenant": "ramp",
"title": "Staff Software Engineer, Platform",
"company": "Ramp",
"location": {
"city": "New York",
"region": "NY",
"country": "US",
"remote": false
},
"salary": {
"min": 220000,
"max": 290000,
"currency": "USD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-08T20:15:00Z",
"expires_at": null,
"apply_url": "https://jobs.lever.co/ramp/...",
"description": "Ramp is hiring a Staff Engineer to lead the platform team responsible for shared services across our finance products ..."
}Every Lever job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every Lever job record
FAQ
Why not just hit api.lever.co/v0/postings/<company> directly?+
You can, when you know the company slug and the customer hasn't disabled the public endpoint. JobsPipe is useful when you don't know the slugs in advance or want a normalized schema across Lever + other sources.
How fresh is Lever data?+
Lever postings are re-crawled at least every 24 hours.
Can I get jobs from one Lever company?+
Yes. ?tenant=ramp filters to Ramp's Lever postings (substitute any company slug).
Does JobsPipe include Lever-internal candidate or applicant data?+
No. JobsPipe reads only public job postings.
Try Lever data free - 5,000 requests/month, no credit card.
Get a free API key