Company Jobs Scraper — Greenhouse Lever Ashby Workable Workday

Claude / Codex skill to describe and setup this actor: SKILL.md

One input — a list of companies. This ATS job scraper auto-detects each company's ATS across six providers (Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Workday), pulls every live posting through official public APIs and returns a single deduped dataset. No login, no proxies, no per-ATS setup.

How ATS detection works

You pass company slugs — the Actor probes each company on Greenhouse, Lever, Ashby, Workable and SmartRecruiters (one API request per ATS; the fetch itself is the probe). Whichever board answers is fetched in full; companies found nowhere are logged and skipped. Everything is merged and cross-source-deduped by URL into one dataset. Use atsProviders to skip ATS you know a company isn't on — fewer providers probed per company means fewer upstream requests and a faster run. Each ATS fails open independently: if one provider's API errors, the run keeps going on the others (and the error surfaces as a dataset row, not a run failure).

Workday needs a full URL

Greenhouse, Lever, Ashby, Workable and SmartRecruiters are addressed by a bare company slug. Workday is the exception: its API is keyed by datacenter + career-site (e.g. acme.wd1.myworkdayjobs.com / site External), which a bare slug can't express. To include a Workday board, pass its full careers URL in companies, e.g. https://acme.wd1.myworkdayjobs.com/en-US/External — the Actor decodes the tenant, datacenter and site from it. A bare slug is simply a Workday probe miss (the other five ATS still run for it).

Input

Field	Type	Default	Description
companies	array	—	Company slugs (full board URLs also accepted). Slugs are probed on every selected ATS; misses are just logged. For Workday, pass the full careers URL (see above). Optional if you use presetLists.
presetLists	array (multi-select)	—	Curated company groups (ai-labs, tech-unicorns, devtools-infra) — pick one to run without your own slug list. Merged + deduped with companies.
atsProviders	array (multi-select)	all 6 (greenhouse, lever, ashby, workable, smartrecruiters, workday)	Restrict which ATS get probed per company.
keyword	string	—	Case-insensitive substring match on the job title.
titleExclude	array	—	Drop postings whose title contains any of these substrings (case-insensitive).
locationFilter	string	—	Case-insensitive substring match on the location.
postedWithin	string	any	Keep only jobs published inside this window. Use any for no date filter, or a duration — 1h, 24h, 3d, 2w, 6m. Jobs the source gave no date for are dropped rather than guessed at. Replaces postedSince, still accepted for existing integrations.
remoteOnly	boolean	false	Keep only postings the source ATS flags as remote. Greenhouse-hosted companies never match this filter — see FAQ.
includeDescription	boolean	true	Include a plain-text description snippet per posting.
maxItemsPerCompany	integer	100	Cap postings returned per company (0 = no cap). Each result is a billed event. If the cap actually cuts postings for a company, one extra dataset row flags it (warnings: ["truncated ..."]) — see "Warning rows".
maxItems	integer	200	Hard cap on total postings returned (0 = no cap). Each result is a billed event. If the cap actually cuts postings, one extra dataset row flags it (warnings: ["truncated ..."]) — see "Warning rows".
concurrency	integer	8	Companies fetched in parallel (advanced).

What company career pages data does this scraper extract?

Published postings follow nomad-agent-job-row-v1. The shared fields carry source identity, title and company, parsed locations, dates, the complete plain-text body when available, source markup when usable, and work type. Unavailable scalar facts are null; no parsed location is []. Source-only facts appear in versioned custom.data only when mapped there. See the Output example section for the exact dataset fields and diagnostic rows.

How to scrape company career pages with this Actor

