Company Job Board Finder — Domain to ATS & Careers

Give it a domain. Get the company's job board, which ATS runs it, and how many roles are open right now.

{ "domains": ["ramp.com", "figma.com", "gitlab.com"] }

Real output from that run:

ramp.com     ashby:ramp           124 open roles   jobs.ashbyhq.com/ramp
figma.com    greenhouse:figma     177 open roles   boards.greenhouse.io/figma
gitlab.com   greenhouse:gitlab    189 open roles   boards.greenhouse.io/gitlab

Call it as an API

One domain in, one row out, in a single HTTP call — no polling.

curl -X POST "https://api.apify.com/v2/acts/dev_web_col~ats-finder/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domain": "ramp.com"}'

import requests

r = requests.post(
    "https://api.apify.com/v2/acts/dev_web_col~ats-finder/run-sync-get-dataset-items",
    params={"token": "YOUR_TOKEN"},
    json={"domain": "ramp.com"},
)
board = r.json()[0]
print(board["companyToken"], board["openJobs"], board["boardUrl"])

Pass domains instead of domain to check a whole account list in one call.

Why this exists

Every job-data tool assumes you already know that Stripe is greenhouse:stripe and Ramp is ashby:ramp. Nobody tells you where that comes from. This Actor is the missing step: domain in, board identifier out.

The companyToken it returns (ashby:ramp) is the exact identifier other job Actors accept, so the output of this one feeds straight into the next.

How it finds the board — and how often it works

Two methods, run in order, because they rescue different companies:

Method	What it does	Found
Career page	Reads the company's own /careers and follows the link to its ATS	3 of 8
Endpoint probe	Derives candidate tokens from the domain and confirms them against each ATS API	3 more
Combined		6 of 8 — 75%

Every hit is confirmed against the live ATS endpoint before it is reported. A board that does not answer with real data is not reported at all.

The 25% it misses, and why

Measured on the same run, the two failures are instructive and neither is fixable:

• deel.com — runs an applicant tracking system outside the six supported.
• nvidia.com — runs Workday, whose URL needs a tenant, a host number and a site name unique to each company (NVIDIAExternalCareerSite). Measured: 15 guessed combinations per company, zero hits. It is not discoverable.

found: false means "no public board on a supported platform", not "this company is not hiring".

What you can use it for

What you want	How to ask for it
Enrich an account list with hiring data	domains: [...], read openJobs
Sales triggers — who is staffing up	Sort your list by openJobs
Build a job aggregator	companyToken feeds job-scraping Actors directly
Recruiting competitive intel	Track a competitive set's open-role counts
Find a company's careers page	boardUrl, confirmed live
ATS market share research	Group your list by platform
Qualify inbound leads	A company with 120 open roles has budget
Live API lookup from your product	domain via run-sync-get-dataset-items

Supported platforms

Greenhouse · Lever · Ashby · Workable · SmartRecruiters · Rippling

All six are read through their public JSON endpoints — the same feeds companies use to embed job boards on their own sites. No login, no API key, no anti-bot circumvention.

Honest limits

• 75% detection, measured on 8 real companies. Test your own list before committing to a big job.
• Workday is not detectable and it is the biggest enterprise ATS. If your list is Fortune 500, expect a low hit rate. This Actor is strongest on technology companies, startups and scale-ups.
• openJobs is a live count at the moment of the run, not a historical series.
• A run stops after about 3.5 minutes and delivers what it has, so Apify's automated checks never time it out. Split large lists across runs.
• Company names are not accepted, only domains. A domain is unambiguous; a name is not.

FAQ

Do I need an API key for any of these platforms?

No. All six publish the endpoints this Actor reads so that companies can embed their job boards elsewhere.

What is companyToken for?

It is platform:token — for example ashby:ramp. Job-scraping Actors take that identifier directly, so you can pipe this Actor's output into one of them without any translation step.

Why does it report method?

So you know how much to trust the row. career-page means the company links that board from its own website, which is as certain as it gets. probe means the token was derived and then confirmed against the live ATS endpoint — also verified, just discovered differently.

A company I know is hiring came back found: false. Why?

Either its ATS is outside the six supported, or it runs Workday, whose board URLs cannot be derived from a domain. Both cases are documented above.

Is it legal to read these endpoints?

They are public feeds published so that job boards can be embedded on company websites. No login, no personal data — job counts and board addresses only.

Can I export to Excel, CSV or Google Sheets?

Yes, from the Storage tab of any run, plus the usual Apify integrations with Google Sheets, Airtable, Zapier, Make and Slack.

Can I run it on a schedule?

Yes. Useful for tracking how a target account list's open-role counts move over time.

Related Actors

• Job Scraper — Greenhouse, Lever & Ashby API — feed it the companyToken from here and get the actual postings.
• Company Data Scraper — firmographics, emails and a hiring signal for the same domains.

Where the data comes from

The public JSON endpoints of Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Rippling, plus the company's own careers page. No login, no API key.