Stale Job Listing Checker — Greenhouse, Lever & Ashby avatar

Stale Job Listing Checker — Greenhouse, Lever & Ashby

Pricing

$50.00 / 1,000 delivered audits

Go to Apify Store
Stale Job Listing Checker — Greenhouse, Lever & Ashby

Stale Job Listing Checker — Greenhouse, Lever & Ashby

Audit existing job URLs against live ATS boards. Find missing listings and stale titles in one grouped check, independent of your original scraper. $0.05 per audit, up to 5,000 jobs.

Pricing

$50.00 / 1,000 delivered audits

Rating

0.0

(0)

Developer

Typed Diff

Typed Diff

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Check whether the jobs in your catalog are still listed

Audit existing job URLs against current Greenhouse, Lever and Ashby public job feeds. Get a review queue of listings that are no longer present, listings marked unlisted, and titles or locations that have changed.

Paste your catalog's job URLs and run. The Actor groups them by company board, so 1,000 jobs at one company are checked against one board snapshot instead of making 1,000 separate page requests. Lever boards are read page by page.

Why use this job listing status checker?

Job boards and recruiting pipelines often collect listings from multiple suppliers. A supplier-specific expired-ID feed cannot reconcile another supplier's IDs, and an HTTP 200 response does not prove a job is still listed. This Actor uses the original public ATS job URL and current board membership. It works on demand, with no monthly subscription or third-party API key.

Use Apify's API to connect it to a catalog pipeline, or schedule an Apify task to recheck the same URLs. Your source catalog is never modified. Review the output before changing or removing listings.

How to use it

  1. Replace the example with job URLs from your catalog.
  2. Optionally supply each URL as an object with your stored title and location.
  3. Run the Actor and filter the results by reviewRequired.
  4. Export the dataset in JSON, CSV or Excel, or retrieve it through the Apify API.

Input

{
"jobs": [
{
"url": "https://jobs.ashbyhq.com/ashby/390e266b-4b6c-4490-ad74-05ff5e0bb36a",
"title": "Product Manager, Onboarding and Growth"
}
]
}

Supports Greenhouse boards.greenhouse.io and job-boards.greenhouse.io, Lever jobs.lever.co and jobs.eu.lever.co, and Ashby jobs.ashbyhq.com. Provide job URLs, not company homepages. Limits: 5,000 input jobs, 20 company boards, 10,000 source jobs per board and 12 MB per source response. Larger or incomplete responses are reported as unknown, never silently truncated into missing-job results.

Output

FieldMeaning
statuslisted, unlisted, not_listed, or unknown
currentTitle, currentLocationCurrent source values, when found
titleChanged, locationChangedComparisons when the corresponding catalog value was supplied
reasonWhy this result was produced
sourceUrl, sourceJobCount, checkedAtEvidence for the board snapshot
reviewRequiredTrue for missing, unlisted or unverifiable listings

Input order and duplicate catalog rows are preserved so you can join the results back to your own records using inputIndex. A full report is also saved under OUTPUT in the run's key-value store.

Price

$0.05 per delivered audit, covering up to 5,000 input jobs across 20 company boards. One event per run, regardless of how many changed or missing listings are found. Invalid input and runs where no board can be verified do not incur the audit event. An audit with some unavailable boards still costs $0.05; those jobs are explicitly marked unknown. Platform usage is included under the published pay-per-event model.

Interpretation and support

not_listed means absent from the public feed at the check time. It is a review signal, not proof that the employer filled the role: a job may become private, move boards, or temporarily disappear. unlisted is an explicit Ashby listing flag; the direct application link may still work. listed is not a guarantee that applications will be accepted.

The Actor checks the public APIs documented by Greenhouse, Lever, and Ashby. It does not log in, submit applications, bypass blocks, or use residential proxies. Board data can change during a check; rerun consequential missing-job findings before making catalog changes. Report unsupported URL formats or source failures in the Issues tab.