Ashby Jobs Scraper — Company Job Boards API

Scrape any company's Ashby job board through the official posting API — used by OpenAI, Ramp, Linear and thousands of fast-growing startups.

Don't know the slug — or even that a company runs on Ashby? Just hand it the company website. Point-and-scrape auto-discovery (companyDomains) resolves the jobs.ashbyhq.com board for you, then scrapes it.

Why this one:

• Cross-ATS join key — every posting carries a stable globalId (ashby:<slug>:<id>) that lines up with our Greenhouse, Lever and Workable Actors — merge multi-ATS pipelines without fuzzy matching.
• No silent failures — a slug that 404s, a website with no Ashby board, or a cap that cut results shows up as a warning row in the dataset itself (e.g. {"company": "acme.com", "warnings": ["no live Ashby board found for 'acme.com' ..."]}), so a 50-company batch tells you exactly what needs fixing without opening the run log. See "Warning rows".
• Delta mode — onlyNewSinceLastRun drops already-seen postings before billing; on a schedule you only pay for genuinely new jobs.
• BYOK AI enrichment — opt-in skills/seniority/remote/visa extraction with your own Anthropic or Mistral key; never bundled into the per-posting price.

Input

Provide companies (Ashby slugs), companyDomains (plain websites, auto-resolved), or both.

