Job Board Scraper: Greenhouse, Lever, Ashby, SmartRecruiters & Workday

Pull open roles straight from companies' own career boards. Give it a list of companies; it works out which of five systems each one uses and returns every job in a single consistent shape.

Why these sources

All five publish official public job-board APIs: companies expose them deliberately so their openings can be syndicated. That means no blocking, no login, and no grey area, unlike scraping a job aggregator.

It also means the data is first-party: straight from the employer, before it's rewritten or delayed by an aggregator.

Auto-detect

You rarely know which ATS a company uses. Enter the board name from their careers URL and the Actor works it out:

Careers URL	Enter
boards.greenhouse.io/stripe	stripe
jobs.lever.co/acme	acme
jobs.ashbyhq.com/ramp	ramp
jobs.smartrecruiters.com/Visa	Visa
nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite	the whole URL

Filter before you pay

{
  "companies": ["stripe", "ramp", "figma"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true,
  "includeDescription": true
}

Filters run before billing, you are charged only for jobs actually returned, not for everything scanned.

Do you need an API key? No. Is there a free tier? Yes.

The two things people search for in this category, measured, are free and API key: job board api free, job board api key.

So, plainly:

• No API key. Nothing to register for, nothing to rotate, no key to leak in a repo. The source is a public API published deliberately by its owner.
• No proxy setup. The source does not bot-wall datacenter addresses, so the default works.
• Pay per result, not per month. There is no subscription and no minimum. Rows that error or that your filters drop are not charged.
• Free to try. Run it with the prefilled input and see real rows before deciding anything.

What you get per job

Always: company · ats · jobId · title · location + locations · remote · url · description (clean text, HTML stripped)

Where the ATS publishes it: department + departments · postedAt · updatedAt · employmentType (Lever, Ashby, SmartRecruiters; Greenhouse does not expose it) · compensation (Ashby) · seniority (SmartRecruiters) · postedAgo (Workday, which publishes "Posted 3 Days Ago" rather than a date)

The split matters: a flat list reads as a guarantee, and a customer who writes code against employmentType will get null on every Greenhouse row.

Use cases

• Hiring-signal intelligence: a company suddenly opening 12 sales roles is a growth signal; schedule this weekly and watch headcount plans
• Job boards & aggregators: build a niche board from first-party listings
• Recruiting: track which competitors are hiring the roles you're filling
• Sales prospecting: companies hiring for a stack are buying tools for it
• LLM pipelines: descriptions come through as clean text, ready to summarise or classify

Which ATS, and how the board is found

Five applicant tracking systems, covering startups through to the largest enterprises. Every one of these publishes its job board openly, because that is how a company's own careers page renders its listings, so no key is involved anywhere:

ATS	Public board endpoint	Set ats to	Typical company
Greenhouse	boards-api.greenhouse.io job board API	greenhouse	startups and scale-ups
Lever	api.lever.co postings API	lever	startups and scale-ups
Ashby	Ashby's public job board API	ashby	newer startups
SmartRecruiters	api.smartrecruiters.com postings API	smartrecruiters	mid-market and enterprise
Workday	the career site's own wday/cxs endpoint	workday	large enterprises

Workday is the one that reaches the big companies. Most of the Fortune 500 posts there rather than on a startup ATS, so a competitor-hiring watch that skips Workday misses exactly the companies you most want to watch. NVIDIA alone lists around 2,000 open roles through it.

Leave ats on auto and each company is tried against Greenhouse, Lever, Ashby and SmartRecruiters, so a mixed list resolves without you knowing which system anyone uses.

Workday needs its careers URL, not a company name. Its address carries three things that a company name cannot produce: a host label, a data-centre number and a career-site name, as in nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite. Guessing across those would mostly generate 404s and bill you for the attempts, so instead you paste the careers URL you already have and it is parsed for you.

You do not have to set ats for it, though. A Workday address identifies itself, so auto recognises one on sight and routes it straight there. Mix Workday URLs and plain board slugs in the same list and each is handled the right way.

A Greenhouse job board API key is not required. The board endpoint is public by design, since it is what the company's own careers page calls to render the listings. The companies input takes the board token from the careers URL, so boards.greenhouse.io/stripe means stripe.

Every job posting comes back with title, location, department, employment type, remote flag, posted date, compensation when the company publishes it, and a direct apply URL.

Notes

• Descriptions are HTML-stripped into plain text, capped at 5,000 characters.
• Companies with no public board on any of the five systems return a clear error row naming the problem. Error rows are never charged.
• Public job postings only, no candidate data, no personal data.