Which ATS API gives you what

Twelve applicant tracking systems publish an open JSON endpoint that their customers' careers pages read. They do not publish the same fields, and the gaps are not documented anywhere. This page is the measurement.

Every percentage below was measured across every live board we track for that platform — not a sample. Between 17,000 and 179,000 postings per platform, 1,549,353 in total, on 2026-08-20. yes means 99.5% or more; no means the endpoint carries no such field at all.

The table

title, company, location and an apply URL come back from every one of them.

Which ATS APIs publish salary?

Four, and none of them fills it most of the time. They also disagree on form, which matters more than the fill rate if you are benchmarking:

• Pinpoint (42.5%) and Recruitee (26.9%) store minimum, maximum, currency and period as separate numbers. These are the two you can compute on.
• Breezy HR (45.7%) — the highest fill rate — and Ashby (38.9%) return a human-written string: "$28 – $100 / hour", "$211.4K – $290.6K • Offers Equity". Parsing those into numbers is guesswork about currency, period and whether equity is included.
• The other eight expose no compensation field at all. No scraper can invent one.

Recruitee keeps the salary object present with zeros when the employer skipped the field, so a naive reader ships "0 USD hour" as a pay range. Treat min <= 0 && max <= 0 as absent.

Which ATS APIs give a real posting date?

Seven date effectively everything. Personio, Rippling, Pinpoint and BambooHR publish no date at all, and Workday dates only 78.2% of rows because it ships prose — "Posted Today", "Posted 30+ Days Ago" — instead of a timestamp. An exact age can be converted; 30+ genuinely is unknown.

If you are building a "posted in the last 7 days" filter, that is a design decision, not a detail: you either drop undated rows and silently lose a third of the market, or keep them and let the filter mean less than it says. Saying which one you did is the honest option.

Which ATS APIs have a real "remote" field?

Five publish a work-arrangement field the employer filled in: Ashby, Recruitee, Workable, Pinpoint and SmartRecruiters. The other seven do not, so the only option there is pattern-matching the location string — which misses "Anywhere" and misfires on "Remote Support Engineer, London office".

The spread between platforms says more about their customers than about the job market. 54.2% of Ashby postings are marked remote; Lever, where the flag has to be inferred, resolves to 4.8%.

BambooHR is the trap. It has an isRemote field, so a reader assumes it works. Across 50,616 postings measured, not one had it set.

One page per platform

Each of these goes deeper on one API — the exact request shape, what it returns measured across every live board, the mistakes that cost us time, and how its boards are actually found:

Greenhouse · Lever · Ashby · Workday · SmartRecruiters · Workable · Breezy HR · Personio · Recruitee · BambooHR · Pinpoint · Rippling

The endpoints

All of these answer without a key. Replace {company} with the board slug.

Things that will bite you

• SmartRecruiters returns at most 100 postings per response whatever limit you pass. Page with offset, and take the real count from totalFound rather than counting rows.
• Breezy HR answers 403, not 404, for a subdomain with no board on it. Treating that as rate limiting will make you back off from boards that simply do not exist.
• Workday saturates total at 2000 and keeps serving rows past the end of the list, so probing offsets until a page comes back empty never terminates. The facets counts are the real total. Site names are case-insensitive, so the same board arrives twice unless you lowercase the key.
• BambooHR splits its API in two. /careers/list has no date, description or compensation; those live on /careers/{id}/detail, one request per posting.
• Finding out who is on which platform is the actual work. There is no public directory of Greenhouse or Personio boards. Slugs live in careers URLs, and the Wayback CDX index is the practical source — but it sorts by urlkey, so a domain's own pages fill the first pages and customer subdomains sit deep in the index. Reading only the first few pages is how you conclude a platform "has no public boards" when it has thousands.

Running any of this

The code behind these measurements is open: github.com/HwangByeongSeon/ats-job-feed-recipes. If you would rather not maintain twelve clients and a board registry, the same engine runs as a hosted Actor that emits one row shape across every platform above — Career Site Job Feed, or New Job Alerts if you only want what changed since your last run.

Single-platform Actors, if you only need one: Greenhouse · Lever · Ashby · Workday · Workable · SmartRecruiters · Breezy HR · Personio · Recruitee · Rippling · Pinpoint

How this was measured

Each platform's board registry was walked in full and every live board's listing endpoint was read once. A field counts as present when the parsed row carries a non-null value for it, using the same normalizer across all twelve platforms so the columns are comparable. Boards that answered with an error or returned no postings were excluded rather than counted as zeros.

The numbers move. Boards close at roughly 0.6% every day and a half, and employers fill fields differently over time. The date on this page is the date it was measured.