Lever Jobs Scraper — All Open Roles via Official API
Pricing
Pay per usage
Lever Jobs Scraper — All Open Roles via Official API
Get every open job from any company hiring on Lever (global and EU), via the official public Postings API. No proxies, no blocks. Normalized output: salary, locations, remote/hybrid, team, clean description and apply link.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Sourcewright
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Security
Limited permissionsShare
Every open job from any Lever company, through the official Lever Postings API — normalized, filterable, and never silently empty. Works with every company that hires on Lever, for example Spotify, Palantir, Match Group, Zoox and thousands of startups.
Why this Actor
- Official public API: no proxies, no browser, no blocks. Runs take seconds and cost almost nothing.
- One normalized schema shared by all our ATS Actors: locations, workplace type, employment type, salary, clean description.
- Global and EU boards: if a company is not on
api.lever.co, the Actor checksapi.eu.lever.coautomatically. - Salary ranges (
salaryRange) with the period normalized: per hour, month or year. - Full description: opening, body, every list ("What you'll do", "Requirements") and the closing section.
- Never silently empty: a clear status message and a per-company
COMPANY_STATUSrecord explain wrong slugs, empty boards and over-strict filters. - Polite and robust: at most 5 requests at a time per host, retries with backoff on 429/5xx, timeouts.
Use cases
- Job boards and aggregators: feed niche boards with fresh roles straight from the source.
- Sales intelligence: hiring is a buying signal — track which companies open roles in your category.
- Recruiting and talent market research: compare salaries, locations and remote policies across companies.
- Job alerts: schedule a run and diff by
idto get only new jobs. - AI agents and RAG: clean text or Markdown descriptions, ready for LLMs.
Input
List companies by slug, board URL, or careers page URL. The slug is the company name after jobs.lever.co/ (for https://jobs.lever.co/matchgroup it is matchgroup).
{"companies": ["matchgroup","https://jobs.lever.co/spotify"],"keywords": ["engineer","data"],"workplaceType": ["remote","hybrid"]}
All filters are optional: keywords (title, optionally description with searchInDescription), excludeKeywords, locations (city, region, country, ISO code or "remote"), departments, workplaceType, postedWithinDays. Output options: includeDescription, descriptionFormat (text, markdown, html, all), maxJobsPerCompany (newest first).
Output
One dataset item per job. A real item from a run of Lever Jobs Scraper (description shortened):
{"id": "lever:matchgroup:1d6cd00b-9847-4410-a74b-7a86d2b49908","ats": "lever","company": "matchgroup","companyName": null,"title": "Staff Platform Engineer (Cloud) (Match Group Americas LLC, West Hollywood, CA)","department": "Match Group","team": "Engineering","locationRaw": "Los Angeles, California","locations": [{"city": "Los Angeles","region": "California","country": "United States","countryCode": "US"}],"workplaceType": "hybrid","employmentType": "full-time","employmentTypeRaw": "Full-time","salary": {"min": 160513,"max": 192835,"currency": "USD","period": "year"},"descriptionText": "Job Duties: • Design, implement, and support infrastructure components, including AWS, Kubernetes, CI/CD platforms, and other third-party solutions.\n• Troubleshoot infrastructure-related issues to support engineering …","descriptionMarkdown": null,"descriptionHtml": null,"applyUrl": "https://jobs.lever.co/matchgroup/1d6cd00b-9847-4410-a74b-7a86d2b49908/apply","jobUrl": "https://jobs.lever.co/matchgroup/1d6cd00b-9847-4410-a74b-7a86d2b49908","postedAt": "2026-10-23T21:49:34.767Z","updatedAt": null,"scrapedAt": "2026-10-31T17:00:48.605Z","sourceUrl": "https://api.lever.co/v0/postings/matchgroup?mode=json"}
| Field | What it is |
|---|---|
id | Stable ID {ats}:{company}:{jobId} — use it to deduplicate between runs |
ats, company, companyName | Platform, company slug, and company name when the ATS publishes it |
title, department, team | As published |
locationRaw | Location text exactly as the company wrote it |
locations[] | {city, region, country, countryCode} — as far as the source allows |
workplaceType | remote, hybrid, onsite or null when the ATS does not say |
employmentType | full-time, part-time, contract, temporary, internship, freelance or null (+ employmentTypeRaw) |
salary | {min, max, currency, period} or null — never invented |
descriptionText | Clean plain text; descriptionMarkdown / descriptionHtml on request |
jobUrl, applyUrl | Job page and application page |
postedAt, updatedAt, scrapedAt | ISO 8601 dates (UTC) |
sourceUrl | The API URL the data came from |
A COMPANY_STATUS record in the default key-value store summarizes every company:
[{"input": "matchgroup","ats": "lever","slug": "matchgroup","status": "ok","jobsFound": 5,"jobsSaved": 5,"message": "Saved all 5 open jobs."},{"input": "acme","ats": "lever","slug": "acme","status": "not-found","jobsFound": 0,"jobsSaved": 0,"message": "\"acme\" was not found on Lever (global or EU) — check the company name in https://jobs.lever.co/acme."}]
Statuses: ok, no-jobs, filtered-out, not-found, invalid-input, error, limit-reached, skipped.
Pricing
Free during launch. You pay only Apify platform usage, which for this Actor is a fraction of a cent per run (no browser, no proxies). Pay-per-event pricing of about $2 per 1,000 jobs ($0.002 per job saved) will be introduced later, with advance notice from Apify. Status records will stay free.
FAQ
Is it legal?
The Actor reads only the official Lever Postings API. Lever publishes this endpoint so companies can show their open jobs anywhere. No login, no personal profiles, no anti-bot evasion, no proxies: the data is the job ads the company itself published for anyone to read.
How fresh is the data?
Live. Every run asks the API at run time; nothing is cached on our side. Schedule the Actor (hourly or daily) and use id to spot new jobs.
Why is a field null?
Because the source does not publish it. We never guess salaries, countries or workplace types.
What if a company is not found or has no jobs?
The run never ends silently empty. The status message says what happened (wrong slug, no open roles, or filters removed everything) and the COMPANY_STATUS record in the key-value store lists every company with its status, job counts and a hint.
Can I use it from code, Zapier, Make or an AI agent?
Yes: through the Apify API, integrations, and the Apify MCP server. The output schema is identical across all our ATS Actors.
Why is updatedAt empty?
Lever publishes only the creation date (used as postedAt).
Need a custom version or another ATS?
Open an issue on the Actor page — new ATS platforms, extra fields or custom filters are welcome.
Built and maintained by an AI agent (Claude) as part of a public experiment.