Lever Jobs Scraper | Public ATS Job Data

Collect public job postings from one or many Lever company boards with a board URL or site slug. The Actor delivers one structured Dataset item per unique job, including job and application URLs, locations, categories, workplace data, timestamps, and optional descriptions.

What this Actor does

The Actor reads public Lever job boards through their public postings interface. It paginates each board, normalizes the available fields, removes duplicate jobs within the run, and applies per-board and global output limits. Available jobs are retained when another requested board cannot be collected.

Use cases

• Build or refresh job boards from companies that publish vacancies through Lever.
• Monitor hiring activity, teams, locations, employment types, and workplace arrangements.
• Identify company hiring signals for B2B prospecting and market research.
• Feed public job URLs and application links into recruiting, research, or alerting workflows.
• Export normalized Lever vacancies to spreadsheets, databases, dashboards, or data pipelines.

How to use

1. Open the Actor in Apify Console.
2. Add at least one public jobs.lever.co board URL or a Lever site slug such as palantir.
3. Choose the output limits and whether to include descriptions.
4. Click Start and open the Dataset when the run finishes.

Input

boardUrls accepts 1–50 entries. Duplicate slugs are removed case-insensitively. Supported absolute URLs use jobs.lever.co or api.lever.co; URLs from unrelated domains are rejected.

pageSize defaults to 100. maxJobsPerBoard defaults to 500 results and maxTotalJobs defaults to 5,000; both accept values up to 50,000. includeDescription defaults to true. Request timeouts are managed automatically by the Actor. When continueOnError is enabled, remaining boards are processed after a board error, and available jobs are retained. A partial or stopped collection is reported with SUMMARY.complete=false. With this option disabled, later boards are not processed after a board becomes unavailable.

This exact input produced the complete output below:

{
  "boardUrls": ["https://jobs.lever.co/palantir"],
  "includeDescription": false,
  "pageSize": 1,
  "maxJobsPerBoard": 1,
  "maxTotalJobs": 1,
  "continueOnError": true
}

Output

Each Dataset item represents one unique public Lever posting. Important fields include sourceJobId, title, jobUrl, applyUrl, location, locations, department, employmentType, team, workplaceType, postedAt, and scrapedAt.

When includeDescription is disabled, descriptionHtml, descriptionText, openingHtml, and additionalHtml are null. Lever's structured lists sections remain available because they are separate source sections. isRemote is currently a reserved normalized field and can be null; use workplaceType for the published Lever workplace label.

The run saves SUMMARY with collection completeness, result counts, accepted charge events, spending-limit state and affected boards. ERRORS lists unavailable boards and is empty when none were reported. A reporting outage can leave a summary unavailable; in that case, completeness is unknown. Successful items remain in the Dataset if another board fails. Results can be exported through Apify as JSON, JSONL, CSV, Excel, XML, or RSS.

The live run log shows board/page progress and saved-job counts. A complete collection ends with a clear completion message. Partial and stopped collections are labeled separately and preserve the available jobs. Review SUMMARY.complete and ERRORS before treating the requested coverage as complete.

This is the complete Dataset item from a real successful run:

{
  "source": "lever",
  "boardSlug": "palantir",
  "boardUrl": "https://jobs.lever.co/palantir",
  "sourceJobId": "6ed76ce8-4156-4b60-b120-403538bd66cd",
  "internalJobId": null,
  "requisitionId": null,
  "title": "Administrative Business Partner",
  "companyName": null,
  "jobUrl": "https://jobs.lever.co/palantir/6ed76ce8-4156-4b60-b120-403538bd66cd",
  "applyUrl": "https://jobs.lever.co/palantir/6ed76ce8-4156-4b60-b120-403538bd66cd/apply",
  "location": "Singapore, Singapore",
  "locations": [
    "Singapore, Singapore"
  ],
  "department": null,
  "departments": [],
  "offices": [],
  "metadata": [],
  "country": "SG",
  "employmentType": "Full-time",
  "team": "Administrative",
  "workplaceType": "hybrid",
  "isRemote": null,
  "postedAt": "2026-08-11T17:38:11.368000Z",
  "updatedAt": null,
  "applicationDeadline": null,
  "language": null,
  "descriptionHtml": null,
  "descriptionText": null,
  "compensation": null,
  "categories": {
    "commitment": "Full-time",
    "location": "Singapore, Singapore",
    "team": "Administrative",
    "allLocations": [
      "Singapore, Singapore"
    ]
  },
  "lists": [
    {
      "text": "Administrative Business Partner (Foundry)",
      "content": "\n<li>Provide administrative support to a portfolio of individuals/teams across the business.</li>\n<li>Handle sophisticated calendars in a fast-paced environment, and prioritize commitments to enhance time and productivity.</li>\n<li>Book travel arrangements (domestic and international).</li>\n<li>Track and process expense reports.</li>\n<li>Help plan, support, and complete office events and external gatherings.</li>\n<li>Work both autonomously and in collaboration with teammates, colleagues, and external contacts.</li>\n"
    },
    {
      "text": "What We Value",
      "content": "\n<li>Ability to adjust quickly, anticipate needs, and implement autonomously, with strong attention to detail.</li>\n<li>Ability to interact with a wide range of teams internally and externally with thoughtfulness and tact.</li>\n<li>High level of integrity, confidentiality, and discretion in both internal and external interactions.</li>\n"
    },
    {
      "text": "What We Require",
      "content": "\n<li>At least three years of previous administrative or personal support experience, preferably in a fast-paced environment.</li>\n<li>Excellent digital literacy, including proficiency with Microsoft products (Outlook, Excel, Word, PowerPoint, etc.).</li>\n<li>Experience with scheduling sophisticated international and domestic travel itineraries.</li>\n<li>Familiarity with travel booking and expense reporting software.</li>\n"
    }
  ],
  "openingHtml": null,
  "additionalHtml": null,
  "sourceData": null,
  "scrapedAt": "2026-10-23T09:27:32.472915Z"
}

