Company Hiring Signals: Greenhouse, Lever & Ashby Jobs API
Pricing
$10.00 / 1,000 company hiring signals
Company Hiring Signals: Greenhouse, Lever & Ashby Jobs API
One row per company: open roles, new and closed roles since your last run, departments, seniority, remote share, locations and a ramping / steady / shrinking hiring signal. From the public Greenhouse, Lever and Ashby job-board APIs. For sales intelligence and account research.
Pricing
$10.00 / 1,000 company hiring signals
Rating
0.0
(0)
Developer
Atesen Software
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Features
Share
Find out which companies are hiring now, and how fast. Give this Actor a list of companies and get one row per company: open roles, new and closed roles since your last run, departments, seniority mix, remote share, top locations and a plain ramping / steady / shrinking hiring signal.
It reads the official public job-board APIs of Greenhouse, Lever and Ashby. No login, no proxy, no browser, no company websites crawled.
Built for sales intelligence and account research: SDR and AE teams who want hiring data as a buying signal, recruiting agencies looking for companies that are ramping, investors tracking portfolio and competitor headcount plans.
What you get per company
| Field | Meaning |
|---|---|
company, ats, slug | Company name (from Greenhouse, otherwise the slug), which ATS, the board slug |
openRoles | Open roles that match your filters |
newRolesSinceLastRun, closedRolesSinceLastRun | Role IDs that appeared or disappeared since your previous run. null on the first run (that run sets the baseline) |
closedRoleIds | Up to 50 IDs of roles that closed |
rolesPostedLast30Days | Roles first published in the last 30 days |
hiringSignal, signalBasis | ramping, steady, shrinking or unknown, and what it was based on (rules below) |
departments | Role count per department (top 25, rest under (other)) |
seniority | Role count per seniority level, classified from the title |
remoteShare, hybridShare | Share of roles marked remote / hybrid (0 to 1) |
topLocations, topCountries | Five most common locations and country codes |
oldestPostedAt, newestPostedAt | Oldest and newest posting dates |
sampleRoles | Up to 5 roles (title + URL), new roles first, then newest |
guessedFrom | null when you gave the ATS (ats:slug or a board URL). slug-auto-detect or domain when the board was found by trying the slug: check company and sampleRoles URLs, because a different company can own the same slug on another ATS |
source, attribution, checkedAt | Which API the data came from and when |
Turn on Include the full role list to add a roles array: title, URL, department, team, location, country, workplace type, employment type, seniority, posted date and isNew.
Companies that are not found, invalid lines and API errors come back as rows with status = not_found, invalid_input or error and a message. They are not charged.
Input
{"companies": ["greenhouse:stripe", "lever:palantir", "ashby:ramp", "https://jobs.lever.co/palantir", "notion", "notion.so"],"onlyChanged": false,"includeRoles": false,"departments": ["Engineering"],"locations": ["US", "London"],"workplaceTypes": ["remote", "hybrid"],"seniority": ["senior", "staff_principal"]}
Each company line can be:
ats:slug, for examplegreenhouse:stripe,lever:palantir,ashby:ramp(fastest and exact)- a job-board URL:
boards.greenhouse.io/…,job-boards.greenhouse.io/…,jobs.lever.co/…,jobs.ashbyhq.com/… - a bare slug such as
notion: tried on Greenhouse, then Lever, then Ashby - a domain such as
notion.so: its first label (notion) is tried as a slug on the three APIs. This is a guess. The company website itself is never fetched, so a company whose board slug differs from its domain will come backnot_found; give theats:slugpair for those.
Bare slugs and domains are matched by name only: the first of the three APIs with a board of that name and open roles wins, so the row can belong to a different company with the same slug. Such rows carry guessedFrom; use ats:slug when you need an exact match. The same company given twice in one run (for example stripe and greenhouse:stripe) is checked and charged once.
All filters are optional and case-insensitive. A different filter set keeps its own change history.
Example output
{"company": "Acme","ats": "greenhouse","slug": "acme","status": "ok","openRoles": 42,"newRolesSinceLastRun": 6,"closedRolesSinceLastRun": 1,"previousOpenRoles": 37,"rolesPostedLast30Days": 11,"hiringSignal": "ramping","signalBasis": "change-since-last-run","departments": { "Engineering": 18, "Sales": 12, "Customer Success": 7, "Marketing": 5 },"seniority": { "senior": 14, "unspecified": 12, "manager": 6, "staff_principal": 4, "junior": 3, "director": 2, "intern": 1 },"remoteShare": 0.31,"topLocations": [{ "location": "New York, NY", "count": 15 }, { "location": "Remote - US", "count": 9 }],"oldestPostedAt": "2026-03-02T15:10:00.000Z","newestPostedAt": "2026-11-07T09:00:00.000Z","sampleRoles": [{ "title": "Senior Account Executive, EMEA", "url": "https://boards.greenhouse.io/acme/jobs/123" }],"source": "Greenhouse Job Board API (boards-api.greenhouse.io)","checkedAt": "2026-11-08T12:00:00.000Z"}
How the hiring signal is decided
The rules are simple on purpose, so you can trust and explain them.
From the second run on (signalBasis = change-since-last-run), comparing with the previous run's open roles:
ramping: at least 2 more open roles and at least 10 % moreshrinking: at least 2 fewer open roles and at least 10 % fewersteady: anything in betweenunknown: no open roles now or before
On the first run (signalBasis = posting-age), there is no history yet:
ramping: at least 40 % of dated roles were first published in the last 30 dayssteady: otherwiseunknown(not-enough-data): fewer than 5 dated roles- A single snapshot never says
shrinking: old postings are often evergreen roles, not a slowdown.
Run it on a schedule (weekly works well) to get real change data. Ashby's publishedAt is the last publish date, so a re-published role can look newer than it is.
Seniority rules (from the job title)
First matching rule wins:
intern: intern, internship, co-op, apprentice, trainee, working studentexecutive: chief (not chief of staff), CEO/CTO/CFO/COO/CMO/CIO/CPO, CISO, VP, vice president, SVP, EVP, president, general counsel (not associate / assistant / deputy)director: director, head ofmanager: manager / mgr, except titles that are usually individual roles (product, account, project, program, partner, customer success, marketing, solutions, territory and similar "… manager" titles)staff_principal: staff, principal, distinguished, fellow, architectlead: lead, team lead, tech leadsenior: senior, sr, III, IVjunior: junior, jr, entry level, graduate, new grad, associate, "Engineer I"unspecified: no level word in the title
Keyword rules make mistakes on unusual titles; use the counts as a mix, not as an org chart.
Use cases
- Sales intelligence hiring data: push companies that start ramping in Sales or Engineering into your CRM as warm accounts.
- Account research: see where a target company is hiring, which teams grow and how remote-friendly it is before a call.
- Recruiting agencies: find companies hiring now in your niche (filter by department, seniority and location).
- Market and competitor tracking: weekly watchlist with
onlyChangedon, so you only see companies that moved.
Monitoring with "only changed"
Turn on Only companies that changed since the last run and schedule the Actor. Role IDs are kept in a key-value store in your account. Each run returns rows only for companies with new or closed roles; unchanged companies are skipped and cost nothing. To keep the history, pick or create a key-value store in Change-history store and use the same store for every run of that watchlist (a different store per watchlist). Without a picked store the Actor still runs, treats every company as a first check, and says in the run notes that change history was unavailable.
Limits (honest)
- Covers only companies that publish jobs through Greenhouse, Lever or Ashby. Companies on Workday, SmartRecruiters, iCIMS, Taleo, their own systems or only on job sites are not covered.
- No LinkedIn, no Indeed, no job aggregators. Data is what the company itself publishes on its ATS board.
- Lever and Ashby do not return a company display name, so
companyis the slug for those. - Departments are whatever the company configured (some use cost-centre names or code names).
- Recruiter or hiring-manager names, e-mails and phone numbers are never returned. Job descriptions and custom ATS fields are dropped; only a fixed list of role fields is kept.
- Up to 1,000 companies per run, 2 in parallel by default to stay polite to the public APIs.
Use via API
One request runs the Actor, waits for it and returns the dataset items as JSON. Send your token in the Authorization header, not in the URL:
curl -X POST "https://api.apify.com/v2/acts/atesen-software~company-hiring-signals/run-sync-get-dataset-items?timeout=120" \-H "Authorization: Bearer $APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"companies":["greenhouse:stripe","lever:palantir","ashby:ramp"]}'
The synchronous endpoint waits up to 300 seconds. For longer jobs start a run with POST https://api.apify.com/v2/acts/atesen-software~company-hiring-signals/runs and read the dataset when it finishes.
JavaScript (npm install apify-client):
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('atesen-software/company-hiring-signals').call({ companies: ["greenhouse:stripe", "lever:palantir", "ashby:ramp"] });const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Use with AI agents (MCP)
Claude Desktop, Cursor, VS Code and other MCP clients can call this Actor as a tool through the Apify MCP server. Load only this Actor with:
https://mcp.apify.com?tools=atesen-software/company-hiring-signals
Client config (sign in with Apify OAuth when the browser opens, or add an Authorization: Bearer <APIFY_TOKEN> header instead):
{"mcpServers": {"apify": { "url": "https://mcp.apify.com?tools=atesen-software/company-hiring-signals" }}}
Then ask in plain words, for example: "How many open roles do Stripe, Palantir and Ramp have right now, and in which teams?" The agent fills the same input fields you see on the Input tab, and runs are billed to your Apify account at the prices on the Pricing tab.
Pricing
Maximum items is a hard cap on charged rows. Set maxItems in the run options (or ?maxItems= in the API) and the run stops after that many companies: it never writes or charges more rows than that number. Leave it empty for no cap. Free status rows are not counted.
FAQ
Do I need an API key? No. The three APIs are public read-only job-board endpoints.
What am I charged for? One event per company row with status = ok. Not-found companies, invalid lines, API errors and unchanged companies skipped by "only changed" are free. The run stops cleanly when your maximum cost per run is reached; companies not delivered keep their previous history, so they show up as changed next time.
How do I find a company's slug? Open its careers page and look at the job links: boards.greenhouse.io/<slug>, jobs.lever.co/<slug> or jobs.ashbyhq.com/<slug>. You can paste that URL as is.
Why is the first run's newRolesSinceLastRun empty? The first run sets the baseline. From the second run on with the same filters and store name you get new and closed counts.
Can I get every job with descriptions? This Actor is a company-level summary. The optional role list has titles, links, location and dates, without descriptions.
Data comes from public job postings published by each company through Greenhouse, Lever or Ashby. Atesen Software is not affiliated with these companies.