# Lever Jobs Monitor PL/DE (`danielmichalek/lever-jobs-monitor-pl-de`) Actor

Monitor explicit Lever employer boards for jobs in Poland and Germany. Get source-backed locations, only published salaries, new/changed jobs and repeated-absence evidence. Includes coverage reports and reusable snapshots; no inferred pay or remote eligibility.

- **URL**: https://apify.com/danielmichalek/lever-jobs-monitor-pl-de.md
- **Developed by:** [Daniel Michałek](https://apify.com/danielmichalek) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 qualified job observations

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 Jobs Monitor PL/DE

Monitor a supplied list of public employer boards hosted on Lever. Get current jobs whose **published country field is PL or DE**, source salary ranges when present, and evidence of changes or repeated absence. This Actor does not discover employers or cover the whole Polish/German job market.

**One delivered current job observation is one billable event, including jobs labeled `unchanged`. See the Pricing tab for the active price; at $0.003 per observation, eight delivered observations cost $0.024.** There is no startup fee, charge for errors, or charge for zero matching observations. Changes, coverage summaries and snapshots are free key-value outputs. The platform's active price governs a run; this version refuses prices above $0.003 or positive automatic fees.

### Start with your employer boards

```json
{
  "boards": [
    {"site": "aircall", "region": "global"},
    {"site": "palantir", "region": "global"},
    {"site": "spotify", "region": "global"}
  ],
  "countries": ["PL", "DE"],
  "maxPagesPerBoard": 10,
  "maxResults": 100,
  "minimumMissingHours": 6
}
```

`site` is the identifier in the employer's Lever board URL. Use `global` for `jobs.lever.co`, or `eu` for `jobs.eu.lever.co`. API endpoints are fixed; arbitrary URLs, login and candidate/application access are unavailable. A board returning 404 is an error, not an empty result.

Changes and snapshots do not duplicate the full current job payload. Snapshots carry hashes for comparison; their checksum detects corruption but does not authenticate a customer-supplied baseline.

For later comparisons, copy the complete `NEXT_SNAPSHOT` object from the previous run into the optional `previousSnapshot` input. Keep the same boards, countries and minimum missing interval. Omit it to start a fresh baseline. Scheduling remains your choice in Apify; this Actor creates no schedules.

### Run through the API

Use your own token in the `APIFY_TOKEN` environment variable. This example starts a run; use the returned run ID to inspect status and output when it finishes.

```bash
curl --request POST \
  'https://api.apify.com/v2/acts/danielmichalek~lever-jobs-monitor-pl-de/runs?maxTotalChargeUsd=0.03&timeout=240&memory=512' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"boards":[{"site":"aircall","region":"global"},{"site":"palantir","region":"global"},{"site":"spotify","region":"global"}],"countries":["PL","DE"],"maxResults":100}'
```

### What you receive

| Output | Contents | Job event charge |
| --- | --- | --- |
| Default dataset | Current matching job observations; `changeType: current` and `changeSinceSnapshot` | One per delivered row, including `unchanged` |
| `CHANGES` | Compact identity/time/changed-field evidence: `new`, `changed`, `entered_scope`, `left_scope`, `reappeared`, `disappeared` | None |
| `OUTPUT` | Per-board coverage, error/cap status, selected counts, structured salary coverage and billing summary | None |
| `NEXT_SNAPSHOT` | Compact identity, field hashes and state baseline for a later run, when safely available | None |

Each current row has a stable `recordKey` based on region, board and posting ID, the title, raw location/commitment/workplace fields, source link when valid, observation times and salary status. Identity deduplication does not merge similar titles across employers. `firstObservedAt` is the first observation in the supplied baseline history. `sourceCreatedAt` preserves Lever's numeric `createdAt` when supplied. Neither is claimed as publication date; `publicationDate` stays null.

Salary comes only from the optional structured `salaryRange`. It is not extracted from descriptions, inferred, converted or assigned a tax basis. `salaryStatus` distinguishes `published`, `not_published` and `invalid_published_value`; unknown salary is null. Commitment and location remain source text. Country selection uses the explicit source `country`, not a city name or inferred remote eligibility. Additional location strings can name other countries without changing the primary published country filter.

### What absence means

A missing job first becomes a pending absence. Only a second complete read of that board, at least `minimumMissingHours` later (minimum and default six), emits `disappeared`. A complete read requires a terminating page and valid unique posting IDs. Failed, capped, malformed or duplicate/racy pagination cannot advance that board's baseline or produce an absence event. Successful boards can advance while a failed board's previous state is preserved.

This is evidence of repeated absence from the published API, **not proof that a vacancy was filled or definitively closed**. Offset pagination is not an atomic source snapshot: undetected source changes between pages remain possible. Two spaced reads reduce false disappearance claims; they do not eliminate them. A published country change is `left_scope`, not closure. Reappearing after confirmed disappearance is labeled `reappeared`.

If current observations, changes, a spending limit or snapshot size truncate the intended result, `NEXT_SNAPSHOT` is withheld. Inspect `OUTPUT.report` before continuing a baseline. Retained historical disappeared entries count toward the snapshot limit; start a fresh baseline when needed and retain old snapshots yourself if useful.

### Bounds and failures

- 1–5 explicit boards; only PL/DE filters; at most 100 postings/page and 10 pages/board.
- 500 delivered observations or change entries; 5,000 entries and 5 MiB per snapshot; 8 MiB per source page and 32 MiB total source bodies per run. Unused HTML/descriptions are discarded after each page.
- Sequential public GETs, redirects refused, 20-second request timeout, a 180-second source budget; at most three attempts for network errors, HTTP 429 or 5xx. Retry-After is honored within the source deadline; waits over 30 seconds stop the board instead of retrying early. Set a platform run timeout of at least 240 seconds to allow output finalization.
- A full 100-row final page needs another page to establish completeness. Lowering the page cap can intentionally yield incomplete coverage.
- `INPUT` rejects invalid bounds, unknown fields, changed snapshot scope or checksum corruption. `HTTP_*`, `PAGE_LIMIT`, `TIME_LIMIT`, `SOURCE_*` and `DUPLICATE_ID` appear in board coverage. No complete board means a failed run with no job events.
- `BILLING_CONFIGURATION` rejects unsupported pricing. The SDK's unpriced shape is accepted only when the SDK explicitly identifies a local runtime; missing cloud pricing fails closed. A zero effective spending limit makes zero source requests and emits zero job events. Partial budgets deliver only the affordable prefix and withhold the next snapshot.
- `RECONCILIATION_REQUIRED` means an interrupted or inconsistent delivery cannot safely be replayed. Writes and charges are not transactional. A durable pending checkpoint blocks automatic replay, including after a lost charge acknowledgement. Inspect the existing dataset and platform charge records before deciding whether to start a separate run; a separate run can bill a fresh observation again.

### Access and evidence

Lever's [official Postings API README](https://github.com/lever/postings-api) explicitly states that published jobs are publicly viewable and may be scraped by third parties. Only those public GET endpoints are used. This is not a blanket license to redistribute employer content. Respect employer content rights and applicable downstream obligations. No full job descriptions, candidate records, contact enrichment, paid API, browser or proxy are used.

On 2026-10-21, a live read through this source adapter covered Aircall (77 postings), Palantir (306) and Spotify (79). Of 462 source postings, eight matched explicit PL/DE countries (one PL, seven DE), with **zero structured salary ranges** in those eight. Spotify legitimately matched zero. These are three source checks, not evidence of comprehensive market coverage or paying demand.

### Local verification

Node 22 or newer. `npm test` uses built-in Node tests and saved source-field fixtures. `npm run verify:live -- /tmp/lever-check.json` performs bounded public GETs through the source adapter and writes a local report; it does not initialize or run an Apify Actor. Normal runtime is `npm start` after `npm ci --omit=dev --ignore-scripts`.

The SDK is pinned to `apify@3.7.2`. Runtime guards check actual dataset contents, the cumulative named-event count delta and the response to each write/charge call. Interrupted delivery stops rather than automatically replaying ambiguous writes or charges.

# Actor input Schema

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

Explicit published Lever board identifiers. No discovery, candidate data or arbitrary URLs.

## `countries` (type: `array`):

Only source country field; city text and remote eligibility do not infer country.

## `maxPagesPerBoard` (type: `integer`):

100 postings/page. A cap without a terminating page means incomplete coverage; no absence inference.

## `maxResults` (type: `integer`):

Output cap. Truncated current rows or changes prevent next-snapshot publication.

## `minimumMissingHours` (type: `integer`):

Two complete reads separated by this period emit disappeared. This does not prove a vacancy was filled.

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

Optional prior NEXT_SNAPSHOT from this Actor with the exact same board/country/absence scope. Omit to start a new baseline.

## Actor input object example

```json
{
  "boards": [
    {
      "site": "aircall",
      "region": "global"
    }
  ],
  "countries": [
    "PL",
    "DE"
  ],
  "maxPagesPerBoard": 10,
  "maxResults": 500,
  "minimumMissingHours": 6
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `report` (type: `string`):

No description

## `changes` (type: `string`):

No description

## `nextSnapshot` (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": [
        {
            "site": "aircall",
            "region": "global"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("danielmichalek/lever-jobs-monitor-pl-de").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": [{
            "site": "aircall",
            "region": "global",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("danielmichalek/lever-jobs-monitor-pl-de").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": [
    {
      "site": "aircall",
      "region": "global"
    }
  ]
}' |
apify call danielmichalek/lever-jobs-monitor-pl-de --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,danielmichalek/lever-jobs-monitor-pl-de"
        }
    }
}
```

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/SnIysl8o1635JE2AG/builds/Gfa4cgzY0e1aLgjMN/openapi.json