# ATS Job Board Change Monitor — Greenhouse, Lever & Ashby (`ol_bozh/ats-board-change-monitor`) Actor

Track new, changed and removed jobs on public Greenhouse, Lever and Ashby boards. Get normalized job data and reusable snapshots. Failed checks preserve previous data. Includes salary details when the source provides them. No LLM API key required.

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

## Pricing

$0.01 / successful board check

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 Board Change Monitor

This Actor checks public Greenhouse, Lever, and Ashby job boards and emits deterministic `new`, `changed`, and `removed` records. It uses stable IDs supplied by each ATS, includes compensation only when the board API supplies it, and does not use an LLM at runtime.

Use it to keep a job directory current, track hiring changes at a company list, or feed a recruitment research workflow. Supply the board handles you want to follow. The Actor does not discover companies or send applications.

### Quick start

Create a baseline with this input:

```json
{"boards":[{"provider":"ashby","slug":"Ashby"}],"baseline":true}
```

Open the run's key-value store and retrieve `SNAPSHOT`. On the next run, use the same `boards`, omit `baseline`, and put that complete object in `priorSnapshot`. The dataset contains a status row for each checked board and its change events; the key-value store contains the normalized current jobs in `SNAPSHOT`.

For a recurring API workflow, save each run's `SNAPSHOT` in your own workflow state and supply it to the next run. The Actor does not automatically retrieve previous runs. You control the polling schedule and the state; no separate language-model API subscription is needed.

The input accepts up to 20 boards. A board is `{ "provider": "greenhouse|lever|ashby", "slug": "board-handle" }`; Lever also accepts `"region": "eu"`. The Actor constructs HTTPS URLs only for the fixed official API hosts. Handles are restricted to simple alphanumeric, underscore, and hyphen characters. Redirects are rejected. Each response is limited to 10 MB, requests time out after 15 seconds, and transient failures receive at most two retries. Lever boards are read in pages of 100, with a 20-page ceiling; a board that reaches this ceiling without a final short page is marked failed. The prior snapshot is capped at 20 MB and the aggregate snapshot and run output are capped at 20 MB and 25 MB respectively.

On the first run, set `baseline` to `true`. The Actor stores the current job state without emitting false `new` events. Copy the `SNAPSHOT` value from that run's key-value store into `priorSnapshot` on the next run. The snapshot travels with the caller's input, so separate users and runs do not share mutable named state. Boards omitted from a later input are left in the snapshot unchanged.

Each successful, valid board fetch produces one `board-check` event, including unchanged or empty boards. Failed fetches and malformed or oversized responses are not charged. A successfully charged board's result is delivered even if that charge reaches the run limit; no further boards are processed. See the Pricing tab for the current price per successful board check.

Removals are generated only after a complete valid jobs list. If a board request, response validation, or charge step fails, its previous job list remains in `SNAPSHOT` and the output contains a board error. This prevents a temporary outage or malformed response from removing every job. A successful empty list is treated as a complete fetch and can produce removal events.

Normalized fields include stable `id` and `source_id`, ATS `source`, title, location, department/team, employment and workplace type, description when provided by the endpoint, published/updated timestamp, job and application URLs, and optional source compensation. Exact field availability varies by ATS. The Actor does not enrich or infer salary, and Greenhouse list responses generally omit pay ranges.

### Sources and limits

- [Greenhouse Job Board API](https://developers.greenhouse.io/job-board.html)
- [Lever Postings API](https://github.com/lever/postings-api)
- [Ashby Public Job Posting API](https://developers.ashbyhq.com/docs/public-job-posting-api)
- [Apify Python SDK pay-per-event guide](https://docs.apify.com/sdk/python/docs/concepts/pay-per-event)

Compensation and descriptions depend on source configuration. A valid empty response can indicate a real closure of all jobs; the Actor cannot independently verify the ATS provider's own data. Very large boards may exceed the documented limits and are reported as errors, preserving their previous successful state.

# Actor input Schema

## `boards` (type: `array`):

Between 1 and 20 board handles. For Lever EU boards, set region to eu.

## `baseline` (type: `boolean`):

Required only when priorSnapshot is omitted. Initial baseline stores jobs without emitting new events.

## `priorSnapshot` (type: `object`):

Paste the SNAPSHOT value from the preceding Actor run to compare with it.

## Actor input object example

```json
{
  "boards": [
    {
      "provider": "ashby",
      "slug": "Ashby"
    }
  ],
  "baseline": true
}
```

# Actor output Schema

## `results` (type: `string`):

Per-board success or error rows and detected job changes.

## `snapshot` (type: `string`):

Pass this record as priorSnapshot to detect changes on the next run.

# 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 = {
    "boards": [
        {
            "provider": "ashby",
            "slug": "Ashby"
        }
    ],
    "baseline": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("ol_bozh/ats-board-change-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 = {
    "boards": [{
            "provider": "ashby",
            "slug": "Ashby",
        }],
    "baseline": True,
}

# Run the Actor and wait for it to finish
run = client.actor("ol_bozh/ats-board-change-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 '{
  "boards": [
    {
      "provider": "ashby",
      "slug": "Ashby"
    }
  ],
  "baseline": true
}' |
apify call ol_bozh/ats-board-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ol_bozh/ats-board-change-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/wyDdl9XaRgu6F3drs/builds/ouP8gmUKawKeTRRcu/openapi.json