# Job Board Delta | Greenhouse, Lever & Ashby Changes (`sbio-apps/job-board-delta-monitor`) Actor

Track new, edited and removed public job postings across Greenhouse, Lever and Ashby boards. Keep persistent history and confirm removals across two complete checks. Return changes for recruiting and hiring-intelligence workflows.

- **URL**: https://apify.com/sbio-apps/job-board-delta-monitor.md
- **Developed by:** [Austin Aryain](https://apify.com/sbio-apps) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 successful board checks

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

{
"actorSpecification": 1,
"fields": {
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"required": \[
"monitorId",
"board",
"checkedAt",
"status",
"currentJobs",
"changeCount",
"pendingRemovals",
"changes"
],
"properties": {
"monitorId": {
"type": "string",
"description": "History scope."
},
"board": {
"type": "string",
"description": "Provider and company board identifier."
},
"checkedAt": {
"type": "string",
"format": "date-time"
},
"status": {
"type": "string",
"enum": \[
"checked",
"baseline\_created"
]
},
"currentJobs": {
"type": "integer",
"description": "Current listed postings in the complete source snapshot."
},
"changeCount": {
"type": "integer",
"description": "Number of emitted changes."
},
"pendingRemovals": {
"type": "integer",
"description": "Postings absent once, awaiting another complete check."
},
"changes": {
"type": "array",
"description": "New, updated or twice-absent postings. Removed means absent from two observed snapshots, not confirmed filled.",
"items": {
"type": "object",
"required": \[
"eventId",
"type",
"id",
"title",
"url"
],
"properties": {
"eventId": {
"type": "string",
"description": "Deterministic transition ID for replay deduplication."
},
"type": {
"type": "string",
"enum": \[
"new",
"updated",
"removed"
]
},
"id": {
"type": "string",
"description": "Source posting ID or Ashby job URL."
},
"title": {
"type": "string",
"description": "Job title."
},
"url": {
"type": "string",
"format": "uri"
},
"location": {
"type": "string",
"description": "Primary source location."
},
"department": {
"type": "string",
"description": "Department or team."
},
"employmentType": {
"type": "string",
"description": "Source employment category, if available."
},
"workplaceType": {
"type": "string",
"description": "Source workplace type, if available."
},
"descriptionHash": {
"type": "string",
"description": "SHA-256 of the source description fields; full descriptions are not returned."
},
"compensationSummary": {
"type": "string",
"description": "Ashby source compensation summary when published."
}
}
}
}
}
},
"views": {
"overview": {
"title": "Board checks",
"transformation": {
"fields": \[
"board",
"status",
"currentJobs",
"changeCount",
"pendingRemovals",
"checkedAt",
"changes"
]
},
"display": {
"component": "table",
"properties": {
"board": {
"label": "board",
"format": "text"
},
"status": {
"label": "status",
"format": "text"
},
"currentJobs": {
"label": "currentJobs",
"format": "number"
},
"changeCount": {
"label": "changeCount",
"format": "number"
},
"pendingRemovals": {
"label": "pendingRemovals",
"format": "number"
},
"checkedAt": {
"label": "checkedAt",
"format": "text"
},
"changes": {
"label": "changes",
"format": "array"
}
}
}
}
}
}

# Actor input Schema

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

1-20 entries: greenhouse:board, ashby:board, lever:board or lever-eu:board. Use the company identifier from its hosted job-board URL.

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

Reuse this ID for persistent history. Omit only on a saved task, whose ID is used instead. Use a new ID to reset the baseline.

## `firstRun` (type: `string`):

Emit returns current postings on the initial run; baseline saves them without changes. Later checks always compare history.

## Actor input object example

```json
{
  "boards": [
    "greenhouse:greenhouse"
  ],
  "monitorId": "hiring-monitor",
  "firstRun": "emit"
}
```

# Actor output Schema

## `checks` (type: `string`):

Priced dataset records, including observed unchanged checks or HTTP audit errors as documented.

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

Free errors, spending/time stops and unprocessed inputs.

# 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": [
        "greenhouse:greenhouse"
    ],
    "monitorId": "hiring-monitor"
};

// Run the Actor and wait for it to finish
const run = await client.actor("sbio-apps/job-board-delta-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": ["greenhouse:greenhouse"],
    "monitorId": "hiring-monitor",
}

# Run the Actor and wait for it to finish
run = client.actor("sbio-apps/job-board-delta-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": [
    "greenhouse:greenhouse"
  ],
  "monitorId": "hiring-monitor"
}' |
apify call sbio-apps/job-board-delta-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sbio-apps/job-board-delta-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/EKKX1ZvAknmzakjrg/builds/yEL3h67CjRef8vQOI/openapi.json