1. Enter one or more company slugs (stripe, duolingo, openai, netguru) — or select a presetLists group. Use the company's careers-page slug. When unsure, pass your best guess — slugs are probed on all selected ATS providers and misses are just logged. For Workday boards, pass the full careers URL instead of a slug.
2. Optionally restrict atsProviders, and set keyword / titleExclude / locationFilter / postedWithin / remoteOnly / caps.
3. Run and export JSON, CSV or Excel — or call it over the API:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("nomad-agent/company-careers-bundle").call(run_input={
    "companies": ["stripe", "duolingo", "openai", "netguru"],
    "keyword": "engineer",
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["company"], "|", item["title"], item["url"])

curl -X POST \
  "https://api.apify.com/v2/acts/nomad-agent~company-careers-bundle/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["stripe", "duolingo", "openai", "netguru"]}'

Output example

Every row follows nomad-agent-job-row-v1, the one shape shared by all of this fleet's job Actors. A row carries every field; null means the source did not publish that fact, and locations: [] means no usable location was parsed from the posting. Nothing is guessed.

{
  "schemaVersion": "nomad-agent-job-row-v1",
  "recordType": "posting",
  "source": "linkedin",
  "id": "a1b2c3",
  "url": "https://example.com/linkedin/jobs/a1b2c3",
  "title": "Senior Backend Engineer",
  "company": "Example Company",
  "locations": [
    "Bilbao",
    "Spain"
  ],
  "postedAt": "2026-09-02T00:00:00Z",
  "deadline": null,
  "description": null,
  "descriptionHtml": null,
  "workType": "remote",
  "custom": {
    "schemaId": "nomad-agent-job-custom-company-careers-bundle-v1",
    "data": {
      "globalId": "…",
      "department": "…",
      "hasEquity": "…"
    }
  }
}

Field	Meaning
schemaVersion	Always "nomad-agent-job-row-v1".
recordType	"posting" for a job, "diagnostic" for a row reporting something about the run itself.
source	Which job source the posting came from, from the collector registry's vocabulary — not the Actor name.
id	Stable identifier for the posting within source.
url	Canonical public URL of the posting on the source site.
title	Job title exactly as the source publishes it, untruncated.
company	Employer name as published.
locations	Places the role is based, most specific first — e.g. ["Bilbao", "Spain"].
postedAt	When the source published the posting, ISO-8601 UTC (YYYY-MM-DDTHH:MM:SSZ).
deadline	Closing date for applications as an ISO-8601 calendar date (YYYY-MM-DD).
description	The complete posting body as plain text — never truncated, never summarised.
descriptionHtml	The posting body as the source's own markup, preserving lists, headings and links.
workType	Working arrangement: "remote", "hybrid" or "onsite".
custom	Facts only this source publishes, as {"schemaId", "data"}.

A run also emits diagnostic rows — recordType: "diagnostic" with a warnings array — when it has something to report, such as a source returning nothing. They are never billed and are easy to filter out on recordType.

Preset company lists

No slug list yet? Select one or more presetLists groups and the Actor runs against a curated set of well-known boards (verified live) without any companies input:

Preset	Companies (sample)
ai-labs	OpenAI, Anthropic, Mistral, Cohere, Hugging Face, ElevenLabs, Together
tech-unicorns	Stripe, Databricks, Figma, Ramp, Notion, Coinbase, Reddit, Discord, …
devtools-infra	GitLab, Vercel, Confluent, CockroachLabs, Postman, Gusto, Samsara, …

Presets are merged with (and deduped against) any companies you pass. If neither companies nor presetLists is provided, the Actor falls back to a built-in default spread so a first run works out of the box.

Warning rows

Diagnostic rows use schemaVersion: "nomad-agent-job-row-v1", recordType: "diagnostic", a warnings array and optional docs. They carry no posting fields and are not billed as job results. A dataset consumer can filter them by recordType:

Trigger	Example warnings
A requested company slug 404'd (or hard-failed) on every ATS probed	["not found on any ATS probed (greenhouse/lever/ashby/workable/smartrecruiters/workday): 'acme-corp' (404 on every probe)"]
maxItemsPerCompany actually cut postings for one company	["truncated for 'acme-corp': maxItemsPerCompany=100 returned 100 of 137 matching postings — raise maxItemsPerCompany to get the rest"]
maxItems actually cut the total run	["truncated: maxItems=200 returned 200 of 340 matching postings — raise maxItems to get the rest"]
An unexpected run error (kept SUCCEEDED, not billed)	["run error (…): … — no further postings returned; see the run log. This row is not billed."]

None of these rows are billed as a result event — only genuine postings are. Pass 50 company slugs in one run and you can tell exactly which ones need fixing straight from the dataset, instead of hunting through the run log.

Integrations

Export results as JSON, CSV or Excel/XLSX, or pipe them straight into Make, Zapier or n8n. Call this Actor synchronously with run-sync-get-dataset-items, or plug it into any AI agent through the Apify MCP server.

Pricing

Pay per event: a small per-run start fee plus a flat price per posting returned — current rates are on this Actor's Pricing tab. No subscription, no minimum: pay only for what you fetch, and cap spend per run with maxItems / maxItemsPerCompany. Warning/diagnostic rows are never billed.

Use cases

• Watchlists: monitor hiring across target/competitor/portfolio companies
• Recruiting agencies: one feed over every client's ATS
• VC talent teams: portfolio-wide open-roles dashboards
• Job boards that aggregate by company rather than by board

FAQ

Is it legal to scrape company career pages? The data comes from the ATS providers' official, public, unauthenticated JSON APIs — the same data any visitor sees on the company's careers page. Review the providers' terms for your use case.

Do I need an API key or login? No. These are public job-board APIs — no authentication of any kind.

What if a company isn't found? The run continues with the other companies and emits an unbilled diagnostic row whose warnings names the missing slug and whether it was a clean 404 or a fetch failure. Full board URLs are also accepted and reduced to slugs automatically. See "Warning rows".

Why do some records have remote: null and employmentType: null? Those are ats: "greenhouse" records. Greenhouse's public API never exposes a remote/workplace-type or employment-type field, so this Actor reports null rather than guessing. Lever/Ashby/Workable records populate both fields whenever the source states them.

How fresh is the data? Every run hits the ATS APIs live. No caching layer in between.

Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and fixes ship fast.

Related Actors

• Greenhouse Jobs Scraper — Company Job Boards
• Lever Jobs Scraper — Company Job Postings API
• Ashby Jobs Scraper — Company Job Boards API
• Workable Jobs Scraper — Company Job Boards
• Web Developer Jobs Scraper — 10 Boards in One
• LinkedIn Jobs Scraper — No Login, No Cookies

---

From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.