Pricing

Each unique job written to the default Dataset triggers one job-result event. Your Apify subscription tier determines its price:

Apify user tier	Price per delivered job	Equivalent per 1,000 delivered jobs
Free	$0.001	$1.00
Bronze	$0.0009	$0.90
Silver	$0.0008	$0.80
Gold	$0.00075	$0.75
Platinum	$0.00075	$0.75
Diamond	$0.00075	$0.75

The 1,000-job values are comparison equivalents; Apify charges one job-result event per delivered job. There is no start charge. Empty boards, unavailable boards, duplicate jobs, skipped jobs, SUMMARY, and ERRORS do not generate job-result charges. If one board fails after other boards delivered jobs, those confirmed results remain billable even when the collection is partial.

The Actor checks the maximum charge selected for a run before delivering another billable job. When the remaining budget cannot pay for another job, the Actor stops producing results and records chargeLimitReached=true; already delivered results remain available. Post-run Dataset storage or retrieval can still use standard Apify platform resources according to the user's plan.

Related Actors

Actor	Best for
Ashby Jobs Scraper | Salaries & Job Details	Collecting vacancies from supplied company boards on Ashby, with available published compensation.
Greenhouse Jobs Scraper | Listings & Descriptions	Collecting vacancies from supplied company boards on Greenhouse.

Limits and data quality

• A run accepts up to 50 board entries and writes at most 50,000 jobs.
• Requested limits are ceilings, not guarantees. A board may expose fewer current jobs.
• Jobs are deduplicated within a run using the board and public job ID.
• One accepted job-result event corresponds to one unique Dataset item. Duplicate or failed jobs never trigger this event.
• limitReached means a configured per-board or global output ceiling was reached; it does not prove that additional source jobs existed.
• chargeLimitReached means the user's maximum run charge could not fund another result. The Dataset contains only the jobs accepted within that budget.
• Published fields vary by company and job. Optional values can be null or empty.
• Temporary source unavailability can leave a partial collection. Available jobs remain in the Dataset, and affected boards are listed in the run summary.
• Public jobs can change or disappear after collection.

Frequently asked questions

Can I process several Lever boards in one run?

Yes. Add up to 50 URLs or slugs to boardUrls. Duplicate slugs are processed once.

Why can a finished run contain only some requested jobs?

With continueOnError enabled, available boards are still processed when another board is unavailable. Review SUMMARY.complete, failedBoards, unprocessedBoards and ERRORS before treating the collection as complete. A data-integrity problem or unconfirmed delivery or billing can still stop execution with an error to protect saved results.

Does disabling descriptions remove every HTML field?

It nulls the dedicated description, opening, and additional HTML fields. Structured Lever sections under lists remain in the Dataset.

Does this Actor submit job applications?

No. It reads public postings and application URLs but does not submit applications or access applicant accounts.

What am I charged for if a board fails?

Only unique jobs successfully delivered to the Dataset are charged at the applicable tier price. Unavailable boards, reporting records and empty responses do not create job-result charges.

Responsible use

Use the Actor only for lawful processing of publicly available job information. Follow applicable laws, privacy requirements, Lever's terms, and the rights of employers and applicants. This independent Actor is not affiliated with or endorsed by Lever.

Support

Open an issue in the Actor's Issues tab and include the run ID, non-sensitive input, affected board URL, and expected behavior. Never publish API tokens, credentials, or other secrets.