Field	Type	Default	Description
companies	array	—	Company slugs as used on jobs.ashbyhq.com/<slug> (full board URLs also accepted).
companyDomains	array	—	Auto-discovery. Plain company websites/domains (e.g. ramp.com, https://linear.app) — the Actor finds and scrapes their Ashby board with no slug needed. A site with no Ashby board becomes a warning row, not an error (see "Warning rows").
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.
descriptionSearch	string	—	Keep only postings whose description text contains this substring (case-insensitive). Description is fetched for filtering even when includeDescription is off.
descriptionExclude	array	—	Drop postings whose description text contains any of these substrings (case-insensitive).
companySearch	string	—	Keep only postings whose resolved company display name contains this substring (case-insensitive).
postedSince	integer	—	Keep only postings first published within this many days. Postings with no posting date are dropped when this is set.
postedAfter	string	—	Absolute lower date bound YYYY-MM-DD — keep postings published on or after this date. Undated postings dropped.
postedBefore	string	—	Absolute upper date bound YYYY-MM-DD — keep postings published on or before this date. Undated postings dropped.
remoteOnly	boolean	false	Keep only postings Ashby flags isRemote: true.
minSalary	integer	—	Keep only postings whose stated range reaches at least this amount (top of range). Undisclosed-pay postings dropped when set. No currency conversion.
maxSalary	integer	—	Keep only postings whose stated range starts at or below this amount (bottom of range). Undisclosed-pay postings dropped when set. No currency conversion.
includeDescription	boolean	true	Include a plain-text description snippet per posting.
outputProfile	string	full	full = all fields; compact = drop snippet; mini = drop snippet + structured salary breakdown (keeps salary text). See "Output profiles".
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".
onlyNewSinceLastRun	boolean	false	Delta/monitoring mode: only output postings not seen on a previous run made with this flag on (see "Delta mode / monitoring").
aiEnrichment	boolean	false	Adds aiKeySkills/aiExperienceLevel/aiWorkArrangement/aiVisaSponsorship per posting via the Anthropic or Mistral API — BYOK (see "AI enrichment").
aiProvider	string	anthropic	Which AI provider runs enrichment: anthropic (default, uses anthropicApiKey) or mistral (uses mistralApiKey).
anthropicApiKey	string (secret)	—	Your Anthropic API key. Only used when aiEnrichment is on and aiProvider is anthropic; billed separately by Anthropic, not by this Actor.
aiModel	string	claude-haiku-4-5-20251001	Claude model for AI enrichment (when aiProvider is anthropic): claude-haiku-4-5-20251001 (fast/cheap) or claude-sonnet-4-5 (higher quality).
mistralApiKey	string (secret)	—	Your Mistral API key. Only used when aiEnrichment is on and aiProvider is mistral; billed separately by Mistral, not by this Actor.
mistralModel	string	mistral-small-latest	Mistral model for AI enrichment (when aiProvider is mistral): mistral-small-latest (default, fast/cheap — matches larger Mistral models on this task), mistral-medium-latest, or mistral-large-latest.
concurrency	integer	8	Companies fetched in parallel (advanced).

What Ashby jobs data does this scraper extract?

One flat JSON record per live posting:

Field	Meaning
ats	Which ATS served the posting (always "ashby" here)
company	Real company display name, resolved from Ashby's own job-board page (falls back to the input slug if unresolvable)
id	Ashby's internal posting ID
title	Job title as posted
department	Department or team where provided
location	Location text (may include remote hints)
url	Direct link to the posting
postedAt	First-published date (YYYY-MM-DD) where provided
employmentType	Employment type (FullTime, PartTime, Contract, etc.) where provided, otherwise null
remote	true/false/null — the value of Ashby's own isRemote flag; null only when Ashby didn't state it at all
snippet	Plain-text description excerpt (optional)
salary	Compensation display text (e.g. "$185K - $325K"), or null when the company hasn't opted in to compensation disclosure
salaryMin / salaryMax	Structured salary range bounds, or null
salaryCurrency	3-letter currency code (e.g. "USD"), or null
salaryPeriod	Pay period the range covers ("year", "hour", etc.), or null
globalId	Stable composite id <ats>:<company-slug>:<id> — unique across the whole ATS-actor family, handy for merging with the Greenhouse/Lever/Workable Actors or the Company Careers Bundle
warnings	Array of data-quality notes for this record (e.g. ["postedAt missing"]); empty array when there's nothing to flag
isNew	Only present when onlyNewSinceLastRun is on — always true (already-seen postings are dropped, never emitted with isNew: false)
aiKeySkills	Only present when aiEnrichment is on — array of skills/technologies explicitly named in the posting text, never invented
aiExperienceLevel	Only present when aiEnrichment is on — one of entry/mid/senior/lead/unknown
aiWorkArrangement	Only present when aiEnrichment is on — one of onsite/hybrid/remote/unknown
aiVisaSponsorship	Only present when aiEnrichment is on — true/false only if the posting explicitly states a policy, otherwise null

Auto-discovery — scrape by company website (no slug needed)

Don't know a company's Ashby slug, or whether it even uses Ashby? Put its website in companyDomains and the Actor works the slug out for you:

{ "companyDomains": ["ramp.com", "https://linear.app", "notion.so"] }

How it resolves each site (pure deterministic HTTP probing — no AI, no guessing):

1. Tries the domain's own name as a slug first (ramp.com → ramp) — one API call handles the common case.
2. Otherwise fetches the homepage + common careers paths (/careers, /jobs, /company/careers) and pulls any embedded jobs.ashbyhq.com/<slug> link out of the page.
3. Every candidate slug is confirmed against the live Ashby posting API before it's accepted — a wrong guess simply resolves to nothing and is discarded, never scraped as bogus data.

Fail-open: a website with no reachable Ashby board produces one warning row ({"company": "<domain>", "warnings": ["no live Ashby board found for '<domain>' ..."]}) and the run continues with everything else. Mix companies (known slugs) and companyDomains (websites) freely in the same run — results are de-duplicated across both.

Output profiles

outputProfile trims the payload for high-volume runs:

Profile	Drops	Keeps
full (default)	—	Every field (honors includeDescription for snippet).
compact	snippet	Everything else, including structured salary.
mini	snippet, salaryMin, salaryMax, salaryCurrency, salaryPeriod	Core identity/link fields + salary display text.

How to scrape Ashby jobs with this Actor

1. Enter one or more company slugs in companies (openai, ramp, linear) — or skip the slug entirely and drop the company website into companyDomains (see "Auto-discovery").
2. Optionally set keyword / titleExclude / locationFilter / descriptionSearch / postedSince / postedAfter / postedBefore / minSalary / maxSalary / remoteOnly / outputProfile / 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/ashby-jobs-scraper").call(run_input={
    "companies": ["openai", "ramp", "linear"],
    "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~ashby-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["openai", "ramp", "linear"]}'

Output example

{
  "ats": "ashby",
  "company": "OpenAI",
  "id": "00207abc-49b7-465c-a219-f7c1140f8047",
  "title": "Forward Deployed Software Engineer - SF",
  "department": "Model Deployment for Business",
  "location": "San Francisco",
  "url": "https://jobs.ashbyhq.com/openai/00207abc-49b7-465c-a219-f7c1140f8047",
  "postedAt": "2025-11-15",
  "employmentType": "FullTime",
  "remote": true,
  "snippet": "About the team OpenAI's Forward Deployed Engineering team partners with customers...",
  "salary": "$185K - $325K",
  "salaryMin": 185000,
  "salaryMax": 325000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "globalId": "ashby:openai:00207abc-49b7-465c-a219-f7c1140f8047",
  "warnings": []
}

Only a minority of companies opt in to Ashby's compensation-disclosure feature — postings from companies that haven't have "salary": null, "salaryMin": null, "salaryMax": null, "salaryCurrency": null, "salaryPeriod": null.

Delta mode / monitoring

Set onlyNewSinceLastRun: true to turn this Actor into a "what's new" monitor. Postings already seen on a previous run made with this flag on are dropped before push — you are not billed for them, so pairing this with an Apify schedule (cron) means every run only returns, and only charges for, postings that showed up since the last flagged run.

How it works: seen postings are tracked in a dedicated key-value store, keyed by each posting's globalId, capped at roughly 50,000 entries (oldest evicted first). The first run made with the flag on has nothing to compare against yet, so it emits everything — all isNew: true. Every emitted record gets isNew: true stamped on it; there's no isNew: false in the output, since unseen postings just aren't included.

Runs made with the flag off never read or write this cache — turning it on and off between runs is safe and has no side effects on normal runs.

AI enrichment

Turn on aiEnrichment and supply your own anthropicApiKey (or mistralApiKey, with aiProvider: "mistral") to add four AI-extracted fields to every posting:

Field	Meaning
aiKeySkills	Specific skills/technologies/tools explicitly named in the title or description — the model is instructed to never invent one.
aiExperienceLevel	One of entry / mid / senior / lead / unknown.
aiWorkArrangement	One of onsite / hybrid / remote / unknown.
aiVisaSponsorship	true / false only when the posting explicitly states a sponsorship policy, otherwise null.

The extraction prompt is explicit about never guessing: when the text doesn't clearly support a value you get "unknown" / null / an empty array, not a fabricated answer. Pick the model with aiModel (Anthropic: claude-haiku-4-5-20251001 default, fast/cheap, or claude-sonnet-4-5 higher quality) or mistralModel (Mistral: mistral-small-latest default — matches larger Mistral models on this task, mistral-medium-latest, mistral-large-latest).

Postings are batched (~12 per call) through whichever provider's API you picked (aiProvider). Your Anthropic or Mistral API key is billed separately by that provider, not by this Actor. Rough cost with Haiku or Mistral Small: enriching 100 postings runs well under $0.05 in provider token spend (short prompts, small JSON replies); Sonnet/Mistral Large cost roughly 4-5x that for the same batch.

Enrichment needs a posting's description text even when you have includeDescription off — this Actor fetches it internally for enrichment either way, then still honors your includeDescription choice for what actually ends up in the output snippet field.

If aiEnrichment is on but no matching key is available (anthropicApiKey/ANTHROPIC_API_KEY for aiProvider: "anthropic", or mistralApiKey/MISTRAL_API_KEY for aiProvider: "mistral"), enrichment is skipped: you get one extra dataset row explaining why (warnings: ["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]), a run status message, and every other posting is still returned normally, just without the ai* fields.

This is the same class of field fantastic-jobs' career-site-api prices a whole tier on (ai_key_skills, work arrangement, visa signals) — comparable output here, opt-in and BYOK instead of bundled into every row's price.

Warning rows

Alongside normal posting records, this Actor can push a handful of extra rows that are all null except company/ats/warnings — same flat schema as a posting record, so a dataset-only consumer (no access to the run log) still sees every problem:

Trigger	Example warnings
A companyDomains website couldn't be resolved to a live Ashby board	["no live Ashby board found for 'acme.com' (checked candidate slug(s): acme)"]
A requested company slug 404'd (or hard-failed) on every ATS probed	["not found on any ATS probed (ashby): '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"]
aiEnrichment requested but no API key available	["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]

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 per-posting fee — see this Actor's Pricing tab for the current rates (volume tiers included). 100 postings ≈ $0.25. No subscription — pay only for what you fetch.

If you turn on aiEnrichment, your Anthropic or Mistral key is billed separately by that provider for the enrichment calls themselves — see "AI enrichment" above for a rough per-100-postings cost estimate. Delta mode (onlyNewSinceLastRun) only reduces cost: already-seen postings are dropped before the billed push step.

Use cases

• Track hiring at Ashby-powered startups (OpenAI, Ramp, Linear...)
• Startup-hiring intelligence and talent mapping
• Careers-page aggregation without HTML scraping
• Remote-role discovery via the isRemote flag

FAQ

Is it legal to scrape Ashby jobs? 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 — since 2026-07 — you also get one dataset row for it: {"company": "<slug>", "ats": "...", "warnings": ["not found on any ATS probed (...): '<slug>' (404 on every probe)"]} (or "fetch failed on every ATS probed ..." for a network/5xx failure rather than a clean 404). Previously this was only visible in the run log, easy to miss across a 50-slug batch. Full board URLs are also accepted and reduced to slugs automatically. See "Warning rows".

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.

This Actor saved you time? A quick ⭐ review on the Store page genuinely helps other developers find it — and tells us what to build next.

Related Actors

• Greenhouse Jobs Scraper — Company Job Boards
• Lever Jobs Scraper — Company Job Postings API
• Workable Jobs Scraper — Company Job Boards
• Company Careers Scraper — Greenhouse Lever Ashby
• 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.