# ATS Hiring Changes by Company (`isolovyev/ats-hiring-changes-monitor`) Actor

Track exact public ATS boards and return normalized hiring changes with source links. Отслеживайте публичные ATS-доски и получайте нормализованные изменения найма со ссылками на источники.

- **URL**: https://apify.com/isolovyev/ats-hiring-changes-monitor.md
- **Developed by:** [Ivan Solovyev](https://apify.com/isolovyev) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 complete company 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?

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

[English](#english) | [На русском](#na-russkom)

### English

Turn a target-company list into verified hiring-change records. Track exact public Greenhouse, Lever, and Ashby boards, then send normalized jobs and source links to Sheets, a CRM, a database, Make, or n8n through JSON or CSV.

#### What you get

- normalized job records with title, department, location, role family, work arrangement, published salary text, and direct source links;
- `current`, `new`, `changed`, and `closed` events;
- one `company_check` record per board with coverage, counts, and department, location, and role-family signals;
- stable job-event IDs for delivery deduplication and a state fingerprint for comparing board states.

The Actor reads public job postings. It does not collect candidate or applicant data.

#### A focused agency workflow

1. Create one stable `watchId` per client or campaign.
2. Add up to 100 exact company board URLs.
3. Run once to establish the baseline.
4. Repeat the same input weekly or daily.
5. Export the dataset as JSON or CSV and use each `sourceUrl` to review the original posting.

A practical starting point is 20 companies checked weekly. Filter job events by `roleFamily`, location, or department before sending them to your own Sheets or CRM workflow.

#### Input example

```json
{
  "companyBoards": [
    "Stripe | https://job-boards.greenhouse.io/stripe",
    "Spotify | https://jobs.lever.co/spotify",
    "Ramp | https://jobs.ashbyhq.com/ramp"
  ],
  "watchId": "agency-demo",
  "mode": "monitor",
  "emitInitialSnapshot": true,
  "includeDescriptions": false,
  "maxTotalJobs": 3000,
  "concurrency": 3
}
```

Use `monitor` for change tracking. `snapshot` returns current jobs without using monitor history. State is isolated by the Apify user who starts the run and by `watchId`.

#### Output example

This compact record is based on a verified acceptance run. Public boards change over time, so counts and individual jobs may differ on later runs.

```json
{
  "recordType": "job",
  "recordId": "ba5be3f2cbe49444ac4b676f5f753402aed03391fb8ba1e333569b3c5e131217",
  "watchId": "ats-prefill-sample",
  "companyKey": "greenhouse:stripe",
  "companyName": "Stripe",
  "coverageStatus": "complete",
  "eventType": "current",
  "transitionRevision": 1,
  "title": "Abuse Investigator",
  "departments": ["8611 Security Analytics"],
  "locations": ["Seattle, San Francisco, New York City", "US"],
  "roleFamily": "other",
  "sourceUrl": "https://stripe.com/jobs/search?gh_jid=8172510"
}
```

#### Coverage and history

- `complete`: the full board was read; a missing prior job may be marked `closed`.
- `partial`: a limit or parsing issue prevented a complete comparison; no jobs are closed.
- `unknown`: the board could not be verified in this run; no jobs are closed.

A removed posting is an observation about the public board. It does not prove that the employer filled or cancelled the position.

The Actor fetches companies in bounded batches. Per-company and run-level job and response limits cap work. Companies skipped after a run budget is reached are marked `partial` and cannot create closures.

Each `company_check` has a unique check `recordId` and a `stateFingerprint`. Job events use a persisted `transitionRevision`, so a delivery retry keeps the same ID while a later lifecycle transition gets a new ID.

Run one monitor execution at a time for the same `watchId`. Concurrent runs for one watch are outside the current state-consistency contract.

#### Pricing

Billed once per complete company-board check, including checks with no changes or no open jobs. Platform usage is included. Partial and unknown checks are free and do not advance monitoring history. Partial checks return a coverage summary without job records. The run spending limit bounds the number of company checks. See the current rate in Pricing before starting a run.

### На русском

Превратите список целевых компаний в проверяемые записи об изменениях найма. Актор отслеживает точные публичные доски Greenhouse, Lever и Ashby, нормализует вакансии и отдаёт ссылки на первоисточники для таблиц, CRM, базы данных, Make или n8n через JSON или CSV.

#### Что вы получите

- нормализованные вакансии с должностью, отделом, локацией, семейством роли, форматом работы, опубликованной зарплатой и прямой ссылкой;
- события `current`, `new`, `changed`, `closed`;
- запись `company_check` по каждой доске со статусом полноты, счётчиками и сигналами по отделам, локациям и семействам ролей;
- стабильные ID событий для дедупликации доставки и отпечаток состояния для сравнения досок.

Актор читает публичные вакансии и не собирает данные кандидатов или соискателей.

#### Сценарий для агентства

1. Задайте отдельный стабильный `watchId` для клиента или кампании.
2. Добавьте до 100 точных ссылок на доски компаний.
3. Первый запуск создаст исходное состояние.
4. Повторяйте тот же input ежедневно или еженедельно.
5. Выгружайте dataset в JSON или CSV и проверяйте исходную вакансию по `sourceUrl`.

Удобная стартовая выборка: 20 компаний раз в неделю. Перед передачей в свой сценарий для таблицы или CRM фильтруйте события по `roleFamily`, локации или отделу.

#### Пример input

```json
{
  "companyBoards": [
    "Stripe | https://job-boards.greenhouse.io/stripe",
    "Spotify | https://jobs.lever.co/spotify",
    "Ramp | https://jobs.ashbyhq.com/ramp"
  ],
  "watchId": "agency-demo",
  "mode": "monitor",
  "emitInitialSnapshot": true,
  "includeDescriptions": false,
  "maxTotalJobs": 3000,
  "concurrency": 3
}
```

Режим `monitor` отслеживает изменения. `snapshot` возвращает текущие вакансии без использования истории. Состояние изолировано по пользователю Apify, который запустил Actor, и по `watchId`.

#### Пример результата

Компактная запись ниже взята из проверочного запуска. Публичные доски меняются, поэтому вакансии и счётчики в следующих запусках могут отличаться.

```json
{
  "recordType": "job",
  "recordId": "ba5be3f2cbe49444ac4b676f5f753402aed03391fb8ba1e333569b3c5e131217",
  "watchId": "ats-prefill-sample",
  "companyKey": "greenhouse:stripe",
  "companyName": "Stripe",
  "coverageStatus": "complete",
  "eventType": "current",
  "transitionRevision": 1,
  "title": "Abuse Investigator",
  "departments": ["8611 Security Analytics"],
  "locations": ["Seattle, San Francisco, New York City", "US"],
  "roleFamily": "other",
  "sourceUrl": "https://stripe.com/jobs/search?gh_jid=8172510"
}
```

#### Полнота и история

- `complete`: доска прочитана полностью, пропавшая вакансия может получить событие `closed`;
- `partial`: лимит или ошибка разбора помешали полному сравнению, вакансии не закрываются;
- `unknown`: источник в этом запуске не подтверждён, вакансии не закрываются.

Снятие публикации отражает состояние публичной доски. Оно не доказывает, что работодатель закрыл или отменил позицию.

Актор проверяет компании ограниченными пакетами. Лимиты вакансий и объёма ответов для компании и всего запуска сдерживают нагрузку. Компании, пропущенные после исчерпания общего лимита, получают статус `partial` и не создают закрытий.

Каждая запись `company_check` получает уникальный `recordId` проверки и `stateFingerprint`. У событий вакансий сохраняется `transitionRevision`: повтор доставки имеет тот же ID, а следующий переход жизненного цикла получает новый ID.

Для одного `watchId` запускайте только один мониторинг одновременно. Согласованность истории при параллельных запусках одного наблюдения не гарантируется.

#### Оплата

Оплачивается каждая полная проверка доски компании, в том числе без изменений или открытых вакансий. Расходы платформы включены. Неполные и неподтверждённые проверки бесплатны и не обновляют историю мониторинга. Неполная проверка возвращает сводку полноты без записей вакансий. Лимит расходов запуска ограничивает число проверок компаний. Актуальный тариф указан в Pricing.

# Actor input Schema

## `companyBoards` (type: `array`):

One exact Greenhouse, Lever, or Ashby board URL per line. Optional format: Company name | URL.

## `watchId` (type: `string`):

Stable ID for this client or campaign. State is isolated by the starting Apify user and this value.

## `mode` (type: `string`):

Monitor changes against prior complete checks or return a current snapshot without history.

## `emitInitialSnapshot` (type: `boolean`):

Emit current job records while establishing a new monitor baseline.

## `includeDescriptions` (type: `boolean`):

Adds normalized public description text to job records.

## `maxJobsPerCompany` (type: `integer`):

Stop collecting a company after this many jobs and mark its coverage partial.

## `maxTotalJobs` (type: `integer`):

Stop fetching later company batches when the run reaches this job budget.

## `maxResponseBytes` (type: `integer`):

Reject larger source responses and keep prior history without closures.

## `maxTotalResponseBytes` (type: `integer`):

Stop fetching later company batches when the run reaches this response budget.

## `maxDescriptionChars` (type: `integer`):

Trim emitted descriptions to this length when descriptions are enabled.

## `requestTimeoutSeconds` (type: `integer`):

Maximum time allowed for each public ATS request.

## `concurrency` (type: `integer`):

Number of company boards fetched in parallel, from 1 to 8.

## Actor input object example

```json
{
  "companyBoards": [
    "Spotify | https://jobs.lever.co/spotify"
  ],
  "watchId": "autotest-snapshot",
  "mode": "snapshot",
  "emitInitialSnapshot": true,
  "includeDescriptions": false,
  "maxJobsPerCompany": 1000,
  "maxTotalJobs": 10000,
  "maxResponseBytes": 12000000,
  "maxTotalResponseBytes": 100000000,
  "maxDescriptionChars": 20000,
  "requestTimeoutSeconds": 20,
  "concurrency": 8
}
```

# Actor output Schema

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

Normalized jobs, hiring-change events and company coverage summaries. Нормализованные вакансии, изменения найма и полнота проверок компаний.

# 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 = {
    "companyBoards": [
        "Spotify | https://jobs.lever.co/spotify"
    ],
    "watchId": "autotest-snapshot",
    "mode": "snapshot",
    "emitInitialSnapshot": true,
    "includeDescriptions": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("isolovyev/ats-hiring-changes-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 = {
    "companyBoards": ["Spotify | https://jobs.lever.co/spotify"],
    "watchId": "autotest-snapshot",
    "mode": "snapshot",
    "emitInitialSnapshot": True,
    "includeDescriptions": False,
}

# Run the Actor and wait for it to finish
run = client.actor("isolovyev/ats-hiring-changes-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 '{
  "companyBoards": [
    "Spotify | https://jobs.lever.co/spotify"
  ],
  "watchId": "autotest-snapshot",
  "mode": "snapshot",
  "emitInitialSnapshot": true,
  "includeDescriptions": false
}' |
apify call isolovyev/ats-hiring-changes-monitor --silent --output-dataset

```

## MCP server setup

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