# Job Link Verifier — Greenhouse, Lever & Ashby (`busleyden/job-link-verifier`) Actor

Check existing Greenhouse, Lever and Ashby job URLs against current public employer data. Get listed, not\_listed or unknown with source evidence, your row IDs and a review report. Unknown and duplicate rows have no verification event charge.

- **URL**: https://apify.com/busleyden/job-link-verifier.md
- **Developed by:** [Busleyden](https://apify.com/busleyden) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 conclusive job-link checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{
  "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`:

```json
{
  "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.

# Actor input Schema

## `urls` (type: `array`):

Paste up to 2,000 public job URLs hosted by Greenhouse, Lever or Ashby. Standard application links are supported. Custom employer domains and other sites are returned as unknown and are not fetched. Do not include applicant data or private links.

## `jobs` (type: `array`):

Instead of URLs, provide rows such as \[{"id":"my-job-17","url":"https://jobs.lever.co/company/job-id"}]. Your IDs and input order are preserved. Supply either jobs or urls, not both.

## Actor input object example

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

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://job-boards.greenhouse.io/21shares/jobs/5823209004"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("busleyden/job-link-verifier").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://job-boards.greenhouse.io/21shares/jobs/5823209004"] }

# Run the Actor and wait for it to finish
run = client.actor("busleyden/job-link-verifier").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://job-boards.greenhouse.io/21shares/jobs/5823209004"
  ]
}' |
apify call busleyden/job-link-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,busleyden/job-link-verifier"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/s7cgfW8IfA8lp82CG/builds/KatI64Ju80EiDLJ1X/openapi.json