# ATS Hiring Signal Monitor (`lainmar/ats-hiring-signal-monitor`) Actor

Track hiring changes across Greenhouse, Lever and Ashby. Monitor career boards on a schedule and receive structured events when jobs are added, changed, reopened or closed.

- **URL**: https://apify.com/lainmar/ats-hiring-signal-monitor.md
- **Developed by:** [Martin Lain](https://apify.com/lainmar) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 board snapshots

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 Hiring Signal Monitor

**Track hiring changes across Greenhouse, Lever and Ashby.**\
Monitor company career boards on a schedule and receive structured events when jobs are **added**, **changed**, **reopened**, or **closed**.

### Why teams pay for this

- **Sales intelligence** — trigger outreach when a target company opens relevant roles
- **Company growth signals** — watch headcount and department expansion over time
- **Recruiting intelligence** — track competitor or client boards without manual checks
- **Investment / research monitoring** — structured hiring deltas for diligence and market maps
- **AI-agent workflows** — typed JSON events (`job_added`, `job_changed`, …) for webhooks, MCP, and automations

Built as a **job change monitor** / **hiring signals API** / **career page monitor** over official public ATS career-page JSON — not another full board dump scraper.

### Supported boards

| ATS | Source |
| --- | --- |
| Greenhouse | Public Job Board API |
| Lever | Public postings JSON |
| Ashby | Public posting-api job board |

No login. No LinkedIn. No residential proxy required for these public boards.

### Outputs

| `recordType` | Meaning |
| --- | --- |
| `snapshot` | Normalized open jobs (optional) |
| `change_event` | Deltas after the first baseline run |
| `hiring_signal` | Per-board open-count / department summary (optional) |

#### Change events

| `eventType` | When |
| --- | --- |
| `job_added` | New job appears after baseline |
| `job_changed` | Monitored fields / content hash changed |
| `job_reopened` | Previously closed job returns |
| `job_closed` | Missing for N consecutive *successful* fetches |

Stable id: `jobKey = ats:boardToken:externalId`\
**Confirmed-closed:** missing once is not enough — uses `confirmedClosedAfterRuns` (default `2`). Failed board fetches do **not** close jobs.

### How to use

1. Add one or more boards (`boardToken` and/or careers `boardUrl`; `ats: auto` works for common hosts).
2. Set a durable **`kvStoreName`** (same name on every scheduled run).
3. First successful run = **baseline** (snapshots / signals only — no change events).
4. Later runs emit `change_event` rows when jobs appear, change, reopen, or confirm-close.
5. Schedule hourly/daily and wire the dataset to webhooks, Make/Zapier, or your agent pipeline.

### Example input

```json
{
  "boards": [
    { "ats": "greenhouse", "boardToken": "airbnb", "label": "Airbnb" },
    { "ats": "lever", "boardToken": "leverdemo", "label": "Lever Demo" },
    { "ats": "ashby", "boardToken": "ashby", "label": "Ashby" },
    { "ats": "auto", "boardUrl": "https://jobs.lever.co/netflix" }
  ],
  "kvStoreName": "gtm-hiring-signals",
  "confirmedClosedAfterRuns": 2,
  "keywordFilter": "engineer",
  "emitSnapshots": false,
  "emitHiringSignal": true
}
```

#### Main input fields

| Field | Description |
| --- | --- |
| `boards[]` | `ats` (`auto` / `greenhouse` / `lever` / `ashby`), `boardToken`, `boardUrl`, `label` |
| `kvStoreName` | Named KV store for fingerprints across runs |
| `confirmedClosedAfterRuns` | Missing streak before `job_closed` (default `2`) |
| `departmentFilter` / `locationFilter` / `keywordFilter` | Optional contains filters |
| `emitSnapshots` / `emitHiringSignal` | Toggle snapshot rows and hiring summaries |
| `maxJobsPerBoard` | Safety cap (default `5000`) |

### Example outputs

**`change_event`**

```json
{
  "recordType": "change_event",
  "eventType": "job_added",
  "ats": "greenhouse",
  "boardToken": "airbnb",
  "jobKey": "greenhouse:airbnb:8184174",
  "title": "Account Manager",
  "after": {
    "title": "Account Manager",
    "department": "Sales",
    "location": "London, United Kingdom",
    "absoluteUrl": "https://careers.airbnb.com/positions/8184174?gh_jid=8184174",
    "employmentType": null,
    "isRemote": null
  }
}
```

**`hiring_signal`**

```json
{
  "recordType": "hiring_signal",
  "ats": "ashby",
  "boardToken": "ashby",
  "openJobs": 25,
  "openJobsDelta": 0,
  "added": 0,
  "changed": 0,
  "closed": 0,
  "reopened": 0,
  "departmentsHiring": ["Engineering", "Sales"],
  "isBaseline": false
}
```

### Pricing (pay per event)

| Event | When charged | Price |
| --- | --- | --- |
| `board_snapshot` | Each successful board fetch + normalize | **$0.01** |
| `change_event` | Each emitted change row | **$0.02** |
| `signal_report` | Each `hiring_signal` summary row | **$0.01** |

Example: 10 boards daily with ~5 real changes → about `10×$0.01 + 5×$0.02 + 10×$0.01 ≈ $0.30/day` (plus platform start events if applicable).

### Limitations

- Workday and HTML-only career sites are out of scope for this version.
- Custom career domains need explicit `ats` + `boardToken` when auto-detect cannot infer the ATS.
- If `maxJobsPerBoard` truncates a large board, close detection can be skewed — prefer filters or a higher cap.
- Filters define the monitored universe (filtered-out jobs are treated as absent from the board view).

# Actor input Schema

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

One or more ATS boards (token and/or career URL).

## `kvStoreName` (type: `string`):

Named key-value store that persists fingerprints across scheduled runs. Use the same name on every scheduled run.

## `confirmedClosedAfterRuns` (type: `integer`):

Job missing from this many consecutive successful fetches becomes job\_closed.

## `emitSnapshots` (type: `boolean`):

When true, push normalized open-job snapshot rows to the dataset.

## `emitHiringSignal` (type: `boolean`):

When true, push a per-board hiring\_signal summary row.

## `departmentFilter` (type: `string`):

Case-insensitive substring filter on department.

## `locationFilter` (type: `string`):

Case-insensitive substring filter on location.

## `keywordFilter` (type: `string`):

Case-insensitive substring filter across title, department, and location.

## `maxJobsPerBoard` (type: `integer`):

Safety cap on jobs retained per board after filters.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Official Greenhouse/Lever/Ashby JSON endpoints normally need no residential proxy.

## Actor input object example

```json
{
  "boards": [
    {
      "ats": "greenhouse",
      "boardToken": "airbnb",
      "label": "Airbnb"
    },
    {
      "ats": "lever",
      "boardToken": "leverdemo",
      "label": "Lever Demo"
    },
    {
      "ats": "ashby",
      "boardToken": "ashby",
      "label": "Ashby"
    }
  ],
  "kvStoreName": "ats-hiring-signal-monitor-state",
  "confirmedClosedAfterRuns": 2,
  "emitSnapshots": true,
  "emitHiringSignal": true,
  "maxJobsPerBoard": 5000
}
```

# Actor output Schema

## `overview` (type: `string`):

Normalized snapshots, change events, and hiring signals

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

Board success/fail counts and PPE tallies

# 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": [
        {
            "ats": "greenhouse",
            "boardToken": "airbnb",
            "label": "Airbnb"
        },
        {
            "ats": "lever",
            "boardToken": "leverdemo",
            "label": "Lever Demo"
        },
        {
            "ats": "ashby",
            "boardToken": "ashby",
            "label": "Ashby"
        }
    ],
    "kvStoreName": "ats-hiring-signal-monitor-state",
    "confirmedClosedAfterRuns": 2,
    "emitSnapshots": true,
    "emitHiringSignal": true,
    "maxJobsPerBoard": 5000
};

