Ashby Jobs API — 2,996 Career Pages, Half of Them Remote

Ashby is an applicant tracking system used mainly by venture-backed technology companies, and its job board API is open. It is also, measurably, the most remote-heavy source in this family.

Point it at a company, or leave the list empty and search a bundled registry of 2,996 live Ashby career pages carrying 52,191 open postings.

{ "keywords": ["engineer"], "postedWithinDays": 14, "maxJobs": 200 }

{ "companies": ["https://jobs.ashbyhq.com/openai"] }

No login, no cookies, no proxies, no API key.

More than half the postings here are remote

Measured across every live board in this registry — 32,407 postings from 1,588 boards:

Work arrangement stated by the employer	85.1%
Marked remote	54.2%

That is not a claim about the job market. It is a fact about who uses Ashby — remote-friendly technology companies. If you are building a remote job board or sourcing distributed talent, this is the highest-yield single platform in this family, and remoteOnly filters on the employer's own checkbox rather than on a regular expression over the location string.

Everything is dated and described

Field	Fill rate (all 32,407 postings in this registry)
postedAt	100%
descriptionText	100%
department	~100%
employmentType	~100%
remote	85.1%
salary	38.9%

postedWithinDays works properly here — every row carries a real publish date, so a 7-day or 14-day window means what it says. On the platforms with no date (Workday, Rippling, Pinpoint, BambooHR) that filter has to keep undated rows rather than drop them.

What you get

Field	Description
provider	Always ashby — the same schema the multi-ATS Actors below emit
company / companySlug	Employer board name
jobId	Ashby posting id — stable, so it works as a dedupe key across runs
title	Job title
location	Location as the employer entered it
department	Department, from the employer's own org structure
employmentType	Full-time, contract, intern
remote	Ashby's own isRemote flag
postedAt / updatedAt	Publish and last-change timestamps
applyUrl	Direct link to the posting
descriptionText	Full posting text as readable plain text
salary	Ashby's compensation summary where the employer published one — see below
scrapedAt	When this row was read

About the pay field

Ashby returns compensation as a human-readable summary, not as numbers:

{ "salary": "$211.4K – $290.6K • Offers Equity" }

This Actor passes that through as written. It does not parse it into a minimum and maximum, because the string mixes currency, period and equity notes in ways that differ per employer, and inventing structure over that would be guessing. 38.9% of postings carry it.

If you need pay as separate numbers, Recruitee and Pinpoint publish minimum, maximum, currency and period as real fields — both linked below.

Input

Option	What it does
keywords	Keep only titles containing one of these. Case-insensitive.
excludeKeywords	Drop titles containing any of these, e.g. senior, intern.
locations	Keep only locations containing one of these.
remoteOnly	Keep only postings the employer marked remote. Real field, not a regex.
postedWithinDays	Freshness filter. Every Ashby row has a real date, so this works properly.
companies	Board names or board URLs. Leave empty to search all 2,996.
maxBoards	How many boards to scan, largest-first.
maxJobs	Hard cap on rows, so a run costs what you expect.

Finding a company slug

The board lives at jobs.ashbyhq.com/<slug>, so the slug is the last path segment. Paste the whole URL and the Actor extracts it. Or run without companies and read the companySlug column.

Recipes

A remote job board, cheaply. remoteOnly plus postedWithinDays: 7, run daily. Over half the rows here already qualify, so you spend far less on rows you then throw away than on a general feed.

Track hiring at venture-backed companies. Ashby's user base skews to funded startups, so a diff of jobId between runs is a reasonable proxy for who is scaling and in which department.

Full-text search. Descriptions come back on every row as plain text, so one run gives you a corpus you can grep for a framework, a certification, or a seniority signal the title never says.

Pricing

Pay per result — you are charged per job row delivered. A board that fails or returns nothing costs you nothing. Platform usage is included rather than billed on top.

Beyond Ashby

Companies move between applicant tracking systems, and most job-data projects need more than one:

• Career Site Job Feed — the same engine across every platform in this family, in one run, with an identical output schema.
• New Job Alerts — the same coverage, but each run returns only what appeared since the previous run.
• Recruitee Jobs API — structured pay ranges with currency and period.

Notes

• A dead slug never aborts the run. Failures land in a FAILED_BOARDS record in the key-value store, with the reason for each.
• companySlug:jobId is a stable key, safe for detecting what opened and closed between runs.
• No login, no proxies, no API key. Ashby publishes this board API openly.