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.

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

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".

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).
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.
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".
concurrency	integer	8	Companies fetched in parallel (advanced).

What Ashby jobs 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.

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 / postedWithin / 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

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": "ashby",
  "id": "a1b2c3",
  "url": "https://example.com/ashby/jobs/a1b2c3",
  "title": "Senior Backend Engineer",
  "company": "Example Company",
  "locations": [
    "Bilbao",
    "Spain"
  ],
  "postedAt": "2026-09-02T00:00:00Z",
  "deadline": "2026-10-15",
  "description": "The complete posting body as plain text, exactly as the source published it — never truncated.",
  "descriptionHtml": "<p>The complete posting body as the source's own markup.</p>",
  "workType": "remote",
  "custom": {
    "schemaId": "nomad-agent-job-custom-ashby-v1",
    "data": {
      "globalId": "…",
      "department": "…"
    }
  }
}

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.

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 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"]

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.

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 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".

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.