# Hiring Change Monitor (`woolly_kingcrab/lever-hiring-change-monitor`) Actor

Monitor public job boards powered by Lever and detect new, removed, updated, remote, salary, and hiring-trend changes between runs.

- **URL**: https://apify.com/woolly\_kingcrab/lever-hiring-change-monitor.md
- **Developed by:** [sakthi kumar](https://apify.com/woolly_kingcrab) (community)
- **Categories:** Jobs, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.20 / actor start

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/platform/actors/running/actors-in-store#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

## Hiring Change Monitor

> **Unofficial tool. Not affiliated with or endorsed by Lever.**

Monitor public Lever-powered job boards and detect meaningful hiring changes between runs instead of repeatedly receiving the same job list.

### What it detects

- New jobs
- Removed jobs
- Updated jobs
- Title and location changes
- Team and department changes
- Remote / hybrid changes
- Salary-range changes when available
- Hiring velocity
- Department hiring trends
- Company signal: `EXPANDING`, `STABLE`, or `SLOWING`

The first run creates a **baseline**, so existing jobs are not incorrectly reported as new.

### How it works

1. Fetches current public job postings
2. Compares them with the previous snapshot
3. Detects meaningful changes
4. Returns a concise summary
5. Stores the latest snapshot for the next run

### Data source

Uses Lever's public Postings API.

No browser scraping, proxies, paid data providers, or AI APIs are required.

### Use cases

- Competitor hiring intelligence
- Recruitment intelligence
- Company growth monitoring
- New department detection
- Remote hiring changes
- Salary-range monitoring
- Sales intelligence
- Market research

### Input

Configure:

- Company / Lever board identifier
- Monitor ID
- Optional title filter
- Optional location filter
- Optional team filter
- Remote-only filter
- Salary change threshold
- Optional webhook

A stable `monitorId` should be used for each monitoring configuration.

### Output

Each run can return:

- Company
- Company signal
- Current open jobs
- Previous open jobs
- New jobs
- Removed jobs
- Updated jobs
- Net change
- Hiring velocity
- Department changes
- Observation timestamp

### Scheduling

For most monitoring use cases, run daily or every 6–12 hours.

Example:

`Every 6 hours = approximately 4 checks per day`

### Pricing

**$0.20 per Actor run**

There is no additional per-result charge.

Example:

`4 runs/day × 30 days = 120 runs/month`

Approximate cost:

`120 × $0.20 = $24/month`

Actual cost depends on run frequency.

### Reliability

- Stateful comparison between runs
- Duplicate-change protection
- Existing state preserved if a data fetch fails
- Malformed API responses fail safely
- Webhooks disabled by default
- HTTPS required for webhooks
- Maximum 100 companies per run

### Why this Actor?

A normal job scraper answers:

**"What jobs are open?"**

Hiring Change Monitor answers:

**"What changed since the last check?"**

That makes it more useful for ongoing business and hiring intelligence.

### Roadmap

Possible future additions:

- Email alerts
- Slack alerts
- Greenhouse support
- Ashby support
- Additional ATS platforms
- Multi-company dashboards
- Long-term hiring trend analytics

### Disclaimer

This Actor monitors publicly available job-posting information.

Users are responsible for ensuring their use complies with applicable laws and platform terms.

**Hiring Change Monitor is an independent tool and is not affiliated with, sponsored by, or endorsed by Lever.**

# Actor input Schema

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

Stable ID for this monitoring configuration. Reuse it across scheduled runs.

## `companies` (type: `array`):

Lever company slugs or full jobs.lever.co / jobs.eu.lever.co board URLs.

## `titleContains` (type: `string`):

Optional case-insensitive title substring filter.

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

Optional exact location filters.

## `teams` (type: `array`):

Optional exact team filters.

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

Keep only postings whose Lever workplaceType is remote.

## `salaryChangeThresholdPct` (type: `integer`):

Ignore salary midpoint changes smaller than this percentage. 0 reports any salary-range change.

## `emitBaseline` (type: `boolean`):

Off by default so the first run establishes state without falsely reporting every job as new.

## `enableWebhook` (type: `boolean`):

Send the completed result to webhookUrl after a successful run.

## `webhookUrl` (type: `string`):

Optional HTTPS webhook destination. Private/local destinations are rejected.

## Actor input object example

```json
{
  "monitorId": "default",
  "titleContains": "",
  "locations": [],
  "teams": [],
  "remoteOnly": false,
  "salaryChangeThresholdPct": 0,
  "emitBaseline": false,
  "enableWebhook": false,
  "webhookUrl": ""
}
```

# Actor output Schema

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

Dataset containing CHANGE, SUMMARY, and optional BASELINE records.

## `runSummary` (type: `string`):

Compact run summary from the default key-value store.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("woolly_kingcrab/lever-hiring-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 = {}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,woolly_kingcrab/lever-hiring-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/n29bhokAdY0aQMUpP/builds/c7w5fh7YPQmtGpBgL/openapi.json