# ATS Hiring Change Monitor (`woolly_kingcrab/greenhouse-hiring-change-monitor`) Actor

Monitor public Greenhouse-powered job boards and detect meaningful hiring changes between runs.

- **URL**: https://apify.com/woolly\_kingcrab/greenhouse-hiring-change-monitor.md
- **Developed by:** [sakthi kumar](https://apify.com/woolly_kingcrab) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.20 / actor start

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ATS Hiring Change Monitor

> **Unofficial tool. Not affiliated with or endorsed by Greenhouse Software.**

Monitor public job boards powered by Greenhouse and detect meaningful hiring changes between runs instead of repeatedly receiving the same raw job list.

### What it detects

- New jobs
- Removed jobs
- Updated jobs
- Title and location changes
- Department and office changes
- Remote / hybrid wording changes
- Public pay-range changes when optional pay-transparency fetching is enabled
- Hiring velocity
- Department hiring trends
- Company signal: `EXPANDING`, `STABLE`, or `SLOWING`

The first run creates a **baseline**, so existing jobs are not incorrectly reported as new.

### Data source

Uses Greenhouse's public Job Board API. Public GET endpoints require no authentication.

The primary endpoint is:

`GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true`

No browser scraping, proxies, paid data providers, or AI APIs are required.

### Why this Actor?

A normal Greenhouse scraper answers:

**"What jobs are open?"**

This Actor answers:

**"What changed since the last check?"**

That makes the output useful for competitor intelligence, recruiting research, sales research, and company-growth monitoring.

### Input

- Greenhouse board token or public board URL
- Monitor ID
- Optional title, location, and department filters
- Remote-only filter
- Optional description-change tracking
- Optional public pay-transparency fetching
- Optional webhook

### Output

Each run returns a summary including:

- Company / board
- Company signal
- Current and previous open-job counts
- New, removed, and updated job counts
- Net change
- Hiring velocity
- Department changes
- Observation timestamp

Detailed change records are emitted when changes occur.

### Scheduling

Daily or every 6–12 hours is usually enough.

### Pricing

Recommended Store pricing:

- **$0.20 per Actor start**
- No additional per-result charge

Four checks per day is approximately $24/month.

### Reliability

- Stateful comparison between runs
- Duplicate-change protection
- Fetch-all-before-state-mutation fail-closed behavior
- Existing state preserved when a fetch fails
- Webhooks off by default
- HTTPS-only webhook validation
- Maximum 100 boards per run
- Optional pay-transparency API-call safety cap

### Roadmap

- Email / Slack alerts
- Additional ATS sources
- Multi-company dashboards
- Longer-term hiring trend analytics

### Disclaimer

This Actor monitors publicly available job-posting information. Users are responsible for ensuring their use complies with applicable laws and platform terms.

**This is an independent tool and is not affiliated with, sponsored by, or endorsed by Greenhouse Software.**

# Actor input Schema

## `monitorId` (type: `string`):

Stable ID for this monitoring configuration. Reuse it across scheduled runs.

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

Board tokens or public Greenhouse board/API URLs.

## `titleContains` (type: `string`):

Optional case-insensitive title substring filter.

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

Optional exact location filters.

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

Optional exact department filters.

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

Keep only jobs where Remote is disclosed in the title/location.

## `trackDescriptionChanges` (type: `boolean`):

Hash descriptions and report a job as updated when the description changes.

## `includePayTransparency` (type: `boolean`):

Optional. Fetch public Greenhouse pay-transparency ranges with per-job API calls.

## `maxPayTransparencyJobs` (type: `integer`):

Safety cap when pay-transparency fetching is enabled.

## `emitBaseline` (type: `boolean`):

Off by default so the first run establishes state without falsely reporting every job as new.

## `enableWebhook` (type: `boolean`):

Send results to webhookUrl after a successful run.

## `webhookUrl` (type: `string`):

Optional HTTPS webhook destination. Private/local destinations are rejected.

## Actor input object example

```json
{
  "monitorId": "default",
  "boards": [
    "stripe"
  ],
  "titleContains": "",
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "trackDescriptionChanges": false,
  "includePayTransparency": false,
  "maxPayTransparencyJobs": 200,
  "emitBaseline": false,
  "enableWebhook": false,
  "webhookUrl": ""
}
```

# Actor output Schema

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

Dataset containing CHANGE, SUMMARY, and optional BASELINE records.

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

Compact run summary from the default key-value store.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("woolly_kingcrab/greenhouse-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 = {}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,woolly_kingcrab/greenhouse-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/cpUUrnsjIgt5nPxL5/builds/36AVIgi9ZqKwyJZ0w/openapi.json