Source · AshbyAshby Jobs API.
Ashby's Job Board endpoint covers one company at a time. JobsPipe covers every public Ashby customer in one call, in the same JSON shape as 30+ other ATSs.
Why people are confused about the Ashby API
Ashby exposes a public Job Board endpoint at api.ashbyhq.com/posting-api/job-board/<organizationName> that returns a single customer's published postings without authentication. That is what most developers find first. It works fine for one customer, but it does not scale to many: there is no list endpoint to discover Ashby customers, no cross-customer key, and the organization slug must be known up front.
Ashby also ships a full REST API at api.ashbyhq.com (separate from the public Job Board) covering jobs, candidates, applications, offers, sources, and webhooks. That API requires an API key minted inside the customer's Ashby admin under Settings > API. Each key is tenant-scoped, so it cannot read jobs from any company other than the one that generated it. For aggregator workloads (jobs across many Ashby-using companies), the in-Ashby surfaces alone do not get you there.
JobsPipe sits in front of every public Ashby careers site. We index jobs.ashbyhq.com/<organization> for every public customer plus the customer-owned domains that proxy Ashby through embeds, normalize the data into the same JSON schema we use for Workday, Greenhouse, and 30+ other ATSs, and serve it through one endpoint with one key. Free tier covers 5,000 requests/month with no credit card.
Works for one named Ashby customer. You must know the organization slug and write a separate fetch per company. No customer-discovery surface and no cross-customer pagination - if you want jobs across many Ashby customers, you need that list from somewhere else first.
Possible for one or two named accounts. Each Ashby customer would have to mint you an API key in their admin and grant access to the jobs surface. Impossible at the scale of a multi-company aggregator.
Every public Ashby customer, one endpoint, one key. Same normalized JSON schema as Workday, Greenhouse, Lever, Indeed, and 30+ other sources. Free tier of 5,000 requests/month with no credit card.
Ashby API documentation
Ashby's developer documentation lives at developers.ashbyhq.com. The major surfaces it covers: the public Job Board endpoint (api.ashbyhq.com/posting-api/job-board/<organizationName>, unauthenticated, returns one customer's postings), the authenticated Ashby API at api.ashbyhq.com/v1/ (jobs, candidates, applications, offers, sources, scheduled interviews, webhooks - all customer-scoped), and the Embed API used by Ashby customers to render their own jobs on their marketing site. None of these cover cross-customer aggregation. JobsPipe's documentation at /docs covers a normalized JSON schema we return for every public Ashby customer alongside 30+ other ATSs in the same shape.
Ashby API key and authentication
The authenticated Ashby API uses HTTP Basic Auth with the API key as the username and an empty password. Keys are minted inside the customer's Ashby admin under Settings > API and scoped per-customer. There is no Ashby developer key for cross-tenant reads. The public Job Board endpoint at api.ashbyhq.com/posting-api/job-board/<organizationName> bypasses auth entirely for the one customer whose slug is in the URL. JobsPipe doesn't request Ashby credentials - we read only public-facing data and authenticate every request with one JobsPipe Bearer token in the Authorization header.
Ashby Job Board API
The Ashby Job Board API at api.ashbyhq.com/posting-api/job-board/<organizationName> returns a single customer's currently-published job postings as JSON, with fields for title, location, department, employment type, and a deep link to the apply page on jobs.ashbyhq.com. It is the surface JobsPipe and other aggregators consume for Ashby customers. Important constraints: one customer per call, no customer-discovery endpoint, no historical data, rate-limited per IP. For cross-customer coverage, freshness guarantees, and access to expired postings, the JobsPipe layer on top is what most teams arriving at this page actually need.
Ashby API integration
For a single Ashby customer (sync candidates from your CRM, post jobs from your HRIS, react to offer events), you go through the in-Ashby API key flow and call api.ashbyhq.com/v1 directly. For cross-customer integration - reading jobs across many Ashby-using companies into a single feed - the practical path is JobsPipe: every public Ashby customer indexed every 24 hours, served in the same JSON schema as Workday, Greenhouse, Lever, Indeed, and 30+ other sources, with one key.
Ashby API alternatives
If you need cross-customer Ashby data, the alternatives are: maintain your own list of Ashby customer slugs and poll the public Job Board endpoint per customer (works but customer discovery is your problem), apply for Ashby Embed API access per customer (does not scale), or use JobsPipe which already maintains the customer list, handles polling and rate-limiting, and serves Ashby data alongside 30+ other sources in one normalized shape. Free tier of 5,000 requests/month with no credit card.
Companies using Ashby
Ashby is the ATS of choice for a particular slice of the modern tech industry: AI labs (OpenAI, Anthropic parts), developer-tools companies (Linear, Vercel, Stripe parts, Substack), neobanks and fintech (Mercury, Ramp, Brex parts), and a long tail of YC-backed startups. JobsPipe's Ashby coverage spans every public Ashby careers site, so 'companies using Ashby' is implicitly answered every time you hit /v1/jobs?source=ashby - the unique tenant values in the response are the live list.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=ashby" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "as_YzNhMGJjMjMtZTY0Zg",
"source": "ashby",
"tenant": "linear",
"title": "Software Engineer, Sync Engine",
"company": "Linear",
"location": {
"city": null,
"region": null,
"country": null,
"remote": true
},
"salary": {
"min": 180000,
"max": 240000,
"currency": "USD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-11T16:30:00Z",
"expires_at": null,
"apply_url": "https://jobs.ashbyhq.com/linear/...",
"description": "Linear is hiring backend engineers to work on the sync engine, data model, and graph-based query layer that powers our real-time collaboration ..."
}Every Ashby job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every Ashby job record
FAQ
Is the Ashby API free?+
Ashby's public Job Board endpoint (api.ashbyhq.com/posting-api/job-board/<organizationName>) is free and unauthenticated, but only returns one customer's jobs per call. The full Ashby REST API requires a customer-issued key. JobsPipe's free tier (5,000 requests/month, no card) covers every public Ashby customer through one endpoint - usually what teams looking for 'free Ashby API' actually need.
How do I get an Ashby API key?+
Inside the customer's Ashby admin, go to Settings > API and mint a new key. Each key is scoped to that customer's tenant. If you don't have admin access to an Ashby account, you can still use Ashby's public Job Board endpoint for that customer without a key - or use JobsPipe to read every public Ashby customer with one JobsPipe key.
Does Ashby's public Job Board endpoint require authentication?+
No. api.ashbyhq.com/posting-api/job-board/<organizationName> is unauthenticated and returns currently-published postings for that organization. Note it only returns one customer's jobs per call - there is no list endpoint that enumerates Ashby customers.
What's the difference between the Ashby API and the Ashby Embed API?+
The Ashby API (api.ashbyhq.com) is the full REST surface for jobs, candidates, applications, offers, and webhooks - it requires a customer-minted key. The Embed API is a smaller surface that Ashby customers use to embed their own job board on their marketing site. Neither is built for cross-customer aggregation. JobsPipe is.
How do I scrape jobs from Ashby?+
The official public surface is api.ashbyhq.com/posting-api/job-board/<organizationName> - read the JSON directly, no scraping needed for a single customer. For cross-customer coverage, you would either maintain a list of every Ashby customer slug yourself, or use JobsPipe, which already does this and refreshes every 24 hours.
What's Ashby's API rate limit?+
Ashby's authenticated API uses request quotas tied to the customer's plan and is documented per-endpoint at developers.ashbyhq.com. The public Job Board endpoint is rate-limited per IP and is not suitable for high-volume polling. JobsPipe's tier-based limits start at 5,000 requests/month free and scale up - the underlying Ashby polling happens on our side.
Can I filter Ashby jobs by department, location, or remote status?+
Yes. Use ?tenant=<organization-slug> to narrow to one Ashby customer, ?department=engineering to filter by department, and ?location.country=US or ?remote=true for location filters. Full filter list is in our docs.
Does JobsPipe support Ashby webhooks?+
JobsPipe emits its own webhook events on posting changes (new, updated, closed) for every public Ashby customer we cover, with the same JSON shape as our REST responses. We do not relay Ashby's customer-private webhook surface - only events tied to public job-board changes.
Which Ashby customers does JobsPipe cover?+
Every public Ashby careers site. That includes Linear, Ramp, Mercury, Notion, Vercel, Substack, OpenAI, Anthropic (parts), and roughly 2,000 other public Ashby organizations as of 2026.
Try Ashby data free - 5,000 requests/month, no credit card.
Get a free API key