# Company Hiring Monitor: Lever Job Openings & Changes (`prized_rainstorm/hiring-monitor`) Actor

Current public Lever job openings, hiring summaries, and opened/closed changes since your previous successful check. Schedule daily. Charged only for successful company checks.

- **URL**: https://apify.com/prized_rainstorm/hiring-monitor.md
- **Developed by:** [prized rainstorm](https://apify.com/prized_rainstorm) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 company checkeds

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

## Company Hiring Monitor: Lever Job Openings & Changes

Get current public jobs for companies using Lever, plus new and closed postings since the previous successful check. Use hiring signals for account research, recruiting, job alerts, or market monitoring. No Lever account, API key, login, or proxy is needed.

### Input

```json
{
  "companies": ["palantir", "https://jobs.eu.lever.co/example-company"],
  "monitorId": "daily"
}
```

Supply 1–500 unique company slugs or exact HTTPS board URLs on `jobs.lever.co` or `jobs.eu.lever.co`. Slugs are lowercased and deduplicated; they must match `^[a-z0-9][a-z0-9._-]{0,99}$`. Invalid input rejects the run before collection or billing. URLs with credentials, ports, queries, fragments, or extra path segments are rejected.

`monitorId` defaults to `default` and must match `^[a-z0-9-]{1,40}$`. Reuse the same ID to compare runs. Different IDs create independent monitors. The prefill `palantir` was checked against the public API on October 15, 2026 and returned 314 openings; counts change over time.

### Output

One dataset item per company. This illustrative first-check result shows one posting:

```json
{
  "company": "example-company",
  "source": "lever",
  "boardUrl": "https://jobs.lever.co/example-company",
  "status": "ok",
  "checkedAt": "2026-10-15T12:00:00.000Z",
  "openCount": 1,
  "summary": {
    "byTeam": { "Engineering": 1 },
    "byDepartment": { "Product": 1 },
    "byLocation": { "Remote": 1 },
    "byCommitment": { "Full-time": 1 },
    "byWorkplaceType": { "remote": 1 }
  },
  "postings": [{
    "id": "example-id",
    "title": "Software Engineer",
    "team": "Engineering",
    "department": "Product",
    "location": "Remote",
    "commitment": "Full-time",
    "workplaceType": "remote",
    "createdAt": "2026-10-14T09:00:00.000Z",
    "url": "https://jobs.lever.co/example-company/example-id"
  }],
  "changes": {
    "firstCheck": true,
    "previousCheckedAt": null,
    "opened": [],
    "closed": []
  }
}
```

`source` is `lever` or `lever-eu`. `opened` contains complete postings whose IDs were absent last time. `closed` contains the previous `id`, `title`, and `url` for IDs that disappeared. A title change on the same ID is not an opening or closure. The first successful check establishes the baseline and reports no changes.

Snapshots persist in the named key-value store `hiring-monitor-state-<monitorId>`, one key per normalized company. Only successful, delivered checks update them. Timeouts, invalid or incomplete responses, and missing boards preserve the previous snapshot and report empty change arrays. `previousCheckedAt` points to the last successful check, even after failed runs. Without any snapshot, `firstCheck` remains true.

Schedule this Actor daily with the same `monitorId` to receive changes. Run a given monitor sequentially: overlapping runs with the same ID can race when updating its store. Keep the named store to retain history between runs. The dataset contains each run's results; the named store holds only the latest successful snapshot.

### Pricing

**US$10 per 1,000 successfully checked companies** (US$0.01 per `company-checked` event). You are charged only when the check succeeds, including a valid board with zero openings. `not_found` and `error` results are returned to the dataset without this event charge. Apify platform costs, if applicable to your plan, are separate.

The event is charged before data is added to the dataset. If the spending limit is reached, the Actor stops; a successful report that was not charged is not delivered and does not advance the snapshot.

### Limits and interpretation

- Lever only, including its global and EU instances. A global 404 triggers an EU lookup. Other ATS providers are unsupported.
- At most 500 unique companies per run, processed sequentially; at most one API request per second across pagination, fallback, and companies. Large runs take longer.
- Public postings only. Each page requests 100 postings; collection continues until a shorter page arrives. A 15-second deadline per request, 4 MB per page, or the 1,000-page safety ceiling produces a free error without replacing state. Duplicate IDs also invalidate the collection.
- Lever does not provide an atomic snapshot across pages. Board changes during collection can affect the observed result. Disappearance means a posting left the public API, and does not establish that a candidate was hired.
- Missing category fields are empty strings and count under `unspecified` in summaries. Creation timestamps are ISO formatted. A missing or invalid creation timestamp invalidates the check, preserving state without charging the event.
- Network traffic for collection is restricted to `api.lever.co` and `api.eu.lever.co`; redirects are refused. No arbitrary websites are fetched.

Source: [Lever Postings API documentation](https://github.com/lever/postings-api).

# Actor input Schema

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

Lever company slugs or HTTPS board URLs (jobs.lever.co or jobs.eu.lever.co). Deduplicated; 1–500 unique companies per run. Invalid entries reject the run.

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

Persistent snapshot namespace. Reuse this ID for daily changes. Use different IDs for independent monitors.

## Actor input object example

```json
{
  "companies": [
    "palantir"
  ],
  "monitorId": "default"
}
```

# Actor output Schema

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

One item per company: current Lever jobs, summary and changes since the last successful check.

# 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 = {
    "companies": [
        "palantir"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("prized_rainstorm/hiring-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 = { "companies": ["palantir"] }

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

```

## MCP server setup

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