Career Site Job Feed MCP server

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:

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.

• Every platform has a different shape. Greenhouse nests offices and departments; Workday sends

Greenhouse or Personio boards. The slug is in a careers URL somewhere, if you can find the careers URL.

• Finding out who is on which platform is the actual work. There is no public directory of

"posted in the last N days" filter has to decide what to do with rows whose age is unknown.

• Dates are unreliable. Three of these ten platforms publish no posting date at all, so any

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.

Shortened. The full README is on GitHub.