Multi-ATS Jobs Scraper: Greenhouse, Lever, Ashby & More

Agent skill: SKILL.md

https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/ats-multi-board-jobs-scraper.md

What it does

Give it any careers URL and it detects the ATS, Greenhouse, Lever, Ashby, Workable, Recruitee, Teamtailor or Personio, and returns one normalised job schema across all of them. Give it careerUrls and it returns one structured record per job.

Feed it a mixed company list and stop caring which vendor each company happens to use:

https://job-boards.greenhouse.io/stripe → greenhouse
https://jobs.lever.co/palantir → lever
https://jobs.ashbyhq.com/ramp → ashby
https://apply.workable.com/savvytalent → workable
https://channable.recruitee.com → recruitee
https://polestar.teamtailor.com → teamtailor
https://urbansportsclub.jobs.personio.de → personio
https://ramp.com/careers → ashby (detected from the page)
stripe → greenhouse (detected by probe)

Every one of those returns records with the same twelve fields.

How detection works

Three stages, cheapest first, the first one that answers wins:

1. URL pattern. jobs.lever.co/x, job-boards.greenhouse.io/x, x.recruitee.com, x.jobs.personio.de and friends are recognised outright. Free, no request.
2. Page signature. For a company's own careers domain (https://ramp.com/careers), the page is fetched once and scanned for an embedded ATS URL. One request.
3. Blind probe. For a bare slug (stripe) or a page that gave nothing away, each enabled platform is tried in order and the first one that returns jobs is used.

RUN_SUMMARY.detected records which stage resolved each source, so you can tell a confident match from a lucky guess.

Input

Field	Type	Default	Notes
careerUrls	array	-	Required. Any careers page URL or bare board slug. Mixed platforms in one list is the point.
platforms	array	[] (all)	Restrict to greenhouse, lever, ashby, workable, recruitee, teamtailor, personio.
searchTerms	array	[]	Keep only titles containing one of these terms (case-insensitive). Empty = all.
maxJobsPerCompany	integer	0	Cap saved jobs per source after filtering. 0 = no limit.
normalizeSchema	boolean	true	true = the unified 12-field schema. false = the provider's untouched payload under raw.

{
 "careerUrls": [
 "https://job-boards.greenhouse.io/stripe",
 "https://jobs.lever.co/palantir",
 "https://ramp.com/careers"
 ],
 "searchTerms": ["engineer"],
 "maxJobsPerCompany": 50,
 "normalizeSchema": true
}

Combinations that make sense. platforms narrows detection and shortens the blind probe, if you already know your list is all Greenhouse and Lever, setting it makes bare-slug inputs resolve in at most two requests instead of seven. A URL that clearly belongs to an excluded platform is reported as such rather than silently probed. maxJobsPerCompany applies after searchTerms, and paging stops as soon as the cap is met, so {"searchTerms": ["engineer"], "maxJobsPerCompany": 25} costs one page on most boards.

Output

One dataset item per job. Sample record (real values from stripe):

{
 "sourcePlatform": "greenhouse",
 "company": "Stripe",
 "jobId": "8023928",
 "title": "Account Executive, Bridge",
 "department": "8589 Bridge - S&M",
 "team": null,
 "location": "London",
 "isRemote": false,
 "employmentType": null,
 "postedAt": "2026-07-30T06:59:38-04:00",
 "applyUrl": "https://stripe.com/jobs/search?gh_jid=8023928",
 "descriptionPlain": "Who we are\n\nAbout Stripe\n\nStripe is a financial infrastructure platform…",
 "scrapedAt": "2026-08-06T12:00:00.000Z"
}

Field	Meaning
sourcePlatform	Which ATS the record came from, greenhouse, lever, ashby, workable, recruitee, teamtailor or personio
company	Company name as the platform reports it, falling back to the board slug
jobId	The platform's own posting ID, as a string. Unique within a platform, key on sourcePlatform + jobId
title	Job title, trimmed
department	Department, where the platform publishes one
team	Sub-team / category, where the platform publishes one
location	Primary location, assembled from whatever location fields the platform fills in
isRemote	The platform's own remote flag where it has one (Ashby, Lever, Workable, Recruitee), otherwise inferred from the title and location
employmentType	Full-time / contract / intern, in the platform's own vocabulary, FullTime on Ashby, Full-time on Lever, fulltime_permanent on Recruitee
postedAt	ISO timestamp the posting went live (Workable publishes a date only)
applyUrl	Direct application link
descriptionPlain	Full description as clean plain text, HTML stripped, entities decoded, Lever's four description blocks re-joined
scrapedAt	Run timestamp

