Job Link Verifier — Greenhouse, Lever & Ashby

Check whether an employer still publishes a job before you include its link in your job board, newsletter or alert feed.

Paste your existing job links. Receive a result for each checked row, the public source behind it, the check time, and a suggested next action. You do not need to move your feed to a new jobs database.

What you get

• listed: the job is present in the provider's public data.
• not_listed: the job is absent from an available public source. Review it before your next publication.
• unknown: the source is unavailable, empty, contradictory, unsupported or cannot establish a reliable result. Keep the last known state and review or retry.

Every row includes your original position and optional ID, provider, job ID, normalized link, reason, source URL and check timestamp. A readable HTML report groups the counts and explains the next action. Export the dataset to CSV, Excel or JSON using Apify.

“Not listed” does not mean “filled”. Roles can move, become private or disappear temporarily. A listed result confirms public listing membership; it does not test the application form, prove the employer is actively interviewing, or guarantee the job is suitable. If a published deadline has passed, the result flags it for review even when the source still lists the job.

Start with your links

{
  "urls": [
    "https://job-boards.greenhouse.io/21shares/jobs/5823209004"
  ]
}

The example is a real public URL used during development. Its status can change. Replace it with links from your own feed.

To preserve your own database IDs, use jobs instead of urls:

{
  "jobs": [
    {"id": "feed-row-17", "url": "https://job-boards.greenhouse.io/21shares/jobs/5823209004"}
  ]
}

Supply either field, not both. Each run accepts up to 2,000 links. Your maximum run charge may limit the number checked; the summary records the number returned and remaining. Split larger feeds into batches.

Supported URLs

Provider	URL forms
Greenhouse	boards.greenhouse.io/BOARD/jobs/ID, job-boards.greenhouse.io/BOARD/jobs/ID, standard embed/job_app?for=BOARD&token=ID links
Lever	jobs.lever.co/BOARD/UUID, jobs.eu.lever.co/BOARD/UUID, including /apply
Ashby	jobs.ashbyhq.com/BOARD/UUID, including /application

Custom employer domains, LinkedIn/Indeed URLs, shortened links and other providers are not resolved in this version. They return unknown. Tracking parameters do not cause duplicate checks. Input links must use HTTPS and cannot contain credentials.

Fit it into your existing workflow

1. Collect the employer-hosted application links from your current feed.
2. Run this Actor before your next publication or alert batch.
3. Join the output back using rowId, or inputIndex for URL-only input.
4. Keep listed entries. Route absent entries to review. Preserve the last known state for unknown entries.
5. Schedule the Actor at the frequency that fits your publication cycle. Each run is a new snapshot.

Do not automatically delete your database rows based on a single absent result. A moved employer board can otherwise remove legitimate opportunities from your feed.

Pricing and cost control

The job-verified event applies only to a unique conclusive result (listed or not_listed). Unknown results and duplicate links within the same run have no verification event charge. The current event price and any platform usage charges are shown in the Actor's pricing panel before you run it. Set a maximum run charge to control your budget.

The run summary reports returned rows, unique conclusive checks, source requests and any input truncation. Internal test runs are not customer results or evidence of demand.

Privacy and limits

This Actor requests public job-board data from supported providers. It does not log into sites, submit job applications, read candidate profiles, send notifications or follow links to arbitrary destinations. Do not include applicant records, personal notes, passwords or private application URLs.

Inputs, results and the report are stored in your Apify run storage under your account's settings. We do not maintain a separate customer jobs database. Source access can be rate-limited or unavailable; those cases remain unknown. No association with or endorsement by the supported providers or named employers is implied.

Support

Use the Actor's Issues tab for a reproducible problem. Include the run ID, one public example URL and what you expected. Exclude applicant data, credentials and confidential job information. A bug should produce a corrected result or a clearer limitation, not an unsupported certainty.