Career Site Job Feed README

ATS job feed recipes

Working code for pulling job postings straight out of company applicant tracking systems — Greenhouse, Lever, Workday, Ashby, Workable, SmartRecruiters, Breezy, Personio, Recruitee, BambooHR, Pinpoint and Rippling — and doing something useful with them.

Which ATS API gives you what — salary, posting dates and remote flags across all twelve platforms, measured across 1,549,353 live postings. Nothing else publishes these numbers, so start there if you are choosing which platform to build on.

Every script here runs as-is. Set APIFY_TOKEN and go.

export APIFY_TOKEN=...        # https://console.apify.com/settings/integrations
python python/new_jobs_to_csv.py

Why this exists

Each of these platforms publishes an open JSON endpoint that the company's own careers page reads — no key, no login, no scraping of rendered HTML. The awkward parts are everything around that:

• Every platform has a different shape. Greenhouse nests offices and departments; Workday sends a POST and reports posting age as the string "Posted 30+ Days Ago"; SmartRecruiters caps a response at 100 rows whatever limit you pass; Breezy answers 403 for a board that does not exist, where everyone else uses 404.
• Finding out who is on which platform is the actual work. There is no public directory of Greenhouse or Personio boards. The slug is in a careers URL somewhere, if you can find the careers URL.
• Dates are unreliable. Three of these ten platforms publish no posting date at all, so any "posted in the last N days" filter has to decide what to do with rows whose age is unknown.

The scripts below use Apify Actors that have already dealt with all of that and return one row shape across every platform. You can equally point them at the raw endpoints — the notes at the bottom list them.

Recipes

These Actors bill per row delivered. Every script caps itself at a couple of hundred rows and reads MAX_ROWS if you want more, so running an example does not produce a surprise.

The row shape

Every recipe gets the same fields, whichever platform the job came from:

{
  "provider": "greenhouse",
  "company": "Databricks",
  "companySlug": "databricks",
  "jobId": "7845321",
  "title": "Staff Software Engineer",
  "location": "San Francisco, CA",
  "department": "Engineering",
  "employmentType": "Full-time",
  "remote": false,
  "postedAt": "2026-08-14T09:12:00.000Z",
  "applyUrl": "https://boards.greenhouse.io/databricks/jobs/7845321",
  "salary": null,
  "descriptionText": "...",
  "scrapedAt": "2026-08-19T11:02:41.883Z"
}

companySlug:jobId is stable while a posting is open, which is what makes the diffing recipes work.

What each platform actually publishes

Measured from live boards, not from vendor documentation. Useful before you build on any one of them:

The same table, with the reasoning behind each column, is on the full reference page.

title, company, location and applyUrl come back on every row from every platform.

These are measured numbers, not a feature matrix. Each row is every live board this project tracks for that platform — between 17,000 and 179,000 postings per platform, measured 2026-08-20. yes means 99.5% or more; no means the endpoint carries no such field at all.

Three things the table is telling you:

• Four platforms publish pay, and none of them fills it most of the time. Breezy and Pinpoint come closest at 45.7% and 42.5%. Breezy and Ashby give you prose ("$28 – $100 / hour", "$211.4K – $290.6K • Offers Equity"); Pinpoint and Recruitee give you separate minimum, maximum, currency and period. If you are benchmarking, use the latter two.
• Half the platforms have no posting date. Personio, Rippling, Pinpoint and BambooHR publish none, and Workday dates only 78.2% of rows because it ships prose like "Posted 30+ Days Ago" rather than a timestamp. Any freshness filter has to decide whether to drop undated rows or keep them, and the honest default is to keep them.
• "Remote" is a real field on five platforms and a guess on the rest. Ashby marks 54.2% of its postings remote, which says more about who uses Ashby than about the job market. Where the platform has no such field, the only option is matching the location string, which misses "Anywhere" and misfires on "Remote Support Engineer, London office".

Raw endpoints

If you would rather call the platforms directly, these are the public endpoints. All of them answer without a key. Replace {company} with the board slug.

Four things that will bite you if you write your own client:

• SmartRecruiters returns at most 100 postings per response regardless of limit. Page with offset, and take the real total from totalFound rather than counting rows.
• 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.
• BambooHR splits its careers API in two. /careers/list has no posting date, description or compensation; those live on /careers/{id}/detail, one request per posting. And its isRemote field exists but is never populated — across 50,616 postings measured, not one had it set.
• Breezy returns 403, not 404, for a subdomain with no board on it. Treating that as rate limiting and backing off turns a half-hour job into a fourteen-hour one.

Licence

MIT. The Actors these scripts call are commercial and priced per row; the code here is not.