With normalizeSchema: false each record is { sourcePlatform, company, jobId, raw, scrapedAt }, where raw is the provider's response object exactly as it arrived.

A RUN_SUMMARY record in the key-value store carries per-run counts, per-source failures and the applied filters:

{
 "sourcesRequested": 10,
 "sourcesFailed": 1,
 "failures": [
 {
 "source": "https://example.com/careers",
 "platform": null,
 "error": "no ATS matched \"example\", greenhouse: not found (404); lever: not found (404); …"
 }
 ],
 "jobsSaved": 36,
 "byPlatform": {
 "greenhouse": 8, "lever": 4, "ashby": 8, "workable": 4,
 "recruitee": 4, "teamtailor": 4, "personio": 4
 },
 "detected": {
 "https://ramp.com/careers": { "platform": "ashby", "company": "ramp", "via": "page-signature" },
 "figma": { "platform": "greenhouse", "company": "Figma", "via": "probe" }
 },
 "filters": { "platforms": [], "searchTerms": [], "maxJobsPerCompany": 4, "normalizeSchema": true },
 "finishedAt": "2026-08-06T11:36:33.848Z"
}

Use cases

1. Run one Actor across a mixed company list. No per-ATS integration, no branching in your pipeline.

{
 "careerUrls": [
 "https://job-boards.greenhouse.io/stripe",
 "https://jobs.lever.co/palantir",
 "https://jobs.ashbyhq.com/ramp",
 "https://channable.recruitee.com",
 "https://polestar.teamtailor.com"
 ]
}

2. Build a job board without per-ATS integrations. Schedule it, ingest the dataset, key on sourcePlatform + jobId, diff on postedAt.

{
 "careerUrls": ["https://ramp.com/careers", "https://vanta.com/careers", "figma", "stripe"],
 "normalizeSchema": true
}

3. Normalise hiring data for analytics. One job family across every platform, capped so the run stays predictable.

{
 "careerUrls": ["https://job-boards.greenhouse.io/stripe", "https://jobs.lever.co/palantir"],
 "platforms": ["greenhouse", "lever"],
 "searchTerms": ["engineer", "data", "machine learning"],
 "maxJobsPerCompany": 100
}

Limits and behaviour

• Detection order matters. URL pattern, then page signature, then blind probe. Give it a real board URL when you have one; it is both faster and unambiguous.
• A failing source never aborts the run. Every failure is recorded in RUN_SUMMARY.failures with the platform and the reason. The Actor only errors out if every source fails.
• Transient errors are retried. 429 and 5xx get three attempts with linear backoff. 404 and malformed payloads fail fast.
• Personio is the one soft spot. A share of Personio career sites sit behind a Vercel bot checkpoint that answers 429 to non-browser clients. Those tenants are recorded as failures and skipped; the rest (for example urbansportsclub, holidu) serve their XML feed straight out. Nothing here tries to defeat that checkpoint.
• Field coverage varies by platform, by design. Greenhouse's public feed carries no employment type; Teamtailor's public feed carries no department. Missing values are null, never guessed, except isRemote, which falls back to a keyword read of the title and location when the platform has no flag of its own.
• company on Lever is the board slug. Lever's public postings API does not publish a display name.
• Paging is honoured where the API pages (Lever 100/page, Teamtailor 100/page) and stops early once maxJobsPerCompany is met.
• Public data only. No authentication, no personal data, no access-control bypass.

FAQ

Do I need a proxy? No. Proxy configuration is not required to run this Actor.

Do I need an account on the source? No. You supply no credentials.

What happens if a source is unavailable? It is reported in RUN_SUMMARY.failures and the run continues with the remaining sources.

Can I schedule it? Yes, it is designed for scheduled runs. Diff on sourcePlatform + jobId to spot new roles.

Which platform will it pick for a bare slug? The probe order is Greenhouse, Lever, Ashby, Workable, Recruitee, Teamtailor, Personio, the first that returns jobs wins. Set platforms to make that deterministic.

Can a company's careers page point at more than one ATS? In practice no, but the page-signature stage takes the first match in probe order. Pass the board URL directly if you need to be certain.

Can I get the platform's native fields? Yes, set normalizeSchema: false and every record carries the provider's untouched object under raw.

Can I integrate it with something else? Yes, Apify API, client libraries, webhooks, scheduled runs, dataset exports (JSON/CSV/Excel) or MCP. Output is structured JSON.

API example

curl -X POST "https://api.apify.com/v2/acts/arman-bd~ats-multi-board-jobs-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{
 "careerUrls": ["https://job-boards.greenhouse.io/stripe", "https://jobs.ashbyhq.com/ramp"],
 "searchTerms": ["engineer"],
 "maxJobsPerCompany": 25
 }'