# ATS Job Monitor: Greenhouse, Lever, Ashby, Recruitee & more (`kislov-data/ats-job-board-monitor`) Actor

Get all open jobs from Greenhouse, Lever, Ashby, Recruitee, Personio and Teamtailor career boards in one clean schema. Paste a company name, job board URL or website. Track new, updated and removed jobs between runs. Official public feeds, no proxies, pay per job.

- **URL**: https://apify.com/kislov-data/ats-job-board-monitor.md
- **Developed by:** [Aleksandr](https://apify.com/kislov-data) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 job record returneds

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 Job Board Monitor: Greenhouse, Lever, Ashby, Recruitee, Personio & Teamtailor jobs in one clean schema

Get every open job from company career boards built on **Greenhouse, Lever, Ashby, Recruitee, Personio and Teamtailor**, normalized into one consistent format. Paste a company name, a job board URL or a company website. Run it on a schedule and get only the **new, updated and removed** jobs since last time.

It uses the **public job board APIs and feeds that these vendors publish for career sites** (no login, no browser, no proxies), so runs are fast, cheap and stable.

### What you can do with it

- **Recruiting and sourcing:** watch target companies and get alerted when they open roles that match your keywords.
- **Competitor and market intelligence:** track hiring volume, departments and locations over time.
- **Job boards and aggregators:** feed fresh, deduplicated listings into your own site.
- **Sales triggers:** a company hiring for a role is often a buying signal. Monitor hiring and reach out at the right moment.
- **Compensation research:** collect salary ranges where employers publish them (pay transparency).

### Why this Actor

- **One schema for six systems.** Title, department, team, employment type, locations, remote/hybrid/onsite, publish date, salary range (min, max, currency, interval), job URL, apply URL, description.
- **Change tracking built in.** Turn on `trackChanges` and every job gets `changeStatus`: `new`, `updated` or `unchanged`. Turn on `onlyChanges` to return just what changed, and `includeRemoved` to also get jobs that were taken down.
- **Flexible input.** Use a board name (`airbnb`), a board URL (`https://jobs.lever.co/spotify`) or a company website (`notion.so`). For websites the Actor looks for a link to a supported system on the careers page and, if it finds none, tries the brand name as a board name. Guessed boards are marked `detectedBy: "guess"` in the `SUMMARY` record so you can check them.
- **Filters.** Keywords, excluded keywords, location, remote only, posted within N days, max jobs per company.
- **Cheap and predictable.** Pay per job record returned. No start fee.

### Input

```json
{
  "companies": ["airbnb", "https://jobs.lever.co/spotify", "notion.so"],
  "keywords": ["engineer", "data"],
  "remoteOnly": false,
  "postedWithinDays": 30,
  "trackChanges": true,
  "onlyChanges": true,
  "includeRemoved": true
}
```

| Field | What it does |
|---|---|
| `companies` | Board names, board URLs or company websites. |
| `ats` | `auto` (default), `greenhouse`, `lever`, `ashby`, `recruitee`, `personio` or `teamtailor`. |
| `keywords` / `excludeKeywords` | Match against title, department and team. |
| `locationContains` | Keep jobs whose location contains one of the words. |
| `remoteOnly` | Keep only remote jobs. |
| `postedWithinDays` | Keep only recently published jobs. |
| `maxJobsPerCompany` | Newest first. 0 means no limit. |
| `trackChanges`, `onlyChanges`, `includeRemoved` | Change tracking between runs. |
| `stateName` | Name of the key-value store that remembers the last run. Use different names for different watch lists. |
| `includeDescription`, `includeHtml` | Description as plain text and/or HTML. |

The first run with change tracking marks every job as `new`. Later runs compare against it.

### Rank jobs against your resume (new)

Paste your skills or resume text into **Your profile** and the Actor sorts every job from all boards by relevance. Each job gets `relevanceScore` (100 = best match in this run) and `matchedTerms` (the words and phrases that matched, for example `curtain wall`). Use **Minimum relevance score** to drop weak matches.

How it works: plain tf-idf scoring over words and two-word phrases, with the job title counted three times and department/team twice. There is no external AI service, nothing is sent anywhere, and your text is used only during the run. Scores are relative to the jobs found in that run, so add more companies to widen the comparison. Combine it with *Track changes* and *Return only new and updated jobs* to get a short, ranked list of fresh matches every week.

### Output

```json
{
  "id": "greenhouse:airbnb:8245428",
  "ats": "greenhouse",
  "companySlug": "airbnb",
  "company": "Airbnb",
  "jobId": "8245428",
  "title": "Software Engineer, Guest & Host",
  "department": "Software Engineering",
  "location": "Bangalore, India",
  "locations": ["India", "Bangalore, India"],
  "workplaceType": "remote",
  "isRemote": true,
  "postedAt": "2026-10-06T00:20:52-04:00",
  "jobUrl": "https://careers.airbnb.com/positions/8245428",
  "salaryMin": 3050000,
  "salaryMax": 4350000,
  "salaryCurrency": "INR",
  "salaryInterval": "year",
  "descriptionText": "…",
  "changeStatus": "new",
  "firstSeenAt": "2026-10-06T06:03:49+00:00"
}
```

A `SUMMARY` record in the default key-value store lists, for every input, which boards were found, how many jobs each has, and what was not found.

### Pricing

Pay per event: **$1.20 per 1,000 job records** returned (new, updated, unchanged or removed). You are not charged for boards that do not exist or for jobs removed by your filters.

### Tips

- To find a board name, open the company careers page: the address looks like `boards.greenhouse.io/<name>`, `jobs.lever.co/<name>`, `jobs.ashbyhq.com/<name>`, `<name>.recruitee.com`, `<name>.jobs.personio.de` or `<name>.teamtailor.com`.
- Use `maxJobsPerCompany` while testing.
- Schedule the Actor (hourly, daily, weekly) with `onlyChanges` on, then connect the dataset to Slack, Google Sheets, Make, Zapier or a webhook.
- Large boards can have thousands of jobs. Turn off `includeDescription` if you only need titles and links.

### Limits

- Supports companies that publish jobs through **Greenhouse, Lever, Ashby, Recruitee, Personio or Teamtailor**. Other systems (Workday, SmartRecruiters, Workable and so on) are not supported yet; tell us which one you need.
- Personio and Teamtailor feeds do not include salary data; Recruitee, Greenhouse, Lever and Ashby include it when the employer publishes it.
- Only jobs the employer has published publicly are returned.
- Guessed boards (`detectedBy: "guess"`) can belong to a different company with a similar name. Check the `company` and `jobUrl` fields.
- Some Lever and Ashby boards do not expose a company display name, so `company` falls back to the board name.

### Responsible use

The Actor reads the career-board endpoints that the vendors document for public use and does not log in or bypass anything. You are responsible for how you use the data and for following the terms of the vendors and the laws that apply to you. The Actor does not collect personal data about candidates or employees.

### Feedback

Found a board that does not work or want another field? Open an issue from the Actor page and include the input you used.

# Actor input Schema

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

One entry per company. Accepted formats: a board name such as <code>airbnb</code>, a job board URL such as <code>https://jobs.lever.co/spotify</code>, or a company website such as <code>notion.so</code>. For websites the Actor looks for a Greenhouse, Lever or Ashby link on the careers page and, if none is found, tries the brand name as a board name (see SUMMARY in the key-value store).

## `ats` (type: `string`):

Leave on Auto to try all supported systems (Greenhouse, Lever, Ashby, Recruitee, Personio, Teamtailor). Choose one system to speed up runs when you know where the companies hire.

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

Keep only jobs whose title, department or team contains at least one of these words (case-insensitive). Example: <code>engineer</code>, <code>data</code>.

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

Skip jobs whose title, department or team contains any of these words. Example: <code>intern</code>.

## `profile` (type: `string`):

Optional. Paste your skills, target roles or the text of your resume (up to 30,000 characters). The Actor ranks all returned jobs by how well their title, team and description match it and adds <code>relevanceScore</code> (100 = best match in this run) and <code>matchedTerms</code>. The text is used only for scoring during the run and is not stored or sent anywhere.

## `minRelevance` (type: `integer`):

Used with the profile: drop jobs whose relevanceScore is below this value (0-100). 0 keeps everything, sorted from best to worst match.

## `locationContains` (type: `array`):

Keep only jobs with a location containing at least one of these words. Example: <code>London</code>, <code>Germany</code>.

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

Keep only jobs the employer marks as remote.

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

Keep only jobs published in the last N days. 0 means no limit. Jobs without a publication date are kept.

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

Limit the number of jobs returned for each company (newest first). 0 means no limit.

## `trackChanges` (type: `boolean`):

Adds a <code>changeStatus</code> field (new, updated or unchanged) and remembers every board between runs. The first run marks every job as new.

## `onlyChanges` (type: `boolean`):

After the first run, return only jobs that are new or changed since the previous run. Turns on change tracking automatically.

## `includeRemoved` (type: `boolean`):

With change tracking, also return a short record (<code>changeStatus: removed</code>) for jobs that disappeared since the previous run.

## `stateName` (type: `string`):

Name of the key-value store that keeps the last seen jobs. Use different names for separate watch lists.

## `includeDescription` (type: `boolean`):

Add the full job description as plain text.

## `includeHtml` (type: `boolean`):

Also add the description as HTML.

## `concurrency` (type: `integer`):

How many job boards to load at the same time.

## Actor input object example

```json
{
  "companies": [
    "airbnb",
    "spotify",
    "notion"
  ],
  "ats": "auto",
  "minRelevance": 0,
  "remoteOnly": false,
  "postedWithinDays": 0,
  "maxJobsPerCompany": 10,
  "trackChanges": false,
  "onlyChanges": false,
  "includeRemoved": false,
  "stateName": "ats-jobs-state",
  "includeDescription": true,
  "includeHtml": false,
  "concurrency": 4
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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": [
        "airbnb",
        "spotify",
        "notion"
    ],
    "maxJobsPerCompany": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("kislov-data/ats-job-board-monitor").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": [
        "airbnb",
        "spotify",
        "notion",
    ],
    "maxJobsPerCompany": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("kislov-data/ats-job-board-monitor").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": [
    "airbnb",
    "spotify",
    "notion"
  ],
  "maxJobsPerCompany": 10
}' |
apify call kislov-data/ats-job-board-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kislov-data/ats-job-board-monitor"
        }
    }
}
```

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/zNWoaaJOiu2mQrz4q/builds/SuxnDfR9dj9CQpRwa/openapi.json