# ATS Hiring Change Monitor — Greenhouse & Ashby (`sourcerowlabs/ats-hiring-change-monitor`) Actor

Monitor a supplied list of public Greenhouse and Ashby job boards. Get normalized jobs, department totals and explainable hiring changes against your previous snapshot. Failed or incomplete boards never create removal signals. No proxies or paid APIs.

- **URL**: https://apify.com/sourcerowlabs/ats-hiring-change-monitor.md
- **Developed by:** [SourceRow Labs](https://apify.com/sourcerowlabs) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$25.00 / 1,000 complete 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 Change Monitor

See what changed on the public careers boards you already follow. Supply 1-10 Greenhouse or Ashby employer tokens to receive current job posts, company-level totals and an optional comparison with your previous snapshot.

For a focused competitor watchlist, a small job feed or a company hiring check. This Actor does not discover employers or search every job site.

### What you get

- A dataset of current listed jobs, with board/job IDs, title, location, department, original job link and observation time.
- An `OUTPUT` JSON record containing jobs, company summaries and change rows. Use this as the authoritative result.
- A `SNAPSHOT` JSON record for the next comparison.
- When a prior snapshot is supplied: `added`, `changed`, `unchanged` and `not_observed` results, including the normalized fields that changed.

A first run is a baseline. A job missing from a later complete response is only `not_observed`; this does not prove that a vacancy was filled or closed. Failed boards never create disappearance events.

### Start with two boards

```json
{
  "boards": [
    {"ats": "greenhouse", "token": "greenhouse"},
    {"ats": "ashby", "token": "ashby"}
  ],
  "maxJobsPerBoard": 500
}
```

Use the employer token from its real public ATS board URL. Duplicate boards are processed once. Check the returned source links to confirm that the token identifies the employer you intended.

### Compare runs explicitly

Download a completed run's `SNAPSHOT` record and include that complete JSON object as `previousSnapshot` in the next input. Without it, the next run is another baseline.

**A schedule alone does not carry history forward. Your workflow must pass the previous snapshot.** This version does not include automatic snapshot handoff, email alerts or an accumulating historical database. If a board fails, its previously supplied successful snapshot is retained.

### Pricing

**$0.025 per successfully completed board snapshot.** The chargeable event is `board-snapshot`; it is not a per-job or per-change price.

- A complete board is charged even when it has no listed jobs or nothing changed.
- Invalid, inaccessible, malformed, over-limit and skipped boards have no board-event charge.
- A repeated board in the same input counts once.
- Ten complete boards cost $0.25 in Actor events; two cost $0.05.
- The listed Actor-event price includes platform usage during the run. There is no startup or dataset-item event.

Set a finite maximum run charge. The Actor saves usable `OUTPUT` and `SNAPSHOT` records before requesting a board charge. If a charge result is uncertain, it stops collecting additional boards rather than automatically charging again. If the dataset export is uncertain, use `OUTPUT`.

Check the live Pricing tab before running. Separately using Apify storage after the run can incur the platform's normal storage/read charges under your account terms.

### Coverage and limits

- Greenhouse and Ashby only; 1-10 boards per run and at most 500 listed jobs per board.
- A board exceeding the chosen job cap is skipped entirely, not truncated.
- Maximum source response: 4 MiB. Maximum normalized board: 1 MiB. Maximum board snapshot: 320 KiB. Oversized boards are skipped without a board-event charge. Long source fields can reach the byte caps before the job cap.
- Input including the prior snapshot: at most 4 MiB. Memory: 256 MB. Use a 180-second hard run timeout.
- Only the two official public API hosts are contacted. No login, proxy, browser challenge handling or paid third-party API.
- Ashby salaries come only from published structured salary fields, with the original currency and interval. Greenhouse salaries are not inferred. Missing salary information stays missing.
- Ashby workplace type uses an explicit source field. Greenhouse workplace type stays unknown; a mention of remote work in prose is not classified.
- Full job descriptions and recruiter/candidate contact fields are not exported. A description hash allows text changes to be detected.

Public job-post counts are not employee counts, hires or necessarily distinct vacancies. Use source links to check the original posting and respect applicable source terms.

### Validation and support

Cloud checks on 3 November 2026 covered three owner-operated runs: a 90-job baseline, a second comparison with 90 unchanged jobs, and a run capped at USD 0.025 that returned one complete board and skipped the second before fetching it. Counts change with the source boards. These checks validate delivery and budget handling; they are not customer purchases.

For an issue, provide the ATS, public board token, error code and run ID. Do not send credentials or applicant information.

Sources: https://docs.greenhouse.io/job-board.html and https://developers.ashbyhq.com/docs/public-job-posting-api

# Actor input Schema

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

Objects with ats=greenhouse or ashby and token from the company's public job-board URL. No arbitrary URLs, cookies or credentials.

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

If a board exceeds this cap it is skipped completely and not charged. This is not a result truncation setting.

## `previousSnapshot` (type: `object`):

Paste the exact schemaVersion 1 SNAPSHOT JSON from a previous run of these boards. Omit for an initial baseline. The Actor does not automatically retain cross-run history.

## Actor input object example

```json
{
  "boards": [
    {
      "ats": "greenhouse",
      "token": "greenhouse"
    },
    {
      "ats": "ashby",
      "token": "ashby"
    }
  ],
  "maxJobsPerBoard": 500
}
```

# Actor output Schema

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

No description

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

No description

## `snapshot` (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 = {
    "boards": [
        {
            "ats": "greenhouse",
            "token": "greenhouse"
        },
        {
            "ats": "ashby",
            "token": "ashby"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sourcerowlabs/ats-hiring-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": [
        {
            "ats": "greenhouse",
            "token": "greenhouse",
        },
        {
            "ats": "ashby",
            "token": "ashby",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sourcerowlabs/ats-hiring-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": [
    {
      "ats": "greenhouse",
      "token": "greenhouse"
    },
    {
      "ats": "ashby",
      "token": "ashby"
    }
  ]
}' |
apify call sourcerowlabs/ats-hiring-change-monitor --silent --output-dataset

```

## MCP server setup

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