ATS Jobs Feed: Greenhouse, Lever & Ashby Jobs API avatar

ATS Jobs Feed: Greenhouse, Lever & Ashby Jobs API

Pricing

from $1.00 / 1,000 job results

Go to Apify Store
ATS Jobs Feed: Greenhouse, Lever & Ashby Jobs API

ATS Jobs Feed: Greenhouse, Lever & Ashby Jobs API

Live job postings from company career boards on Greenhouse, Lever and Ashby via their official public job-board APIs. Paste slugs or careers URLs, ATS auto-detected. Filter by keyword, location, remote; get only new jobs since your last run.

Pricing

from $1.00 / 1,000 job results

Rating

0.0

(0)

Developer

Tobby Tools

Tobby Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Security

Limited permissions

Share

Get live job postings straight from company career boards hosted on Greenhouse, Lever and Ashby, normalized into one clean schema. Paste board slugs or careers URLs; the Actor detects the ATS, reads the board, filters by keyword, location or remote, and can return only the jobs that are new since your last run.

Data comes from the official public job-board APIs each ATS publishes for careers pages:

ATSEndpoint usedDocs
Greenhouseboards-api.greenhouse.io/v1/boards/{slug}/jobs?content=trueJob Board API
Leverapi.lever.co/v0/postings/{slug}?mode=json (EU: api.eu.lever.co)Postings API
Ashbyapi.ashbyhq.com/posting-api/job-board/{slug}?includeCompensation=trueJob Postings API

No login, no browser, no proxies, no HTML scraping. Each request returns what the company already publishes for job seekers. The Actor reads boards live at run time; it is not a cached database.

What you can do with it

  • Job alerts / monitoring: schedule it daily with Only new jobs since my last run and get just the fresh postings from your target companies.
  • Job board backfill: pull every open role from a list of employers into your site or spreadsheet.
  • Hiring signals for sales and recruiting: see which companies are hiring for which teams and locations.
  • Market research: track openings, departments and locations across competitors.

Input

FieldWhat it does
companies (required)Board slugs or careers URLs, one per line. See below.
keywordsKeep jobs whose title contains any of these (case-insensitive).
searchDescriptionAlso match keywords inside the description.
excludeKeywordsDrop jobs whose title contains any of these.
locationsKeep jobs whose location text contains any of these, e.g. Toronto, Canada, Remote.
remoteOnlyKeep only jobs flagged remote (see Remote flag below).
onlyNewOutput only jobs not seen in your previous run with the same snapshotName.
snapshotNameName of the saved state, so you can run independent monitors.
includeDescriptionInclude description text and HTML (default on).
maxJobsPerCompany, maxResultsLimits. Each output job is one charged result.

Accepted company formats

  • https://boards.greenhouse.io/stripe, https://job-boards.greenhouse.io/stripe
  • https://jobs.lever.co/palantir, https://jobs.eu.lever.co/<slug>
  • https://jobs.ashbyhq.com/ramp
  • Plain slugs: stripe. The Actor checks Greenhouse, Lever and Ashby (and Lever EU if none match). If the same slug exists on more than one ATS, it uses the board with the most jobs and notes the others in the run summary.
  • Forced platform: greenhouse:stripe, lever:palantir, lever-eu:<slug>, ashby:ramp.

Custom-domain careers pages (e.g. company.com/careers) are not auto-detected. Open one job on the page and look for the Greenhouse, Lever or Ashby URL or slug.

Example input

{
"companies": ["https://boards.greenhouse.io/stripe", "https://jobs.lever.co/palantir", "ashby:linear"],
"keywords": ["engineer"],
"locations": ["London", "Remote"],
"onlyNew": true,
"snapshotName": "eng-london"
}

Output

One row per job:

{
"company": "Stripe",
"companySlug": "stripe",
"sourceAts": "greenhouse",
"jobId": "8172503",
"title": "Abuse Research Engineer",
"location": "Remote from the US",
"allLocations": ["Remote from the US", "US"],
"remote": true,
"workplaceType": null,
"department": "8611 Security Analytics",
"team": null,
"employmentType": null,
"salary": null,
"postedAt": "2026-09-09T14:52:09.000Z",
"updatedAt": "2026-10-29T14:42:09.000Z",
"jobUrl": "https://stripe.com/jobs/search?gh_jid=8172503",
"applyUrl": "https://stripe.com/jobs/search?gh_jid=8172503",
"descriptionText": "Who we are\n\nAbout Stripe\n\n...",
"descriptionHtml": "<h2>Who we are</h2>...",
"boardUrl": "https://boards.greenhouse.io/stripe",
"fetchedAt": "2026-11-03T21:11:31.138Z"
}

How fields map per ATS

Fields are only as complete as each ATS's public API. Missing data is null; nothing is guessed.

FieldGreenhouseLeverAshby
companycompany_nameboard slug (the API has no company name)board slug (the API has no company name)
postedAtfirst_publishedcreatedAtpublishedAt (last published)
updatedAtupdated_atnullnull
department / teamfirst department / nulldepartment / teamdepartment / team
employmentTypenull (not in the API)commitment (e.g. Full-time)employmentType (e.g. FullTime)
workplaceTypenullworkplaceTypeworkplaceType
salarynullnullcompensation summary when the employer publishes it
descriptionHtmlcontent (HTML-unescaped)description + lists + additionaldescriptionHtml

Remote flag: Lever and Ashby use the board's workplace type (remote: true only for fully remote; hybrid is false). Greenhouse has no remote field, so a Greenhouse job counts as remote when its location or office text says Remote or Anywhere; otherwise remote is null.

Ashby jobs marked unlisted (isListed: false) are skipped.

Only new jobs since last run

With onlyNew on, the Actor saves the job IDs it saw per board in your named key-value store ats-jobs-feed-state (key snapshot-<snapshotName>). The first run for each board only saves a baseline and outputs nothing for it (so it costs only the start event). Later runs output jobs whose ID was not on the board last time. Schedule the Actor (for example daily) to get a new-jobs feed. Note that a job that is taken down and reposted with a new ID by the employer counts as new.

Reliability

  • One bad slug or a temporary error on one board never fails the run. Each company gets a status (ok, not_found, error, duplicate) in the run summary (key-value store record SUMMARY), with the detected ATS and counts.
  • Retries with backoff on rate limits (429) and server errors; Lever pages are read with a 1-second pause, as Lever's robots.txt asks.

Pricing

Pay per event:

  • $0.001 per job in the dataset ($1 per 1,000 jobs)
  • $0.00005 per run start

Boards that are not found, jobs removed by your filters and baseline runs are not charged. Use maxResults to cap spend per run.

Notes and fair use

  • This Actor only reads published postings from public, unauthenticated endpoints that the ATS vendors document for careers pages. It does not log in, apply to jobs or collect candidate data.
  • Job descriptions belong to the employers. Respect each employer's terms when you republish their postings, and link back via jobUrl/applyUrl.
  • Please don't schedule more often than you need; boards rarely change more than a few times a day.

Questions or a missing ATS? Open an issue on the Actor page.