// Run the Actor and wait for it to finish
const run = await client.actor("lainmar/ats-hiring-signal-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": [
        {
            "ats": "greenhouse",
            "boardToken": "airbnb",
            "label": "Airbnb",
        },
        {
            "ats": "lever",
            "boardToken": "leverdemo",
            "label": "Lever Demo",
        },
        {
            "ats": "ashby",
            "boardToken": "ashby",
            "label": "Ashby",
        },
    ],
    "kvStoreName": "ats-hiring-signal-monitor-state",
    "confirmedClosedAfterRuns": 2,
    "emitSnapshots": True,
    "emitHiringSignal": True,
    "maxJobsPerBoard": 5000,
}

# Run the Actor and wait for it to finish
run = client.actor("lainmar/ats-hiring-signal-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": [
    {
      "ats": "greenhouse",
      "boardToken": "airbnb",
      "label": "Airbnb"
    },
    {
      "ats": "lever",
      "boardToken": "leverdemo",
      "label": "Lever Demo"
    },
    {
      "ats": "ashby",
      "boardToken": "ashby",
      "label": "Ashby"
    }
  ],
  "kvStoreName": "ats-hiring-signal-monitor-state",
  "confirmedClosedAfterRuns": 2,
  "emitSnapshots": true,
  "emitHiringSignal": true,
  "maxJobsPerBoard": 5000
}' |
apify call lainmar/ats-hiring-signal-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lainmar/ats-hiring-signal-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/zbnUAPW6OAT5cQirf/builds/UKCIreKivXPpSuC3X/openapi.json