ATS Database — 40,097 Company Career Pages, Free to Search

Free. Type a company name, get back which applicant tracking system it uses, its career page URL, and the public API endpoint that serves its jobs. No scraping happens, so there is nothing to charge for.

{ "companies": ["notion", "figma", "anthropic"] }

{ "providers": ["recruitee"], "minPostings": 50, "sortBy": "postings" }

What you get back

Field	Description
company	The employer, as the board is registered
provider	Which ATS — one of twelve
companySlug	The identifier in the career page URL, which is what every API wants
knownPostings	Open postings at the last registry refresh — not live, see below
careerPageUrl	The page a human opens
apiEndpoint	The public JSON endpoint, ready to call
apiMethod	GET for eleven platforms, POST for Workday
fetchJobsWith	The Actor that reads that platform, if you would rather not write a client

Why this exists

Every one of these platforms publishes an open JSON endpoint that the employer's own careers page reads — no key, no login. The hard part is not calling it. The hard part is knowing that Notion is on Ashby, Figma is on Greenhouse, and what string to put in the URL. There is no public directory of that, so everyone rebuilds it.

This is that directory: 40,097 boards across twelve platforms, carrying 1,551,977 open postings at last count.

Matching is forgiving

You do not need the slug. Acme Inc., acme.com and https://jobs.lever.co/acme all find the same board — punctuation, www., and common domain endings are stripped before matching.

Exact and prefix matches win. If a search has one, loose substring hits are dropped rather than padded in — searching notion returns Notion, not ion. Only when nothing exact or prefix-like exists does it fall back to substring matches, so a vague search still returns something.

What this Actor does not do

• It does not fetch jobs. It tells you where they are. Every row carries the endpoint and the Actor that reads it.
• knownPostings is not live. It is the count from the last registry refresh, which runs monthly. Treat it as board size, not as today's openings.
• It cannot see private boards. Employers who keep their careers module closed are invisible to every tool, including this one.
• Coverage is not everyone. 40,097 boards is what has been found and verified, not every company on earth. A miss means we have not found that board yet, not that the company has no career page.

Coverage by platform

Platform	Boards
BambooHR	9,711
Greenhouse	5,751
Personio	5,172
SmartRecruiters	4,334
Ashby	3,000
Breezy HR	2,800
Workday	2,658
Lever	1,917
Workable	1,710
Rippling	1,298
Recruitee	1,126
Pinpoint	620

Recipes

Check one company before you build. Paste the name, see whether it is reachable at all and on which platform, then point the matching Actor at the slug.

Size a platform. Leave companies empty, set providers to one platform and minPostings to 50, and you get every employer on it that is actively hiring, largest first.

Build a target list. Filter by platform and posting count, export the companySlug column, and feed it straight into the companies input of any Actor below.

Then what

• Career Site Job Feed — one run across every platform here, one row shape.
• New Job Alerts — the same coverage, but each run returns only what appeared since the last one.
• Single-platform Actors are linked from each row's fetchJobsWith.

If you would rather write your own client, the endpoints and the measured field coverage for all twelve platforms are documented here: Which ATS API gives you what.

Notes

• No network requests. The registry ships inside the Actor, so a run is a lookup and finishes in about a second.
• Free. There is no per-result charge. You pay only the platform compute for a one-second run, which is a fraction of a cent.