Job Board Delta | Greenhouse, Lever & Ashby Changes

What does Job Board Delta Monitor do?

Get changes between successive public Greenhouse, Lever and Ashby job-board snapshots. Use it to keep a jobs database current or observe changes in hiring activity without writing your own history store.

Quick start

1. Enter a board identifier such as greenhouse:greenhouse or ashby:Ashby.
2. Set a stable monitorId. The first run returns existing listed postings; select baseline to save them silently instead.
3. Repeat with the same input. New postings and edits produce changes. A posting must be missing from two consecutive complete successful checks before it is reported as removed.
4. Save the input as a task and schedule it. Run one copy of each monitor at a time, at least five minutes apart, with a 240-second run timeout.

lever:company uses the global API; lever-eu:company uses the European API. Supply the identifier from the hosted board URL. No account password or API key is needed for these public endpoints. This Actor does not discover company identifiers or search every employer.

Price

$0.01 per successful complete board check ($10 per 1,000). Platform usage is included. Unchanged checks, empty valid boards and initial baselines are charged. HTTP, parsing, incomplete-snapshot and oversized-board failures produce free errors in OUTPUT. The spending limit is checked before fetching the next board. There are no separate Actor-start or dataset-item charges.

One company checked daily for 30 days costs $0.30; ten companies cost $3.00, assuming every check succeeds. This is customer usage pricing, not a promise of publisher income.

Results and history

Each dataset row contains board, checkedAt, currentJobs, changeCount, pendingRemovals and a changes array. Each change includes eventId, type (new/updated/removed), source ID, title, URL, primary location, department, workplace/employment category, a description hash and any published Ashby compensation summary. Missing source fields are empty strings. Full job descriptions are not returned; changes to description text still change its hash. Secondary locations and other unlisted fields are not compared.

OUTPUT contains successfulChecks, changes, errors, stopped and uncheckedBoards. A partial or failed board response never advances its history. An all-source-error run fails with no successful event charges.

Named key-value storage belongs to the customer's account. Reuse the same Actor and monitor ID; a saved task supplies its task ID only when monitorId is omitted. Active and once-missing postings are retained until subsequent complete checks update or remove them. Inactive monitors retain state and can incur platform storage charges; delete their named stores when no longer needed. Changing firstRun does not reset existing history.

Limits

Up to 20 boards per run and 2,000 listed postings per board. Source responses are bounded to 4 MB per request; boards that exceed either bound are rejected without advancing history. Lever pagination can change while being read; duplicate IDs and known incomplete Greenhouse totals are rejected, but no third-party API offers an atomic snapshot guarantee here. Two missing observations reduce false removals but do not prove a role was filled or permanently closed. Use restrained schedules and respect source terms.

No distributed lock or exactly-once delivery is promised. Do not overlap runs for the same monitor. An interruption between dataset delivery and history persistence may replay output; use eventId as a unique key in your destination. Polling can miss changes that happen and revert between observations. No applicant records, private recruiting data, applications or messages are accessed or sent. Independently maintained by sbio-apps; not affiliated with or endorsed by Greenhouse, Lever or Ashby.

Report reproducible problems through this Actor's Issues tab without including private data or credentials.

Input example

{
  "boards": [
    "greenhouse:greenhouse"
  ],
  "monitorId": "hiring-monitor",
  "firstRun": "emit"
}

See the Input tab for all supported fields. Results are available through the dataset API and can be downloaded as JSON, CSV or Excel.

Output fields

Field	Meaning
monitorId	History scope.
board	Provider and company board identifier.
checkedAt	string
status	string
currentJobs	Current listed postings in the complete source snapshot.
changeCount	Number of emitted changes.
pendingRemovals	Postings absent once, awaiting another complete check.
changes	New, updated or twice-absent postings. Removed means absent from two observed snapshots, not confirmed filled.

Output example

Illustrative completed check; exact source values vary.

{
  "monitorId": "hiring-monitor",
  "board": "greenhouse:example",
  "checkedAt": "2026-09-07T12:00:00.000Z",
  "status": "checked",
  "currentJobs": 18,
  "changeCount": 0,
  "pendingRemovals": 0,
  "changes": []
}