Lever Jobs Scraper

Lever Jobs Scraper turns known public Lever boards into one structured record per current job opening. Recruiters, talent-intelligence teams, and job-market researchers can provide board tokens or board URLs and receive titles, locations, teams, employment types, public descriptions, compensation fields when available, timestamps, application URLs, and source provenance.

Best fit for this Actor

• Use it when a company already exposes its openings on a public Lever board and you need an auditable dataset of its current roles.
• Start with a Lever board token such as leverdemo-8, or a public board-root URL such as https://jobs.lever.co/leverdemo-8.
• Use title, location, team, and employment-type filters before the actor writes billable job records.

Use it for defined public Lever boards, with one dataset record for each public posting. Company discovery, non-Lever career pages, application submission, and candidate records belong in separate workflows.

Focused standalone workflow

This actor is designed as a focused standalone workflow for known public Lever boards. It works as a clear source-linked collection step before a team compares hiring activity, exports job data, or joins the records to an authorized employer-research workflow.

Recruiting workflow: compare current engineering hiring

A talent researcher has a shortlist of employers using Lever. They provide the relevant board tokens and filter for remote engineering roles. Each returned record has a title, location, team, commitment, postedAt, applyUrl, and sourceApiUrl, making it straightforward to compare active hiring and retain a link back to the employer's public post.

Quick start input

{
  "boardTokens": ["leverdemo-8", "https://jobs.lever.co/leverdemo-8"],
  "maxResultsPerBoard": 100,
  "titleIncludes": "engineer",
  "locationIncludes": "remote",
  "teamIncludes": "engineering",
  "commitmentIncludes": "full-time",
  "includeDescriptions": true
}

boardTokens accepts raw public board tokens, public board-root URLs, and equivalent public Lever API URLs. Each supplied board has its own clear result boundary.

Input reference

Field	Type	What it controls
boardTokens	array	One or more public Lever board tokens or board-root URLs.
maxResultsPerBoard	integer	Validated result boundary for each supplied board.
titleIncludes	string	Case-insensitive literal match against the public job title.
locationIncludes	string	Case-insensitive literal match against public location fields.
teamIncludes	string	Case-insensitive literal match against Lever's public team field.
commitmentIncludes	string	Case-insensitive literal match against Lever's public employment type.
includeDescriptions	boolean	Includes public description and supplementary HTML and clean text.

What data you receive

Each dataset item represents one public Lever job post. The public job and API source URLs, plus scrapedAt, preserve the source and observation time needed for current research.

Field	Meaning
jobId, boardToken, title	Stable public identity for the job and its source board.
location, allLocations, team, commitment	Public role categorization for filtering and analysis.
descriptionText, additionalText	Clean public job detail when descriptions are requested.
salaryMin, salaryMax, salaryCurrency, salaryInterval	Public compensation fields when the board exposes them.
applyUrl, jobUrl	Public employer application and hosted-posting paths.
postedAt, scrapedAt, sourceApiUrl	Freshness and provenance fields.

{
  "jobId": "abc-123",
  "boardToken": "example",
  "title": "Senior Software Engineer",
  "location": "Remote",
  "allLocations": ["Remote", "New York, NY"],
  "team": "Engineering",
  "commitment": "Full-time",
  "workplaceType": "remote",
  "descriptionText": "Build reliable APIs.",
  "salaryMin": 120000,
  "salaryMax": 180000,
  "salaryCurrency": "USD",
  "salaryInterval": "yearly",
  "applyUrl": "https://jobs.lever.co/example/abc-123/apply",
  "jobUrl": "https://jobs.lever.co/example/abc-123",
  "postedAt": "ISO 8601 timestamp when provided",
  "sourceApiUrl": "https://api.lever.co/v0/postings/example?mode=json",
  "scrapedAt": "ISO 8601 collection timestamp"
}

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~lever-jobs-scraper/runs?token=$APIFY_TOKEN" \
  -H "content-type: application/json" \
  -d '{"boardTokens":["leverdemo-8"],"maxResultsPerBoard":25}'

After collection completes, read the default dataset for job records. OUTPUT reports the compact terminal outcome, while RUN_SUMMARY records board coverage, diagnostics, and charged event counts.

Use with AI agents through Apify MCP

Collect up to 25 current public engineering roles from the Lever board leverdemo-8. Return each title, location, team, employment type, application URL, posted timestamp, and source URL. Read the dataset and terminal outcome, preserve the source URLs, and stay within the requested result boundary and cost scope.

The actor is read-only. An agent can recognize VALID_EMPTY as a successful no-match result, preserve sourceApiUrl and jobUrl, and use RUN_SUMMARY to report board diagnostics alongside the dataset.

Pricing

This actor uses Pay per event plus Apify platform usage. Each validated public job record written to the dataset is billed at $0.003; the actor-start event is $0.00005 per GB of configured memory. Filters run before dataset writes, and the actor logs the maximum possible job-event cost for the supplied board and result limits. Open the live Pricing tab for current details; platform compute and network usage are additional.

Best results

• Provide known, public Lever board tokens so the workflow starts with a defined employer set.
• Use a bounded result count and the literal filters to keep the collection focused on a recruiting question.
• Schedule repeat runs for monitoring, then compare postedAt with scrapedAt to distinguish source timing from collection timing.
• Preserve sourceApiUrl and jobUrl when sharing results so collaborators can review the source posting.

Builder's note

I designed the output around Lever's stable boardToken because public boards can vary in their company-display metadata. That choice keeps source identity explicit, preserves a clean record shape, and lets the outcome contract communicate whether a board returned matching roles.

Responsible use

Use public or authorized data in line with applicable laws, the target site's terms, and your organization's data-handling practices. The collection focuses on public job postings and keeps application interaction and candidate records outside its scope.