# Greenhouse Job Snapshot Diff (`lifoli/greenhouse-snapshot-diff`) Actor

Keep your job board current: detect added jobs, changed titles or locations, and postings no longer listed on a public Greenhouse board. Supply your last snapshot to compare. $0.01 per complete board check, not per job. No proxy or AI subscription.

- **URL**: https://apify.com/lifoli/greenhouse-snapshot-diff.md
- **Developed by:** [LiFoli Corp.](https://apify.com/lifoli) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 complete board snapshots

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

## Greenhouse Job Snapshot Diff

Fetch a complete public Greenhouse job board and compare it with a previous snapshot. Built for job-board operators and career-page integration developers. One run checks one board; no proxy or external AI subscription is needed.

### Input

First run: {"board":"figma"}.

For comparison, add previousSnapshot containing the entire snapshot object returned by your last successful run. Your workflow must carry that value forward. A fixed schedule alone does not maintain a comparison baseline.

### Output

One dataset object contains status, jobCount, fingerprint, changes and snapshot. First runs return baseline with no changes. Subsequent runs return compared.

- added: a posting ID is newly present relative to your baseline.
- updated: title, location, public URL or source update timestamp changed. changedFields and previous values are included.
- no\_longer\_listed: a posting ID is absent from a complete current response. This does not mean the role was filled.

Snapshots include posting ID, title, location, job URL and source update timestamp. observedAt is our observation time, not a publication date. Description and compensation changes are outside this version.

### Reliability and limits

HTTP errors, redirects, timeouts, malformed jobs, duplicate IDs and inconsistent totals fail without replacement snapshots. Retain the last successful snapshot after failure. Valid empty boards are accepted; an upstream API that returns internally consistent but incorrect empty data cannot be detected.

Maximum response: 8 MB. Public board tokens only. No applicant data, global company discovery, other ATS platforms, email delivery or application submission. Caller-supplied baselines keep customers separate. Avoid duplicate invocations; independent successful runs may each be charged.

### Pricing

Check the live pricing panel. The board-snapshot event is one complete board result, including a baseline or comparison with no changes. At most one chargeable result per run. Failed reads do not generate that event.

### Source

Uses the [Greenhouse public Job Board API](https://docs.greenhouse.io/job-board.html). Independent integration, not affiliated with Greenhouse or listed employers. Use outputs within applicable source terms; public availability does not grant unrestricted redistribution rights.

# Actor input Schema

## `board` (type: `string`):

Public Greenhouse board token, for example figma. URLs are not accepted.

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

Pass the snapshot object from your previous successful result. Omit for a baseline. No shared storage is used.

## Actor input object example

```json
{
  "board": "figma"
}
```

# Actor output Schema

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

One complete snapshot and change set, including the snapshot to reuse for the next comparison.

# 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 = {
    "board": "figma"
};

// Run the Actor and wait for it to finish
const run = await client.actor("lifoli/greenhouse-snapshot-diff").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 = { "board": "figma" }

# Run the Actor and wait for it to finish
run = client.actor("lifoli/greenhouse-snapshot-diff").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 '{
  "board": "figma"
}' |
apify call lifoli/greenhouse-snapshot-diff --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lifoli/greenhouse-snapshot-diff"
        }
    }
}
```

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/29AOS5Dowx20Y4UPi/builds/H6hrvWxLMaDgG6HbQ/openapi.json