Lever Job Board Scraper — Company Hiring Signals 🚀

foXLabs hiring series: Greenhouse · Ashby · Workday · SmartRecruiters · Personio · Teamtailor

🎉 Turn any company's Lever board into clean, structured hiring data — no login, no API key, one row per open role. Built for recruiters, sales & competitive-intelligence teams, and anyone scoring hiring intent at scale.

🔍 What is the Lever Job Board Scraper — and when should you use it?

Lever runs the careers site for a big slice of scale-up tech. Give this actor a company slug (spotify) or a Lever job-site URL and it returns every open role — title, team, department, location(s), employment type, salary where published, the full description and the apply link.

Use it when you need: every open role at a target company, hiring-intent signals (which functions a company is growing), a recruiter sourcing list across many companies, or a clean read of a competitor's headcount plans — from Lever's public postings API, no key.

Use something else when: the company doesn't run on Lever. Point the matching actor at its ATS instead — every actor in the foXLabs hiring series emits the same schema, so their outputs concatenate into one hiring-intent table: Greenhouse · Ashby · Workday · SmartRecruiters · Personio · Teamtailor.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/lever-job-board-scraper.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is per delivered role, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull a company's open roles using the Apify Actor `foxlabs/lever-job-board-scraper`.
Input: `queries` is a list of a Lever company slug (`spotify`) or a job-site URL. `maxResultsPerQuery` caps rows per company (default 200).
Start with: {"queries":["spotify"],"maxResultsPerQuery":50}
Ask me which companies to track, run the Actor, then summarise the roles as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/lever-job-board-scraper.md.

📋 Overview

Everything you need to turn a Lever careers board into clean, structured data — role details, metadata and hiring signals — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole board in one call — every open role, no per-tool stitching.
• ⚡ Slug- or URL-native — paste what you already have; the actor resolves the rest.
• 📄 Complete descriptions — full role text, HTML stripped to clean plain text.
• 🔗 Same schema across the series — join with the six sibling ATS actors on companyBoard.
• 💰 Pay only for results — per-row pricing, empty/failed lookups never billed.
• 🤖 Agent-ready — MCP + x402 agentic payments.
• ⚡ Rich fields — team, workplace type and salary range (where the company publishes one), not just a title.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~lever-job-board-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["spotify"],"maxResultsPerQuery":50}'

🚀 Getting Started (3 steps)

1. Choose your companies — a Lever company slug (spotify) or a job-site URL.
2. Set the cap — maxResultsPerQuery limits rows per company (default 200).
3. Run and export — a clean dataset as JSON, CSV or Excel.

📥 Input

{
  "queries": [
    "spotify",
    "palantir",
    "https://jobs.lever.co/swordhealth"
  ],
  "maxResultsPerQuery": 200,
  "maxConcurrency": 5,
  "includeRaw": false
}

Field	Type	Description
queries	array	a Lever company slug (spotify) or a job-site URL.
maxResultsPerQuery	integer	Caps rows per company (default 200).
maxConcurrency	integer	How many companies to fetch at once.
includeRaw	boolean	Attach the source's untouched record under raw.
requestDelayMs	integer	Politeness delay between requests.
proxyConfiguration	object	Optional.

📤 Output

One row per open role, saved to the dataset.

Field	Type	Description
companyName	Company name
companyBoard	Company slug — join key across runs
jobId	Lever posting ID
jobTitle	Role title
department	Department (Lever category)
team	Team
location	Primary location
allLocations	All posting locations
isRemote	Remote flag
workplaceType	On-site / remote / hybrid
employmentType	Commitment (full-time, contract…)
salary	Salary range where published
postedAt	Posted date (ISO)
description	Full description, HTML stripped
applyUrl	Apply link
sourceUrl	Public posting URL

Every row also carries query, scrapedAt, and — when a lookup fails — an error.

💼 Use cases

1. Hiring-intent scoring Input: target company slugs, weekly. Output: roles by team + salary + date. Use: rank accounts by what they are recruiting for.

2. Compensation benchmarking Input: a set of peer slugs. Output: roles with published salary ranges. Use: benchmark pay bands by function and market.

3. Recruiter sourcing Input: many slugs in one run. Output: one table of roles + apply links. Use: build a sourcing pipeline in minutes.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/lever-job-board-scraper').call({ queries: ['spotify'], maxResultsPerQuery: 50 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/lever-job-board-scraper').call(run_input={'queries': ['spotify'], 'maxResultsPerQuery': 50})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: $0.002 per delivered role. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads Lever's public postings API — no key.

What do I search by? A Lever company slug (spotify) or a job-site URL.

How current is the data? Every run queries the source live, so results are as fresh as the board itself.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

What happens on a bad input or empty board? You get a row with your query and an error — nothing is silently dropped, and you're not charged.

Is scraping this legal? It reads a public job feed the company publishes for syndication — job data, not personal data. See below.

🐛 Troubleshooting

• "Lever has no public postings site named …" — take the slug from the careers URL, or pass the full job-site URL.
• Fewer rows than expected — the site may have that many roles, or raise maxResultsPerQuery.
• An error row — the slug is wrong or the site is private; confirm the careers page loads publicly.

⚠️ Trademark

Independent, third-party tool. Not affiliated with, endorsed by or connected to Lever, Inc.. "Lever" and related marks belong to their owners and are used here for identification only.

⚖️ Is it legal to scrape this data?

This actor reads only publicly published job-posting data — no private or personal user data. Your results can still contain personal data (e.g. a name in a description); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify's blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor's Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.3

• Standby mode: also runs as a real-time API — GET /search?query=<query> returns open roles as JSON, billed per role. See the Standby tab.

0.2

• Posting dates fixed. postedAt was always empty (Lever's createdAt is an epoch-millisecond value the date parser didn't handle); it now resolves to a real date.
• Every column carries real data. Fields Lever never provides (city, countryName, seniority, updatedAt) are no longer emitted; department and salary remain and fill where the company publishes them.

0.1

• Initial release.