Lever Jobs Feed: every posting from any Lever board | $1.50/1K

Quick start

• Lever jobs API in one run: one JSON row per open posting on every Lever board you list, with title, location, team, apply URL, posted date and a stable id.
• Minimal input: {"boards": ["lever:spotify"]}
• Run it from the Console, the API, or the Apify MCP server; export JSON, CSV or Excel.

Pull live job openings from Lever career boards into one clean JSON dataset, read through the official Lever Postings API (api.lever.co/v0/postings). No HTML scraping, no login, no proxies, no API key.

Pass board slugs (lever:spotify) or just paste the careers URL (jobs.lever.co/<company>). You get one row per job: title, location, department, apply URL, dates, stable id.

Raw board data, nine normalized fields, no enrichment; cheaper than multi-ATS and enrichment feeds. This Actor accepts only Lever boards (lever:<slug> or a pasted Lever URL). Entries for other platforms are returned as one error row each and skipped. For a mixed list across six ATS platforms use ats-jobs-feed ($2 per 1,000).

Why this instead of scraping or the vendor API

• api.lever.co/v0/postings/<company>?mode=json is the same feed the hosted jobs.lever.co page loads. No browser, no rendering, nothing to fix when the page layout changes.
• No key and no account. The Postings API is public and unauthenticated. You do not need Lever's authenticated Data API.
• Pasted URLs work. jobs.lever.co/<company> is recognized and turned into lever:<company>.
• Same nine-column schema as the other CleanFeeds ATS feeds, so rows from this Actor and ats-jobs-feed fit one table.
• Postings without a title or URL are dropped before charging, so a malformed entry never costs you a row.

Input example

{"boards": ["lever:spotify", "https://jobs.lever.co/palantir", "lever:veeva"], "maxJobsPerBoard": 0}

Field	Type	Default	Notes
boards	string list	three sample Lever boards	lever:<slug> or a Lever careers URL
maxJobsPerBoard	integer	0	0 = everything the board returns

Filters are applied before billing

postedAfter (ISO date or 24h / 7d), titleIncludes (keep if the title contains any term) and titleExcludes (drop if it contains any term) are applied to the rows read from the ATS before the pay-per-event charge, so you never pay for jobs you filtered out. Matching is case-insensitive substring; there is no fuzzy or AI matching, so what you see is what was matched. Dates come from the ATS itself (first_published, createdAt, publishedAt, releasedDate, published_at), not from when we indexed the job; Workday only publishes "Posted N Days Ago", so its posted_at has day precision and "30+ days ago" postings have no date and are excluded when postedAfter is set.

{ "boards": ["greenhouse:stripe", "lever:spotify"], "postedAfter": "24h", "titleIncludes": ["engineer", "developer"], "titleExcludes": ["intern", "staffing"] }

Output example

{ "source": "lever", "company": "spotify", "title": "Software Engineer", "location": "Remote",
  "department": null, "url": "https://jobs.lever.co/spotify/3f1c7b2e-8a4d-4c6e-9b1a-2d5e7f8a9b0c", "posted_at": "2026-10-21T09:12:00.000Z", "updated_at": null, "id": "3f1c7b2e-8a4d-4c6e-9b1a-2d5e7f8a9b0c" }

Field	Meaning
source	always lever
company	the slug you passed
title, location, department	as the ATS reports them, null where the ATS does not expose a field. For Lever, department is the posting's team category, falling back to department
url	public job / apply page (Lever hostedUrl)
posted_at, updated_at	ISO 8601 when the ATS provides them. Lever gives createdAt as posted_at; updated_at is always null for Lever
id	ATS-side job id, stable across runs, diff it to detect new and closed roles

A board that fails (bad slug, HTTP error) yields one row with error and the other boards continue.

How much does it cost?

Pay per event: $1.50 per 1,000 job rows plus Apify's small Actor-start event. Compute is included. Set a maximum charge per run in the Console and the Actor stops at the limit. The Apify free plan is enough to try it on the sample boards.

Use cases

• Recruiting SaaS and talent CRMs: nightly sync of target accounts' Lever boards.
• Hiring-intent signals: diff today's ids against yesterday's dataset.
• AI agents and MCP: "list open roles at these companies" through the Apify MCP server.
• Market maps: location and department mix per company over time.

Integrations

• Apify API: POST https://api.apify.com/v2/acts/cleanfeedsapi~lever-jobs-feed/run-sync-get-dataset-items?token=<APIFY_TOKEN> with the input JSON as the body. The response is the dataset, ready to parse.
• Scheduling: open the Actor in the Apify Console, click Schedule, pick a cron (for example daily at 06:00) and the saved input runs on its own. Each run keeps its own dataset.
• n8n, Make, Zapier: use the Apify integration in each tool, choose this Actor and pass the same input JSON. No per-Actor setup, no custom code.
• Apify MCP server for AI agents: connect the Apify MCP server to Claude, Cursor or any MCP client and ask the agent to run cleanfeedsapi/lever-jobs-feed with these inputs.

Related Actors by CleanFeeds

• ats-jobs-feed: all six ATS platforms in one Actor, same schema.
• greenhouse-jobs-feed: Greenhouse boards via the official Job Board API.
• ashby-jobs-feed: Ashby job boards via the posting API.
• workday-jobs-feed: Workday career sites via the public CXS JSON.
• remote-jobs-feed: RemoteOK and Arbeitnow remote listings in one schema.

Free sample dataset: cleanfeeds/tech-jobs-daily on Hugging Face. More feeds at cleanfeeds.dev.

FAQ

Do I need a Lever API key? No. The endpoint is public and unauthenticated.

Is this HTML scraping? No. It reads the official Lever Postings API (api.lever.co/v0/postings), the same data the careers page itself loads.

Where do I find the slug? It is the token in the careers URL. Or paste the URL itself.

Can I mix ATS platforms in one run? No. This Actor accepts only Lever boards (lever:<slug> or a pasted Lever URL). Entries for other platforms are returned as one error row each and skipped. For a mixed list across six ATS platforms use ats-jobs-feed ($2 per 1,000).

How do I detect new and closed items between runs? id is the Lever posting id and does not change between runs. Keep each run's dataset and compare id sets per company: ids present today but not yesterday are new roles, ids present yesterday but not today are closed. Schedule the Actor daily and the diff is a few lines in n8n, Make or a script.

What happens when a source fails? A board that returns an HTTP error, an unknown slug or an unrecognized URL does not stop the run. The Actor logs the failure, pushes one row with source, company and error (the message), and continues with the next board. Error rows are not charged. Filter on error to find them.

Why is updated_at always null for Lever? The Postings API exposes createdAt only. The Actor never guesses a value it did not receive.