# Career Board Proof — Greenhouse, Lever & Ashby Jobs (`hadi.kanj/career-board-proof`) Actor

Collect employer jobs in one schema. Monitor new jobs, changed fields and no-longer-listed roles after complete scans. Public Greenhouse, Lever and Ashby boards; source-published salary and remote details. Demo: https://market-data-gateway-production-2084.up.railway.app/launch/career-board-proof

- **URL**: https://apify.com/hadi.kanj/career-board-proof.md
- **Developed by:** [Hadi Kanj](https://apify.com/hadi.kanj) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 observed jobs

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

## Career Board Proof — Jobs & Hiring Changes

Get public employer jobs from **Greenhouse, Lever and Ashby** in one consistent format. Schedule repeat runs to detect new roles, changed descriptions or compensation, and roles no longer listed. Designed for niche job boards, recruiting research and employer hiring monitors.

### Quick start

```json
{"boards":[{"provider":"greenhouse","board":"greenhouse"},{"provider":"lever","board":"palantir","region":"global"},{"provider":"ashby","board":"ramp"}],"maxJobs":1000,"stateKey":"employers","onlyChanges":false}
```

Use the employer's slug from `boards.greenhouse.io/{slug}`, `job-boards.greenhouse.io/{slug}`, `jobs.lever.co/{slug}` or `jobs.ashbyhq.com/{slug}`. EU Lever boards use `jobs.eu.lever.co/{slug}` and `region: "eu"`. Custom employer careers domains need their underlying provider and slug; arbitrary website crawling is not included.

1. Add employer boards and run.
2. Download the dataset as JSON, CSV or Excel.
3. Read **Board status** to confirm every requested board was accessible and fully scanned.
4. Schedule the same input and monitor name for changes. The first run establishes `BASELINE` rows.

### Output and useful differences

One row per job, with stable `id`, `provider`, `board`, `region`, `title`, source/apply URLs, primary and additional locations, department, team, employment/workplace type, explicit remote state where available, plain-text description, published/updated dates, compensation, `evidenceUrl`, `observedAt`, `baselineAt` and `changes`.

Compensation preserves the provider's published structure and currency/period when present. Ashby tier components, Lever salary ranges and Greenhouse pay-input ranges are not forced into a misleading annual salary. Missing salary, remote state or publication dates remain unknown. No AI guesses or enrichment credits are required.

Changes are `NEW_JOB`, `JOB_CHANGED` (with changed fields) or `NO_LONGER_LISTED`. The last means absent from a complete public board scan; it does not assert the role was filled. Capped, failed or partial scans never confirm removals or replace a complete baseline. Timestamp-only updates do not count as editorial changes. Monitoring history is isolated per customer and `stateKey`. Ashby jobs explicitly marked unlisted are excluded.

### API

```bash
curl -X POST 'https://api.apify.com/v2/acts/hadi.kanj~career-board-proof/run-sync-get-dataset-items' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"boards":[{"provider":"greenhouse","board":"greenhouse"}],"maxJobs":1000}'
```

Use your own Apify token. For larger runs, start `/runs` asynchronously, poll completion, then fetch `defaultDatasetId` and `defaultKeyValueStoreId`. `SUMMARY` reports per-board status, completeness, pages, observed jobs, errors and baseline updates. Always read it, including when the dataset is empty.

### Pricing and limits

The Store pricing panel is authoritative. Billing is per observed job, including unchanged checks when `onlyChanges` is enabled. All fields are included; errors and confirmed removal records have no job charge. Set **Maximum cost per run**. A budget stop preserves the previous baseline.

Up to 25 boards and 10,000 jobs per board. Uses documented public posting endpoints, not an ATS administration API. No applications, applicant information, LinkedIn scraping, login or credentials. Provider limits, outages, unknown slugs and oversized responses are reported. Sources may change during a multi-page scan; this is a snapshot rather than a transactional export. Recheck the employer before applying.

### Source documentation

[Greenhouse Job Board API](https://docs.greenhouse.io/job-board.html), [Lever Postings API](https://github.com/lever/postings-api), [Ashby Public Job Postings API](https://developers.ashbyhq.com/docs/public-job-posting-api).

### Support

Open an Actor issue with provider, board slug, run ID and unexpected result. Never include credentials or applicant information.

# Actor input Schema

## `boards` (type: `array`):

Choose greenhouse, lever or ashby and the employer's board slug. Lever supports global or eu region.

## `maxJobs` (type: `integer`):

Capped scans cannot confirm removals or replace complete baselines.

## `stateKey` (type: `string`):

Repeat this name to compare jobs across runs. History is private to each Apify user.

## `onlyChanges` (type: `boolean`):

All observed jobs are charged, even when unchanged rows are suppressed.

## Actor input object example

```json
{
  "boards": [
    {
      "provider": "greenhouse",
      "board": "greenhouse"
    }
  ],
  "maxJobs": 1000,
  "stateKey": "default",
  "onlyChanges": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

Normalized source-linked job postings and confirmed listing removals.

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

Per-board completeness, errors, counts and baseline state.

# 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 = {
    "boards": [
        {
            "provider": "greenhouse",
            "board": "greenhouse"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hadi.kanj/career-board-proof").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 = { "boards": [{
            "provider": "greenhouse",
            "board": "greenhouse",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("hadi.kanj/career-board-proof").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 '{
  "boards": [
    {
      "provider": "greenhouse",
      "board": "greenhouse"
    }
  ]
}' |
apify call hadi.kanj/career-board-proof --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hadi.kanj/career-board-proof"
        }
    }
}
```

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/5SZDyRrYwl01AZf4C/builds/bxgkhFXEmev8k85ck/openapi.json