# Greenhouse & Lever Job Status Checker (`dataassetlab/greenhouse-lever-job-status-checker`) Actor

Recheck up to 100 Greenhouse and Lever job URLs per run. Identify publicly listed or missing postings, with timestamps and API evidence. Export JSON or CSV for job-board maintenance and recruitment workflows. Unsupported links and inconclusive checks are reported separately.

- **URL**: https://apify.com/dataassetlab/greenhouse-lever-job-status-checker.md
- **Developed by:** [Rafael](https://apify.com/dataassetlab) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 verified job statuses

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

## Greenhouse & Lever Job Status Checker

Recheck saved job URLs before displaying them on a job board, sending them to candidates, or importing them into a recruitment workflow. This Actor checks public Greenhouse and Lever posting APIs and returns a timestamped status with supporting HTTP evidence.

### Quick start

1. Paste 1–100 supported job URLs into the input.
2. Start the Actor. No employer API key or login is needed.
3. Open Output for the results. Export JSON or CSV, or retrieve RESULTS_CSV and SUMMARY from the run’s key-value store.

```json
{
  "urls": [
    "https://job-boards.greenhouse.io/stripe/jobs/8172487",
    "https://jobs.lever.co/spotify/2a55d6c9-c564-443a-be3e-a3851db5a93b"
  ]
}
```

These are real example URLs; their status can change after publication. Substitute the links you need to check.

### Supported URLs

- `https://job-boards.greenhouse.io/{board}/jobs/{id}`
- `https://boards.greenhouse.io/{board}/jobs/{id}`
- `https://jobs.lever.co/{board}/{job-id}`
- `https://jobs.eu.lever.co/{board}/{job-id}`

Lever links ending in `/apply` are also supported. Tracking query parameters are accepted. Company-owned career domains, LinkedIn, Indeed, Workday and iCIMS URLs are not supported. The European Lever endpoint is supported by the parser but has not yet been validated with a live posting in this prototype.

### Interpret the result

| Status | Meaning | Suggested next step |
| --- | --- | --- |
| `open` | The provider returned a public posting with a matching ID and a nonempty title. | Keep as publicly listed; this does not prove that hiring is still active. |
| `not_listed` | Two detail requests returned 404 and a complete, healthy, nonempty board list did not contain the ID. | Review or suppress the link; do not describe the role as filled. |
| `unknown` | The check was inconclusive, including provider errors, blocking, empty or incomplete board responses. | Keep the previous status and retry later. |
| `input_error` | The supplied URL is unsupported or invalid. | Supply a supported hosted posting URL. |

A missing posting does not prove the URL ever existed, the job was filled, or the job is absent from other boards. This tool reports public listing availability, not hiring decisions or job authenticity.

### Output fields

Each result includes `inputUrl`, `status`, `reasonCode`, `provider`, `board`, `jobId`, `title`, `checkedAt`, `evidence` and `version`. Depending on the outcome it may also include `message` or `boardPostCount`. Evidence contains the requested public API URL, HTTP status and any transport error. Timestamps use UTC.

`RESULTS_CSV` provides a downloadable CSV. `SUMMARY` includes result counts and the number of HTTP requests. Identical input strings (after trimming surrounding whitespace) produce one result and at most one charge within a run. Distinct URL variants may be checked separately.

### Limits and operational behavior

- Maximum 100 input URLs per run. Start with a small batch.
- Requests are sequential, with at least 0.5 seconds between requests to the same API host and a 15-second request timeout.
- A missing posting may require multiple requests and a paginated board lookup. Lever board confirmation is capped at 20 pages of 100 entries; incomplete confirmation returns `unknown`.
- HTTP 403 or 429 stops further requests to that host for the remainder of the run. There is no proxy rotation or access-control bypass.
- There is no historical database or automatic comparison between runs.
- Each completed result is saved immediately to the dataset. CSV and summary are checkpointed after each result. An abrupt termination may leave the CSV or summary behind the dataset.
- The Actor reads public posting endpoints only. It does not apply for jobs or access applicant records.

### Pricing and spending limits

The listed price is $3 per 1,000 conclusive checks ($0.003 each). Only `open` and `not_listed` results trigger the `verified-job` event. `unknown` and `input_error` results are not charged. There is no start fee. Refer to the current Store pricing for the effective price.

The Actor stops before checking another URL when the remaining run budget cannot cover one conclusive result. Later inputs may remain unchecked. `SUMMARY.stoppedAtSpendingLimit` reports this condition. Repeated URLs across separate runs are checked and may be charged again.

### Current release

Initial release. The cloud smoke test on 25 October 2026 completed with two publicly listed postings, one deliberately nonexistent ID classified as `not_listed`, and one unsupported URL classified as `input_error`. This small test does not establish accuracy across every employer or provider condition.

No affiliation with Greenhouse, Lever, Stripe or Spotify is implied.

# Actor input Schema

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

1–100 HTTPS posting URLs. Custom company career domains are unsupported. Replace the examples with your saved URLs.

## Actor input object example

```json
{
  "urls": [
    "https://job-boards.greenhouse.io/stripe/jobs/8172487",
    "https://jobs.lever.co/spotify/2a55d6c9-c564-443a-be3e-a3851db5a93b"
  ]
}
```

# Actor output Schema

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

No description

## `files` (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/stripe/jobs/8172487",
        "https://jobs.lever.co/spotify/2a55d6c9-c564-443a-be3e-a3851db5a93b"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dataassetlab/greenhouse-lever-job-status-checker").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/stripe/jobs/8172487",
        "https://jobs.lever.co/spotify/2a55d6c9-c564-443a-be3e-a3851db5a93b",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dataassetlab/greenhouse-lever-job-status-checker").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/stripe/jobs/8172487",
    "https://jobs.lever.co/spotify/2a55d6c9-c564-443a-be3e-a3851db5a93b"
  ]
}' |
apify call dataassetlab/greenhouse-lever-job-status-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dataassetlab/greenhouse-lever-job-status-checker"
        }
    }
}
```

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/NxbJ8D4XuYphDNibP/builds/M1aMLkP9M3HHBQ6m6/openapi.json