Greenhouse, Lever, Ashby & Workable Job Board API avatar

Greenhouse, Lever, Ashby & Workable Job Board API

Pricing

from $1.70 / 1,000 results

Go to Apify Store
Greenhouse, Lever, Ashby & Workable Job Board API

Greenhouse, Lever, Ashby & Workable Job Board API

Career site jobs from the Greenhouse, Lever, Ashby and Workable boards you list as vendor:slug, in one table: title, company (board slug where the vendor gives no name), location, department, type, date, snippet, apply link. No login, no key. Turn on Only new jobs for daily runs. No salary field.

Pricing

from $1.70 / 1,000 results

Rating

0.0

(0)

Developer

Plain Build

Plain Build

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

32 minutes ago

Last modified

Features

Limited permissions

Share

What it does

Career site jobs from the Greenhouse, Lever, Ashby and Workable boards you list as vendor:slug, in one table: title, company (board slug where the vendor gives no name), location, department, type, date, snippet, apply link. No login, no key. Turn on Only new jobs for daily runs. No salary field.

The data comes from Greenhouse, Lever, Ashby and Workable through their public JSON endpoints (https://boards-api.greenhouse.io). This Actor is not affiliated with, endorsed by or sponsored by Greenhouse, Lever, Ashby and Workable. It reads only those endpoints, at most 4 requests at a time, and it checks robots.txt before the first request to each host.

Who it is for

  • Recruiting-tech teams and job aggregators filling a job board from the source boards of named companies
  • Sales and growth people who sell to companies while they hire and want a daily list of new roles per account (Only new jobs on)
  • Analysts following which companies open which roles, exported to CSV or Excel
  • Developers who want one schema for Greenhouse, Lever, Ashby and Workable instead of four parsers
  • Anyone with a list of Workable boards who needs them in the same table as Greenhouse, Lever and Ashby

How it works

You give a list of boards as vendor:slug, for example greenhouse:gitlab. For each board the Actor reads the vendor's public job-board JSON: one request for Greenhouse, Lever and Ashby, page by page for Workable. Each job is mapped to the same fields, its description is cut to a short snippet, and contact details are removed from the text. A keyword keeps only jobs whose title contains it; posted_after keeps only newer jobs. When max_items is lower than the jobs found, the boards share it equally. Text fields are trimmed. Where Greenhouse gives a placeholder such as N/A as the location, the job's offices are used; where it gives only a workplace type such as Hybrid, the offices follow in brackets. A board where the filters keep nothing gives an uncharged no_results item. A board that does not exist becomes an uncharged error item, and the other boards still deliver; a run where no board exists fails.

How to try it

  1. Open the Input tab. The prefilled input returns 25 jobs shared between five known boards.
  2. Click Start. A run usually finishes in under a minute.
  3. Open the Output tab to see the results as a table, or export them as JSON, CSV or Excel.

To get new jobs the same day, schedule a daily run with new_since_last_run on. Each run then delivers and charges only jobs you have not had from this Actor. max_items and your spending limit keep the newest jobs; older ones come in the next run.

  • With several boards, max_items and your spending limit are shared: each board gets its newest job, then its next, in turn. The jobs appear when the last board has answered. A run you abort before that delivers and charges nothing; a run near its timeout stops fetching and delivers what it has. With new_since_last_run on, the newest jobs of all boards come first instead.
  • A board that no longer exists becomes an uncharged error item, and the other boards still run. When none of your boards exists, the run fails, so a scheduled run with a misspelt or deleted board shows as failed.
  • A board where keyword and posted_after keep no job, or that has no open job, gives one uncharged no_results item, so you can tell a wrong keyword from a quiet board.
  • Turn the option off to get every open job. Once you have used the option, a run with it off is remembered too.
  • The memory is a key-value store named ats-job-boards-scraper-state in your account. Delete it to start again. It is one memory for all your boards and holds the newest 50,000 delivered jobs; a job older than that can come, and be charged, again if its board still lists it.
  • Two runs at the same time can deliver and charge the same job, so leave a gap between scheduled runs.

Lever, Ashby and Workable give no company name, so company is the board's slug there. Workable's list has no job text, so description_snippet is empty there. Greenhouse publishes no employment type, so employment_type is empty there. posted_at is the date each vendor gives: when Greenhouse first published the job, when Lever created the posting (it can be years old), when Ashby published it, and only the day for Workable.

How much it costs

You pay per result delivered to the default dataset. Errors and empty results are written to a separate errors dataset and are never charged.

Plan tierPrice per 1,000 results
Free and BronzeUSD 2.00
Silver and aboveUSD 1.70

Example: a run that delivers 1,000 results costs USD 2.00 on the Free and Bronze tiers and USD 1.70 on Silver and above, plus the platform's start event of USD 0.00005. If you set a maximum cost per run, the Actor stops before it would go over it and delivers nothing it cannot charge for.

Input

FieldTypeDefaultDescription
boardsarrayundefinedOne board per line as vendor:slug, where the vendor is greenhouse, lever, ashby or workable. The slug is in the board's address, for example greenhouse:gitlab. Up to 500 entries per run, counted before duplicates are removed. Maximum results is shared by all boards; the default is 10, so raise it for a long list.
keywordstring""Keep only jobs whose title contains this text, in any case and anywhere in the title, so engineer also keeps Engineering Manager. A phrase is matched as one piece of text; it is not a regular expression. It filters the boards you list; it does not search all boards. Leave empty for every job.
posted_afterstring""Date as YYYY-MM-DD, compared with posted_at in UTC. Lever gives the date a posting was created, which can be years ago for a job still open, so this keeps fewer Lever jobs than you may expect. Leave empty for every open job.
new_since_last_runbooleanfalseDeliver and charge only jobs this Actor has not delivered to you before. A job held back by Maximum results or your spending limit comes in the next run. Delivered jobs are remembered in a key-value store named ats-job-boards-scraper-state in your account.
max_itemsinteger10How many results to return at most, from 1 to 10000.

Output

Each result has these fields. Missing values are null, never a different type.

FieldTypeDescription
item_typestringAlways job_post
source_idstringThe vendor's job id with the vendor in front, for example greenhouse:8638232002
companystringCompany name, or the board's slug where the vendor gives no name
titlestringJob title
locationstring or nullLocation as the vendor gives it. A Greenhouse placeholder (N/A, LOCATION, TBD) or missing location becomes the job's offices; a Greenhouse workplace type alone (Hybrid, Distributed, In-Office, Onsite) gets the offices in brackets, for example Hybrid (Austin, TX; New York, NY). Anything with Remote stays as given.
departmentstring or nullDepartment as published
employment_typestring or nullAs the vendor writes it: FullTime or Intern (Ashby), Permanent, Full-time or Internship (Lever), full (Workable). Greenhouse publishes none, so it is empty there.
posted_atstring or nullISO 8601 UTC. Greenhouse: first published (last updated when it gives no first date). Lever: when the posting was created, which can be years ago. Ashby: published. Workable: the publish day only, at 00:00 UTC.
description_snippetstring or nullThe first 300 characters of the job text
apply_urlstringThe job on the vendor's board
ats_vendorstringgreenhouse, lever, ashby or workable
board_slugstringThe board's slug
source_urlstringThe record on the source site
fetched_atstringWhen the record was fetched, ISO 8601 UTC
actor_versionstringThe build that produced the record

Example item:

{
"item_type": "job_post",
"source_id": "<source_id>",
"company": "<company>",
"title": "<title>",
"location": "<location>",
"department": "<department>",
"employment_type": "<employment_type>",
"posted_at": "<posted_at>",
"description_snippet": "<description_snippet>",
"apply_url": "<apply_url>",
"ats_vendor": "<ats_vendor>",
"board_slug": "<board_slug>",
"source_url": "<source_url>",
"fetched_at": "2026-11-04T09:30:00Z",
"actor_version": "0.4.1"
}

Free-text fields are cleaned before delivery: email addresses, phone numbers, @handles and person names introduced by words such as "contact", "recruiter", "founder" or "manager" are replaced with [removed]. The cleaning follows fixed rules, so a name written elsewhere in the text, or in lower case, can remain.

Other Actors in this family

This Actor is part of a family of job and public-data scrapers built on the same core: one result per charge, a separate uncharged errors dataset, and no personal data. Links follow as the other Actors are published.

FAQ and support

  • Is there personal data in the output? No personal data by design: the output holds only facts about jobs and companies, never the author of a post, and contact details are removed from the text as described under Output.
  • Is the data accurate? Accuracy is not guaranteed. The data is parsed from free text written by many people, and fields can be missing or wrong.
  • Who runs this Actor? It is not affiliated with Greenhouse, Lever, Ashby and Workable.
  • What may I do with the data? You are responsible for complying with the law and with the source's terms when you use the data.
  • How is the data collected? The official API or open data is used where the source offers it. This Actor uses only the public JSON endpoints of Greenhouse, Lever, Ashby and Workable.
  • Something is broken. Open an issue on the Issues tab with the run link and your input. Issues are answered by the automated maintainer.