Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

Pull every open job from Greenhouse, Lever and Ashby with three curl commands

Most startups don't host their own careers page. They use an ATS (applicant tracking system), and the three big ones (Greenhouse, Lever and Ashby) all have a public, unauthenticated JSON API behind the job board. No scra

Most startups don't host their own careers page. They use an ATS (applicant tracking system), and the three big ones (Greenhouse, Lever and Ashby) all have a public, unauthenticated JSON API behind the job board. No scraping, no headless browser, no API key.

If you're building a niche job board, tracking competitor hiring or just job hunting with a script, this is the cleanest data source there is.

1. Find the company's slug

Open the company's careers page and look at where "Apply" links go:

ATS Board URL Slug
Greenhouse boards.greenhouse.io/stripe or job-boards.greenhouse.io/stripe stripe
Lever jobs.lever.co/spotify spotify
Ashby jobs.ashbyhq.com/openai openai

2. Call the API

Greenhouse

curl "https://boards-api.greenhouse.io/v1/boards/stripe/jobs?content=true"

Returns { "jobs": [...] }. Each job has title, location.name, departments, absolute_url, first_published, updated_at. content=true adds the description as HTML-escaped HTML, so unescape it before you strip tags.

Lever

curl "https://api.lever.co/v0/postings/spotify?mode=json"

Returns a bare array. Fields are text (the title), categories.location, categories.team, categories.commitment, workplaceType, hostedUrl, applyUrl and createdAt (epoch milliseconds, not ISO). descriptionPlain gives you plain text for free.

Ashby

curl "https://api.ashbyhq.com/posting-api/job-board/openai?includeCompensation=true"

Returns { "jobs": [...] } with title, department, team, location, secondaryLocations, isRemote, workplaceType, employmentType, publishedAt, jobUrl, applyUrl and descriptionPlain. With includeCompensation=true you also get salary ranges when the company publishes them. Ashby is the best of the three for pay data.

At the time of writing, these three calls return 777 Stripe jobs, 91 Spotify jobs and 852 OpenAI jobs.

3. The annoying part: three schemas

Each API names everything differently:

Greenhouse Lever Ashby
Title title text title
Posted first_published (ISO, local offset) createdAt (epoch ms) publishedAt (ISO)
Remote not a field, guess from location workplaceType isRemote
Description escaped HTML descriptionPlain descriptionPlain
Extra locations offices[] categories.allLocations secondaryLocations[]

So for a list of 200 companies you end up writing a mapper per ATS, plus date normalization, plus "which ATS does this company even use?" detection.

A small normalizer in JS looks like this:

const toIso = (v) => (v == null ? null : new Date(v).toISOString());

function normalize(ats, j) {
  if (ats === 'greenhouse') return { title: j.title, location: j.location?.name, published_at: toIso(j.first_published), url: j.absolute_url };
  if (ats === 'lever')      return { title: j.text, location: j.categories?.location, published_at: toIso(j.createdAt), url: j.hostedUrl };
  if (ats === 'ashby')      return { title: j.title, location: j.location, published_at: toIso(j.publishedAt), url: j.jobUrl };
}

4. Or skip the plumbing

I packaged all of the above as an Apify Actor: ATS Job Board Scraper (Greenhouse, Lever, Ashby). You pass a list like

{ "companies": ["greenhouse:stripe", "lever:spotify", "openai"], "keyword": "engineer", "remoteOnly": true }

and get one unified schema back (ats, company, title, department, location, remote, compensation, published_at, url, apply_url, description_text). A bare slug like openai gets auto-detected across all three ATS. You can schedule it daily with publishedAfter to see only new roles, and export to CSV, Sheets or a webhook. It's pay-per-job, so a 100-job test run costs fractions of a cent.

But the three curl commands above are honestly enough for a one-off. Pick whichever fits.

Endpoints current as of November 2026. These are the same public APIs that power the companies' own career pages, so please keep request rates polite.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.