# Lever Job Change Monitor (`quietdatatools/lever-job-change-monitor`) Actor

Track new, updated and removed jobs on global Lever boards. Keep separate history between runs and export changes as CSV/JSON. Failed checks preserve the last good snapshot.

- **URL**: https://apify.com/quietdatatools/lever-job-change-monitor.md
- **Developed by:** [QuietDataTools](https://apify.com/quietdatatools) (community)
- **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?

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

## Lever Job Change Monitor

Check a public Lever job board and get a clear record of what changed since your last successful check. Useful for maintaining a job board, tracking selected employers, and feeding hiring-data workflows.

### Start a monitor

1. Enter the employer's Lever board identifier. For `https://jobs.lever.co/leverdemo`, enter `leverdemo`. This is Lever's demonstration board; choose your permitted company board for real monitoring.
2. Give the monitor a name, or keep `default`.
3. Run it once to create a baseline. Reuse the same board and monitor name for subsequent checks.
4. Export the output dataset as JSON, CSV or Excel. The run's `OUTPUT` record contains a summary even when there are no changes.

You can schedule the same saved input in Apify. History belongs to the running user's account, with separate history for each board and monitor name. A new monitor name starts fresh. Deleting its named history storage also resets the baseline.

### Output states

| Status | Meaning |
| --- | --- |
| BASELINE | Present in the first successful check; not necessarily newly posted |
| NEW | Appeared after the previous successful check |
| UPDATED | The title, location or source link changed |
| UNCHANGED | Those fields are unchanged |
| NO\_LONGER\_LISTED | Missing from a complete successful response; does not prove the role was filled |

Each job row includes its source ID, title, location, source link, board, check time and previous check time. Turn off **Include unchanged jobs** to reduce output volume. Summary counts still include all states.

Failed or incomplete source checks produce an UNKNOWN summary and a failed run. They do not clear history or report removed jobs. Overlapping checks of the same monitor are rejected; retry after the other run completes. If an interrupted run leaves a lock, it expires after five minutes.

### Coverage and limits

- Lever public Postings API, global boards only. EU-hosted boards are not supported. Supply the board identifier; company-domain discovery is not included.
- One company board per run; maximum 2,000 postings and 2 MB of source response data.
- Source requests time out after 20 seconds. Runs terminate after 120 seconds.
- Tracks title, location and link changes. Full description changes are not tracked.
- Published postings only. No employer login, applicant information or job applications.
- A posting is considered no longer listed after one complete successful response omits it. This is source visibility, not verified hiring status.
- Delivery is at least once: an interrupted run can cause changes to appear again on retry. Use board + job ID + status + check time to manage downstream events.

This is an independent tool and is not affiliated with Lever. Use only boards you are authorized to monitor and respect applicable source terms.

### Pricing

Price: **$0.01 per successful board check**, including baseline and unchanged checks. One run checks one board. The Apify Pricing tab is authoritative. No automatic startup or dataset-row event is configured.

Set the maximum run charge above $0.01; the default is $0.05. Failed source requests and failed output delivery do not trigger the board-check event. Charging occurs after output delivery and before history is advanced. An interruption after charging can leave delivered output and an unadvanced snapshot; retries may repeat changes and incur another check charge.

### Support

Report problems through the Actor's Issues tab. Include the board identifier, monitor name, and run ID; do not post API keys, applicant information, or private account details.

# Actor input Schema

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

The company identifier in jobs.lever.co/company. Global Lever boards only; EU boards are not supported.

## `monitorName` (type: `string`):

Keep this name to reuse your history. Choose a different name to start a separate baseline.

## `includeUnchanged` (type: `boolean`):

Include all current jobs in the output. Turn off to receive only the initial baseline and subsequent changes.

## Actor input object example

```json
{
  "board": "leverdemo",
  "monitorName": "default",
  "includeUnchanged": true
}
```

# Actor output Schema

## `changes` (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 = {
    "board": "leverdemo"
};

// Run the Actor and wait for it to finish
const run = await client.actor("quietdatatools/lever-job-change-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 = { "board": "leverdemo" }

# Run the Actor and wait for it to finish
run = client.actor("quietdatatools/lever-job-change-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 '{
  "board": "leverdemo"
}' |
apify call quietdatatools/lever-job-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quietdatatools/lever-job-change-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/3QkKYet5dGfUoaxt6/builds/7EFAoEChknFVi2fSL/openapi.json