# Multi-ATS Job Change Radar (`aieast/multi-ats-job-change-radar`) Actor

Normalize and monitor public job listings from Greenhouse, Lever, and Ashby. Detect new, changed, and closed roles for recruiting, sales intelligence, and market research.

- **URL**: https://apify.com/aieast/multi-ats-job-change-radar.md
- **Developed by:** [Aden](https://apify.com/aieast) (community)
- **Categories:** Jobs, Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 normalized job or change records

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

## Multi-ATS Job Change Radar

Turn public **Greenhouse, Lever, and Ashby** job boards into one normalized hiring-intelligence feed. Monitor several companies at once and detect **new, changed, and closed roles** without maintaining three integrations.

### Why use this Actor?

Public job postings are useful signals, but every applicant-tracking system returns different fields. This Actor gives you a stable schema for:

- recruiting and job aggregation,
- sales signals such as a company building a new security or data team,
- competitive and investment research,
- scheduled hiring-change alerts,
- AI agents that need structured, source-linked job data.

It uses the public job-board endpoints provided by each supported ATS. No login, browser session, proxy, or third-party API key is required.

### Supported sources

Paste a public company job-board URL in any of these formats:

```text
https://boards.greenhouse.io/cloudflare
https://jobs.lever.co/spotify
https://jobs.ashbyhq.com/Notion
```

API URLs and shorthand such as `greenhouse:cloudflare`, `lever:spotify`, and `ashby:Notion` are also accepted.

### Input example

```json
{
  "boardUrls": [
    "https://boards.greenhouse.io/cloudflare",
    "https://jobs.lever.co/spotify",
    "https://jobs.ashbyhq.com/Notion"
  ],
  "keywords": ["security", "data engineer"],
  "excludeKeywords": ["intern"],
  "locations": ["London", "Remote"],
  "departments": ["Engineering", "Security"],
  "remoteOnly": false,
  "matchAllKeywords": false,
  "monitorId": "target-companies-security",
  "deltaOnly": true,
  "includeClosed": true,
  "maxResults": 500
}
```

All filters are deterministic and case-insensitive. Leave the optional filter lists empty to return every listed role.

### Output example

```json
{
  "status": "ok",
  "jobKey": "ashby:notion:1fc309c8-da20-4ff2-84c7-8b863ece2b0a",
  "jobId": "1fc309c8-da20-4ff2-84c7-8b863ece2b0a",
  "changeStatus": "new",
  "isOpen": true,
  "provider": "ashby",
  "company": "Notion",
  "title": "Software Engineer, Developer Platform",
  "location": "San Francisco, California",
  "locations": ["San Francisco, California", "New York, New York"],
  "department": "Engineering",
  "team": "Engineering",
  "employmentType": "FullTime",
  "workplaceType": "Hybrid",
  "remote": true,
  "description": "Who We Are...",
  "salary": null,
  "publishedAt": "2026-08-24T14:44:49.699Z",
  "sourceUpdatedAt": "",
  "jobUrl": "https://jobs.ashbyhq.com/Notion/...",
  "applyUrl": "https://jobs.ashbyhq.com/Notion/.../application",
  "sourceBoardUrl": "https://jobs.ashbyhq.com/Notion",
  "fetchedAt": "2026-09-06T00:00:00.000Z"
}
```

Every successful run also writes a compact `OUTPUT` summary with board success counts, jobs scanned, matches, change counts, paid records, and warnings.

### Change monitoring

1. Choose a stable `monitorId` for one board-and-filter configuration.
2. Run once to create its private snapshot.
3. Schedule the same input and set `deltaOnly` to `true`.
4. Later runs return only `new`, `changed`, or `closed` records.

A role is marked `closed` only when its source board was fetched successfully and the previous role ID has disappeared. A failed board is never interpreted as mass closures. Use a different `monitorId` when you materially change the company list or filters.

### Pricing

This Actor uses pay-per-event pricing:

- **$0.002 per normalized job or change record** successfully delivered.
- No start fee.
- Failed source boards and error rows are not charged.
- `maxResults` is a hard cap on paid output records.

Examples: 100 records cost $0.20; 1,000 records cost $2.00. Scheduled `deltaOnly` runs usually return far fewer records than full snapshots.

### Reliability and limitations

- Data is read from public employer-managed job boards and can change without notice.
- Company names are inferred from the board identifier when a source does not provide one.
- A job-board URL must belong to Greenhouse, Lever, or Ashby; careers pages backed by Workday or another ATS are not supported.
- Salary is returned only when the source exposes a structured value.
- Respect each employer's terms and applicable privacy, employment, and data-protection law. Do not use job data for unlawful discrimination, spam, or automated employment decisions.

### Source references

- [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)

### Need another ATS?

Use the Issues tab on the Actor page and include one public example careers URL. The best candidates for the next integrations are Workable, SmartRecruiters, and Recruitee.

# Actor input Schema

## `boardUrls` (type: `array`):

Supports boards.greenhouse.io, jobs.lever.co, and jobs.ashbyhq.com URLs. You can monitor several companies in one run.

## `keywords` (type: `array`):

Match against title, description, department, team, and location. Leave empty to include every role.

## `excludeKeywords` (type: `array`):

Discard roles containing any of these terms.

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

Case-insensitive partial match, for example London, Germany, or Remote.

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

Case-insensitive partial match, for example Engineering, Sales, or Security.

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

Return only roles explicitly marked remote or whose listed location contains Remote or Anywhere.

## `matchAllKeywords` (type: `boolean`):

Off means any include keyword can match.

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

Stable name for this company/filter set. Reuse it in scheduled runs to detect changes.

## `deltaOnly` (type: `boolean`):

Best for scheduled monitoring. The first run returns the current matching jobs; later runs return only changes.

## `includeClosed` (type: `boolean`):

Detect roles that existed in the previous successful snapshot but are no longer listed.

## `maxResults` (type: `integer`):

Hard cap on normalized records delivered in this run.

## Actor input object example

```json
{
  "boardUrls": [
    "https://jobs.lever.co/spotify"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "matchAllKeywords": false,
  "monitorId": "default",
  "deltaOnly": false,
  "includeClosed": true,
  "maxResults": 100
}
```

# Actor output Schema

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

No description

## `dataset` (type: `string`):

No description

## `summary` (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 = {
    "boardUrls": [
        "https://jobs.lever.co/spotify"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("aieast/multi-ats-job-change-radar").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 = { "boardUrls": ["https://jobs.lever.co/spotify"] }

# Run the Actor and wait for it to finish
run = client.actor("aieast/multi-ats-job-change-radar").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 '{
  "boardUrls": [
    "https://jobs.lever.co/spotify"
  ]
}' |
apify call aieast/multi-ats-job-change-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aieast/multi-ats-job-change-radar"
        }
    }
}

```

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/y5U3bsYYKYMVEeFzX/builds/uzjDK966oQnMFTHcB/openapi.json