# ATS Jobs: Greenhouse, Lever & Ashby Job Boards (`agentready/greenhouse-lever-ashby-jobs`) Actor

Get every open job from any company's Greenhouse, Lever or Ashby careers page in one clean, identical format. Filter by keyword, location, remote and date, or return only jobs that are new since your last run. Official public APIs only.

- **URL**: https://apify.com/agentready/greenhouse-lever-ashby-jobs.md
- **Developed by:** [agentready](https://apify.com/agentready) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## ATS Jobs: Greenhouse, Lever & Ashby Job Boards

Get every open job from any company's **Greenhouse**, **Lever** or **Ashby** careers page in **one identical, clean format**. Mix all three in one run, filter by keyword, location, remote or date, and turn on **"only new jobs"** to get just the postings that appeared since your last run.

It reads only the official public job-board APIs these systems provide for publishing jobs. No logins, no browser, no blocked pages, so runs are fast and cheap and rarely break.

### What you can do with it

- **Track hiring at target accounts.** New roles in a team are a strong buying signal for sales.
- **Feed a job board or newsletter** with fresh postings from hundreds of companies.
- **Give an AI agent live answers** to "who is hiring senior Rust engineers in Berlin?" or "what does Notion pay product designers?"
- **Monitor competitors' hiring**, including department, location and published pay ranges.

### Quick start

Paste careers pages, `ats:board` names, or plain board names:

```json
{
  "companies": [
    "https://boards.greenhouse.io/gitlab",
    "https://jobs.lever.co/leverdemo",
    "ashby:notion",
    "stripe"
  ],
  "keywords": ["engineer", "AI"],
  "remoteOnly": true
}
```

A plain name such as `stripe` is looked up on Greenhouse, then Lever, then Ashby.

#### Daily "new jobs only" feed

Schedule this to run every morning. The first run returns everything that matches; after that, each run returns only jobs you haven't received yet, and **you only pay for those new jobs**.

```json
{
  "companies": ["ashby:openai", "greenhouse:anthropic", "lever:spotify"],
  "keywords": ["machine learning", "research"],
  "onlyNewJobs": true,
  "stateKey": "ml-roles"
}
```

Use a different `stateKey` for each separate search you schedule.

### Input

| Field | What it does |
| --- | --- |
| `companies` (required) | Careers URLs, `greenhouse:x`, `lever:x`, `ashby:x`, or plain board names. Up to 500. |
| `keywords` | Keep jobs whose **title** contains any of these, matched as whole words (`AI` does not match "maintain"). |
| `excludeKeywords` | Drop jobs whose title contains any of these. |
| `searchInDescription` | Also match `keywords` in the job description. |
| `locations` | Keep jobs whose location or country contains any of these (`London`, `Germany`, `Remote`). |
| `remoteOnly` | Keep remote jobs only. |
| `departments` | Keep jobs whose department or team contains any of these. |
| `postedWithinDays` | Keep jobs published in the last N days. |
| `onlyNewJobs` / `stateKey` | Output only jobs not returned in earlier runs under the same key. |
| `descriptionFormat` | `text` (default), `html`, `both`, or `none`. |
| `maxJobsPerCompany`, `maxResults` | Caps. `0` means no limit. |

### Output

Every job has the same fields, whatever system it came from. Missing values are `null`, never guessed.

```json
{
  "id": "ashby:ashby:7458d4e9-da2e-47bd-98cb-adfda43d42b2",
  "ats": "ashby",
  "companySlug": "ashby",
  "companyName": "Ashby",
  "jobId": "7458d4e9-da2e-47bd-98cb-adfda43d42b2",
  "title": "Engineering Manager - EU",
  "department": "Engineering",
  "team": "EMEA Engineering",
  "locations": ["Remote - European Union", "Spain", "Germany"],
  "country": "European Union",
  "workplaceType": "remote",
  "isRemote": true,
  "employmentType": "FullTime",
  "salary": { "min": 110000, "max": 185000, "currency": "EUR", "interval": "year", "summary": "€110K - €185K" },
  "postedAt": "2024-03-04T14:29:08Z",
  "updatedAt": null,
  "url": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2",
  "applyUrl": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2/application",
  "description": "Hi, I am the Director of Engineering, Europe. ...",
  "descriptionHtml": null,
  "scrapedAt": "2026-09-28T12:00:00Z"
}
```

- `id` is stable across runs. Use it to de-duplicate.
- `salary` appears when the company publishes pay (common on Lever and Ashby; Greenhouse's public API doesn't include it).
- `workplaceType` is `remote`, `hybrid`, `onsite` or `null`. Greenhouse has no remote field, so it is read from the location text there.
- Dates are ISO 8601 in UTC.

Each run also saves a **`RUN_SUMMARY`** record in the key-value store. It lists every company you asked for with its status (`ok`, `not_found`, `error`), jobs on the board, jobs matched and jobs output. A misspelled company never fails the whole run.

### Using it from an AI agent (MCP)

This Actor works as a tool in Claude, Cursor and other MCP clients through [Apify's MCP server](https://mcp.apify.com). The input and output are described field by field, so an agent can call it directly, for example: *"Use ATS Jobs to list remote data engineering roles posted this week at gitlab, notion and openai."*

For agents, `descriptionFormat: "text"` returns clean plain text, and `maxResults` keeps responses small.

### Pricing

You pay **per job returned**, with no monthly fee. Boards that are not found or return no matches cost nothing. Set a **maximum charge** on any run and the Actor stops cleanly when it is reached.

### Finding a company's board name

Open the company's careers page and look at the job links:

- `boards.greenhouse.io/<name>` or `job-boards.greenhouse.io/<name>` → Greenhouse
- `jobs.lever.co/<name>` → Lever
- `jobs.ashbyhq.com/<name>` → Ashby

If a careers site is hosted on the company's own domain, open any job's **Apply** link; it usually lands on one of these.

### Limits and good to know

- Only companies that use Greenhouse, Lever or Ashby are covered. Workday, iCIMS and others are not.
- Only jobs the company has made public are returned. Unlisted and internal postings are not.
- EU-hosted Lever boards (`jobs.eu.lever.co`) are supported automatically.

### Data and legal

This Actor reads the public job-board APIs that Greenhouse, Lever and Ashby provide so that job postings can be displayed publicly. It returns job postings only, not personal data about candidates or employees. You are responsible for how you use the data; follow each company's terms and applicable law.

### Support

Found a problem or want a field added? Open an issue on the Actor's **Issues** tab.

# Actor input Schema

## `companies` (type: `array`):

Job boards to read. Each entry can be a careers-page URL (https://boards.greenhouse.io/gitlab, https://jobs.lever.co/leverdemo, https://jobs.ashbyhq.com/ashby), 'ats:board' (greenhouse:gitlab, lever:leverdemo, ashby:ashby), or just the board name (gitlab), in which case Greenhouse, Lever and Ashby are tried in that order. Up to 500 per run.

## `keywords` (type: `array`):

Keep jobs whose title contains any of these words or phrases (whole words, case-insensitive; 'AI' does not match 'maintain'). Leave empty to keep all jobs.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these words (for example 'intern', 'senior').

## `searchInDescription` (type: `boolean`):

Match 'Keywords' against the full job description as well as the title.

## `locations` (type: `array`):

Keep jobs whose location or country contains any of these (case-insensitive), for example 'London', 'United States', 'Remote'.

## `remoteOnly` (type: `boolean`):

Keep only jobs marked remote. Greenhouse has no remote field, so for Greenhouse this relies on 'Remote' appearing in the location.

## `departments` (type: `array`):

Keep jobs whose department or team contains any of these, for example 'Engineering', 'Sales'.

## `postedWithinDays` (type: `integer`):

Keep jobs first published in the last N days. 0 means any date. Jobs with no publish date are dropped when this is set.

## `onlyNewJobs` (type: `boolean`):

Remember which jobs this account has already received and output only new ones. Ideal for scheduled daily runs; you are only charged for new jobs.

## `stateKey` (type: `string`):

Keeps separate 'already seen' lists for different searches. Use a different name for each scheduled search (letters, numbers, '-' and '\_').

## `descriptionFormat` (type: `string`):

'text' is clean plain text (best for AI agents and spreadsheets), 'html' keeps the original formatting, 'both' returns both, 'none' skips descriptions for smaller output.

## `maxJobsPerCompany` (type: `integer`):

Stop after this many matching jobs from each company. 0 means no limit.

## `maxResults` (type: `integer`):

Stop after this many jobs across all companies. 0 means no limit. You can also cap cost with the run's maximum charge.

## Actor input object example

```json
{
  "companies": [
    "https://boards.greenhouse.io/gitlab",
    "lever:leverdemo",
    "ashby"
  ],
  "searchInDescription": false,
  "remoteOnly": false,
  "postedWithinDays": 0,
  "onlyNewJobs": false,
  "stateKey": "default",
  "descriptionFormat": "text",
  "maxJobsPerCompany": 0,
  "maxResults": 0
}
```

# Actor output Schema

## `jobs` (type: `string`):

Every job returned by this run, one record per job, in the format described on the Actor's page.

## `runSummary` (type: `string`):

Per-company status (ok, not\_found, error) with jobs on board, matched and output.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        "https://boards.greenhouse.io/gitlab",
        "lever:leverdemo",
        "ashby"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("agentready/greenhouse-lever-ashby-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "companies": [
        "https://boards.greenhouse.io/gitlab",
        "lever:leverdemo",
        "ashby",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("agentready/greenhouse-lever-ashby-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companies": [
    "https://boards.greenhouse.io/gitlab",
    "lever:leverdemo",
    "ashby"
  ]
}' |
apify call agentready/greenhouse-lever-ashby-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,agentready/greenhouse-lever-ashby-jobs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zN12W2mfFV2tj9AHS/builds/Dh7OqQFNb4HJ2IJ1D/openapi.json