ATS Job & Salary Change Monitor

Know what changed in an employer's job board without rebuilding three API integrations.

Turn public Greenhouse, Lever and Ashby postings into one consistent feed. Compare a previous run to see exactly which title, location, remote condition or published salary range changed. Each result includes the original job link and observation time.

What you can do with it

• Job-board operators: refresh a selected employer list with normalized records instead of maintaining three connectors.
• Recruiting researchers: review newly observed roles and location changes in one spreadsheet.
• Compensation analysts: compare published salary ranges with the previous observation, preserving currency and pay period.

These are public hiring signals, not verified purchasing intent or personal contact leads. No candidate records are collected.

Try a small run

{"boards":["ashby:Ashby"],"maxJobsPerBoard":5,"maxResults":5}

Five delivered jobs cost $0.015, plus the displayed Actor start charge. Source data and results can change. No source account, proxy subscription or separate API key is required.

Use board URLs such as https://jobs.lever.co/spotify, https://jobs.ashbyhq.com/Ashby or https://job-boards.greenhouse.io/stripe. Lever's EU region is supported with lever-eu:board. Use board identifiers exactly as the employer publishes them.

Compare two runs

1. Run once to create a baseline. The run stores a SNAPSHOT file in its default key-value store.
2. Copy that run's key-value store ID into previousSnapshotStoreId. Keep the boards and filters the same.
3. Enable changesOnly to deliver only new or changed observations. Your scheduled workflow must pass the preceding run's store ID each time; this is not an automatic daily subscription.

A salary change appears as a structured before/after entry in changes, with changeType: "changed" and changedFields: ["salaryComponents"]. This describes a comparison feature, not a claim that a particular employer changed pay.

New means first seen in the supplied snapshot, not posted today. Missing jobs are never labeled closed. A capped baseline can make previously unseen jobs appear new on a later run. Use sufficient caps and read SUMMARY before interpreting coverage.

Output you can use immediately

Field	Meaning
title, employerBoard, location	Source-backed job identity and location
salaryComponents	Published salary amounts, currency and interval; an empty array means unavailable
remoteExplicit	true / false / null; no guessing from the title
sourceUrl, applyUrl	Employer's original public links
changeType, changes	New, changed or unchanged; field-level before/after values
firstObservedAt, observedAt	This workflow's observation times
warnings	Missing fields and publication-date caveats

The dataset contains delivered results. OUTPUT-CSV is UTF-8 and spreadsheet-formula-safe; JSON retains original text. SUMMARY reports sources, caps, errors and coverage. DELIVERY reports export completeness. SNAPSHOT supports your next comparison.

Pricing and limits

$3 per 1,000 delivered jobs ($0.003 each), plus the displayed Actor start charge. This is pay per event; platform usage is included in this Actor's price. There is no monthly rental. Set Apify's maximum charge and the input caps before starting. Unchanged jobs suppressed by changesOnly are not charged as delivered jobs. The start charge may apply even when no jobs match.

Up to 20 boards, 500 delivered jobs per board and 1,000 delivered jobs per run. Default: up to 20 per board / 60 total. Collection is bounded to about 90 seconds, with explicit partial results when limits or source errors intervene. Snapshots retain up to 10,000 recent records. A source request is limited to 15 MB; unsupported or changed schemas fail explicitly.

Structured salary is available only when the employer publishes supported fields in Ashby or Lever. Greenhouse salaries embedded in descriptions are not extracted. Ashby's date means last publication, not original creation. No job descriptions, applicants, email addresses or salary estimates are delivered. Access errors and rate limits are respected; there is no login or anti-bot bypass.

Automation and source documentation

Run through Apify Console, API, schedules or your existing workflow. Each run fetches current source data; the Actor does not maintain a global daily dataset. Retention follows your Apify account settings. You control reuse of the public data and must respect source terms and applicable rights.

Sources: Greenhouse Job Board API, Lever Postings API, Ashby public job posting API. Independent tool by Tender Delta; not affiliated with those providers.

For a reproducible issue, use this Actor's Issues tab with the input and a redacted run link. Never include credentials or applicant data.