Guide / Company data
Hiring signals from the Greenhouse, Lever and Ashby job-board APIs
Greenhouse, Lever and Ashby publish every company's open roles as a free, public feed, with no sign-up. How to read it and spot hiring signals.
When a company starts hiring for a new team, the first public sign is often a new posting on its careers page. That makes the page one of the best buying signals a sales or research agent can watch, and many tech companies run it on one of three hiring systems: Greenhouse, Lever or Ashby.
Each of the three publishes the same listings as a free, public data feed. There is nothing to sign up for and no key to request: your agent asks one web address and gets back every open role with its title, team, location and date.
This guide shows how to find a company's feed, read it, and turn the changes from week to week into a hiring signal. All you need is the company's careers page.
How to read a company's open jobs from its job board
- Find which system runs the careers page: click any role and look at the web address it opens, which names the system (boards.greenhouse.io, jobs.lever.co or jobs.ashbyhq.com).
- Note the company's board name, the part of that address right after the system's domain.
- Fetch the open roles from that system's public address, shown for each one below, with no sign-up.
- Save each role's title, team, location, remote or on-site status, date and link, and keep a dated copy of the whole list.
- On the next run, compare the new list with the last one and flag what changed: a team that wasn't there before, a jump in roles in one function, or a role the company has never posted.
- Pass the flags to whoever owns the account, with the links, so a person reads the roles before acting on them.
The three feeds side by side
The three systems answer the same question in different shapes, per their own documentation:
| Greenhouse | Lever | Ashby | |
|---|---|---|---|
| Board name from | boards.greenhouse.io/{token} | jobs.lever.co/{site} | jobs.ashbyhq.com/{name} |
| Key for reads | None; GET endpoints are public | None; a key only to submit applications | None in the documented request |
| Title | title |
text |
title |
| Team or department | departments (with content=true) |
categories.team, categories.department |
department, team |
| Location | location.name, offices |
categories.location, allLocations, country |
location, secondaryLocations, address |
| Remote or on-site | No documented field; read the location text | workplaceType |
isRemote, workplaceType |
| Date | updated_at; first_published on a single job |
None documented | publishedAt, when last published |
| Paging and filters | None documented on the list; /departments and /offices group roles |
skip, limit, five filters, group |
None documented |
| Pay | pay_input_ranges with pay_transparency=true, single job |
salaryRange, optional |
compensation with includeCompensation=true |
The addresses to fetch are https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true, https://api.lever.co/v0/postings/{site}?mode=json and https://api.ashbyhq.com/posting-api/job-board/{name}.
Details that trip agents up
- The careers page may hide the system. Some companies show Greenhouse postings on their own domain. A
gh_jidin the job link gives Greenhouse away. - Not every posting is a real opening. Greenhouse prospect posts carry a null
internal_job_id, and Ashby marks postings it keeps off the public list withisListed: false. Leave both out. - Team and department aren't the same thing. Lever records both, so decide which one your signal counts.
- Locations come as text. One location can name several cities, so split it yourself.
- Each system dates roles differently. Greenhouse gives
updated_aton the list, Ashby givespublishedAt, and Lever's documentation lists no date.
Example calls
We read Stripe's Greenhouse feed with no key and no parameters, and the first posting it returned carried these fields, in order:
GET https://boards-api.greenhouse.io/v1/boards/stripe/jobs
jobs[0]: absolute_url, data_compliance, education, internal_job_id,
location.name, metadata, id, updated_at, requisition_id, title, …
That posting links to Stripe's own domain rather than boards.greenhouse.io, and its location is a single line naming three cities.
A request to Spotify's Lever feed for three postings returned them. Here is the first, trimmed to the fields a signal uses:
GET https://api.lever.co/v0/postings/spotify?mode=json&limit=3
[
{
"id": "[redacted]",
"text": "Art Director - Mexico",
"categories": {
"commitment": "Permanent",
"department": "Markets and Subscriber Growth",
"location": "Mexico City",
"team": "Marketing",
"allLocations": ["Mexico City"]
},
"country": "MX",
"workplaceType": "hybrid",
"createdAt": 1791566108174,
"hostedUrl": "https://jobs.lever.co/[path]"
},
…
]
Its team is Marketing, inside the Markets and Subscriber Growth department. It also carried a numeric createdAt that Lever's documentation doesn't list; it looks like a timestamp in milliseconds, but treat it as undocumented.
We read Notion's Ashby feed the same way, and its first posting carried these fields:
GET https://api.ashbyhq.com/posting-api/job-board/notion
jobs[0]: id, title, department, team, employmentType, location,
secondaryLocations[].location, secondaryLocations[].address.postalAddress,
publishedAt, isListed, isRemote, …
That posting is marked remote and still names San Francisco, with New York as a second location, so read the flag and the cities together. The whole feed ran to about 2.5 MB, because Ashby returns every open posting with its full description and offers no paging to trim it.
What it costs
Nothing. All three calls were free and answered in under half a second.
| Call | Status | Time | Response size | Cost |
|---|---|---|---|---|
| Stripe on Greenhouse, all jobs | 200 | 0.21 s | about 450 KB | $0 |
| Spotify on Lever, three postings | 200 | 0.46 s | about 29 KB | $0 |
| Notion on Ashby, all jobs | 200 | 0.16 s | about 2.5 MB | $0 |
None of the three documents a rate limit for reading jobs. Once a day per company is plenty for a hiring signal.
When this is the wrong tool
Postings can mislead: some roles never close, a repost can look like a new opening, and a pipeline post can stand in for a job that doesn't exist yet. That is why this method watches what changes between snapshots, not how many roles are open. A posting shows that a company published a role, not that it will fill it.
Reach for something else when:
- The company uses none of the three. Its own hiring system may publish a feed of its own; if not, you'll need another source for that company's roles.
- You need history. The feeds show what is open now, and closed roles vanish, so your saved snapshots are the only history you'll have. Start them on day one.
- You need to search across companies. Each call reads one company's board, and Lever says plainly that its API has no full-text search.
- You need internal roles. Lever, for one, keeps everything that isn't published out of its feed.
Pick ten target accounts, find their boards today and save the first snapshot. Compare next week, and the first new team to appear is your reason to call.
Frequently asked questions
Do the Greenhouse, Lever and Ashby job board APIs need an API key?
Not for reading jobs. Greenhouse requires no authentication for GET endpoints, Lever asks for a key only to submit applications, and Ashby's documented request carries none.
How do I find a company's Greenhouse board token?
It is the path segment after boards.greenhouse.io in a job link, such as vaulttec in Greenhouse's own example. If the company hosts postings on its own domain, look for a gh_jid parameter in the link and try the company name as the token.
Does the Lever postings API support pagination and filters?
Yes. Use skip and limit to page, filter by location, commitment, team, department or level, and use group=team to get postings grouped by team.
Can I get salary ranges from these APIs?
Where the company publishes them. Greenhouse returns pay_input_ranges on a single job with pay_transparency=true, Lever includes an optional salaryRange, and Ashby adds compensation with includeCompensation=true.
Are job postings a reliable buying signal?
A single snapshot is weak; a change between snapshots, such as a new team or a first role in a function, shows what a company has started publishing. Treat it as a reason to research the account, not as a forecast.
Read this article as Markdown Open in ChatGPT Open in Claude


