# Job Feed Delta — New Jobs, Updates & Confirmed Closures (`gertner-data/job-feed-delta`) Actor

Track new vacancies, field-level updates and confirmed closures across Greenhouse, Lever and Ashby. Up to 25 boards in one report. Stable IDs, before/after values and reusable snapshots for recruiting, job-board sync and n8n/Make. Launch price: $0.005/report plus start.

- **URL**: https://apify.com/gertner-data/job-feed-delta.md
- **Developed by:** [Евгений Гертнер](https://apify.com/gertner-data) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 complete feed reports

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

## Job Feed Delta

Track new vacancies, field-level updates and confirmed closures across **Greenhouse, Lever and Ashby** in one JSON report. Monitor **up to 25 boards at the launch price of $0.005 per report**, plus the run-start event. Route hiring signals into recruiting workflows, job-board sync and n8n/Make automations.

Stable source IDs, before/after values and reusable snapshots keep downstream processing focused on what changed. Built-in recovery preserves the last healthy board state during temporary source failures.

### Who it is for

Job-board operators keeping listings current, recruiters watching target companies and teams building programmatic hiring signals. Supply the boards you want to monitor and receive ready-to-route change events.

### Input

```json
{
  "boards": [
    {"provider":"greenhouse","slug":"cloudflare"},
    {"provider":"ashby","slug":"notion"},
    {"provider":"lever","slug":"spotify"}
  ]
}
```

The first call returns `BASELINE` events. Store `nextSnapshot` in your workflow, then pass it as `previousSnapshot` on the next call. This requires no manual work once the workflow is wired up. Snapshots belong to the caller; there is no shared server-side customer state and no cross-customer cache.

For n8n or Make: schedule → load your last snapshot → run Actor → fetch `OUTPUT` → route events → atomically save `nextSnapshot`. Never run two writers against the same snapshot concurrently. Use a single serial schedule per feed and queue overlapping requests. A platform schedule alone, with unchanged input, will repeatedly return baselines; it must be paired with a stateful workflow.

### What the events mean

- `BASELINE`: already present when observation started.
- `NEW`: new source ID since the previous snapshot.
- `UPDATED`: a tracked field changed; previous and current values are included.
- `CLOSED`: a source vacancy is absent from two successful board observations.

Remote status and salary retain the source's structured values; unavailable values use `null`. Source IDs preserve distinct vacancies with matching titles. Each ATS keeps its own IDs, including during provider migrations.

### API coverage and run settings

1–25 boards per call; 10,000 postings per board; 4 MB per upstream response; sequential board requests; three attempts for transient failures; 12-second request timeout; 150-second collection deadline for the entire feed. Unchecked boards receive RUN\_TIME\_BUDGET warnings and retain their previous state. Only fixed official ATS hosts are fetched. Arbitrary URLs, redirects and application POST requests are unsupported.

If more than 70% of a known board with at least three roles disappears, `MASS_REMOVAL_GUARD` preserves the entire prior board. Independently verify the change before enabling `acceptMassRemoval`. Even with that option, closure requires two successful observations. Boards not included in the current call remain in the supplied snapshot but are not newly checked. Large snapshots should be split into separate feeds.

The output focuses on vacancy fields and change events. Use public boards you are authorized to monitor and comply with source terms.

### Output

The default key-value store's `OUTPUT` record contains the complete report, including `events`, `warnings`, board observations and `nextSnapshot`. The default dataset contains one summary item per report. It is not one row per vacancy. Fetch `OUTPUT` when you need the snapshot for the next check; exporting the dataset alone does not preserve workflow state.

`METRICS` contains execution measurements. A successful run can still include warnings for individual boards. Check these before interpreting a lack of changes as a lack of hiring activity.

### Pricing

**Launch price: $0.005 per report**, covering up to 25 boards, plus **$0.001 per Actor start event**. The platform's start-event quantity depends on memory (one event per GB, minimum one); the default is 256 MB. Platform usage is included. There is no additional default dataset-item event charge. One dataset item is one report summary, not one vacancy.

Repeated successful checks are billable even if unchanged. A partial-success report is charged and identifies failed sources in `warnings`. If every source fails, no report event is charged; the start event can still apply.

Set a maximum run cost through Console or the API to control spending. The adapter uses the official SDK's `report` event and user spending limits.

Support: [Evgeny Gertner](https://t.me/evgertner). Include the run ID and affected provider/board, without applicant data or credentials.

# Actor input Schema

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

1–25 explicit public boards: provider (greenhouse, lever, ashby), slug and optional Lever region (global/eu).

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

Pass nextSnapshot from the last output. Omit for initial baseline. Keep snapshots in your own workflow; this Actor has no shared customer state.

## `acceptMassRemoval` (type: `boolean`):

Off by default. Enable only after independently verifying that a >70% drop is genuine. Still requires two successful observations for CLOSED.

## Actor input object example

```json
{
  "boards": [
    {
      "provider": "greenhouse",
      "slug": "cloudflare"
    },
    {
      "provider": "ashby",
      "slug": "notion"
    }
  ],
  "acceptMassRemoval": false
}
```

# Actor output Schema

## `report` (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 = {
    "boards": [
        {
            "provider": "greenhouse",
            "slug": "cloudflare"
        },
        {
            "provider": "ashby",
            "slug": "notion"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("gertner-data/job-feed-delta").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": [
        {
            "provider": "greenhouse",
            "slug": "cloudflare",
        },
        {
            "provider": "ashby",
            "slug": "notion",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("gertner-data/job-feed-delta").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": [
    {
      "provider": "greenhouse",
      "slug": "cloudflare"
    },
    {
      "provider": "ashby",
      "slug": "notion"
    }
  ]
}' |
apify call gertner-data/job-feed-delta --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gertner-data/job-feed-delta"
        }
    }
}
```

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/H4xvYnx5l4g3ox3em/builds/J1FAQQZcAiJ0zyFxm/openapi.json