ATS Board Change Monitor

This Actor checks public Greenhouse, Lever, and Ashby job boards and emits deterministic new, changed, and removed records. It uses stable IDs supplied by each ATS, includes compensation only when the board API supplies it, and does not use an LLM at runtime.

Use it to keep a job directory current, track hiring changes at a company list, or feed a recruitment research workflow. Supply the board handles you want to follow. The Actor does not discover companies or send applications.

Quick start

Create a baseline with this input:

{"boards":[{"provider":"ashby","slug":"Ashby"}],"baseline":true}

Open the run's key-value store and retrieve SNAPSHOT. On the next run, use the same boards, omit baseline, and put that complete object in priorSnapshot. The dataset contains a status row for each checked board and its change events; the key-value store contains the normalized current jobs in SNAPSHOT.

For a recurring API workflow, save each run's SNAPSHOT in your own workflow state and supply it to the next run. The Actor does not automatically retrieve previous runs. You control the polling schedule and the state; no separate language-model API subscription is needed.

The input accepts up to 20 boards. A board is { "provider": "greenhouse|lever|ashby", "slug": "board-handle" }; Lever also accepts "region": "eu". The Actor constructs HTTPS URLs only for the fixed official API hosts. Handles are restricted to simple alphanumeric, underscore, and hyphen characters. Redirects are rejected. Each response is limited to 10 MB, requests time out after 15 seconds, and transient failures receive at most two retries. Lever boards are read in pages of 100, with a 20-page ceiling; a board that reaches this ceiling without a final short page is marked failed. The prior snapshot is capped at 20 MB and the aggregate snapshot and run output are capped at 20 MB and 25 MB respectively.

On the first run, set baseline to true. The Actor stores the current job state without emitting false new events. Copy the SNAPSHOT value from that run's key-value store into priorSnapshot on the next run. The snapshot travels with the caller's input, so separate users and runs do not share mutable named state. Boards omitted from a later input are left in the snapshot unchanged.

Each successful, valid board fetch produces one board-check event, including unchanged or empty boards. Failed fetches and malformed or oversized responses are not charged. A successfully charged board's result is delivered even if that charge reaches the run limit; no further boards are processed. See the Pricing tab for the current price per successful board check.

Removals are generated only after a complete valid jobs list. If a board request, response validation, or charge step fails, its previous job list remains in SNAPSHOT and the output contains a board error. This prevents a temporary outage or malformed response from removing every job. A successful empty list is treated as a complete fetch and can produce removal events.

Normalized fields include stable id and source_id, ATS source, title, location, department/team, employment and workplace type, description when provided by the endpoint, published/updated timestamp, job and application URLs, and optional source compensation. Exact field availability varies by ATS. The Actor does not enrich or infer salary, and Greenhouse list responses generally omit pay ranges.

Sources and limits

• Greenhouse Job Board API
• Lever Postings API
• Ashby Public Job Posting API
• Apify Python SDK pay-per-event guide

Compensation and descriptions depend on source configuration. A valid empty response can indicate a real closure of all jobs; the Actor cannot independently verify the ATS provider's own data. Very large boards may exceed the documented limits and are reported as errors, preserving their previous successful state.