# Greenhouse Jobs Tracker (`boldprotocol/jobs-greenhouse`) Actor

Track every job opening at the companies you care about - and see only the ones that are new. One schema across every ATS (Greenhouse, Lever, Ashby, Workday, RemoteOK, Indeed...), deduplicated, with a persistent checkpoint so reruns return only fresh openings.

- **URL**: https://apify.com/boldprotocol/jobs-greenhouse.md
- **Developed by:** [Auralis Studio](https://apify.com/boldprotocol) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 53.8% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.50 / 1,000 one result (per result)s

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 Jobs Tracker

Track every job opening at the companies you care about - and see only the ones that are new.

#### What you get that you cannot get any other way

One schema across every ATS (Greenhouse, Lever, Ashby, Workday, RemoteOK, Indeed...), deduplicated, with a persistent checkpoint so reruns return only fresh openings instead of the same board over and over.

- **Delivered:** job title, company, location, department, apply URL and a per-company board tag
- **Format:** one flat JSON row per result, in the dataset - export to CSV/Excel/JSON in one click
- **Pricing:** pay per result. No compute units, no surprise invoices - if a run returns nothing, you pay nothing
- **Runs your way:** on demand, on a schedule, or from your own code via the API

#### How to use it

1. Open the Actor in Apify Console and press **Try for free**, or paste the input below.
2. Set the options that matter - the input schema documents every field.
3. Run it. Results appear in the **Dataset** tab and under **Output**, one row per result.

```json
{
  "companyBoards": ["airbnb", "stripe", "databricks"],
  "maxItems": 5
}
```

Use the board token from a Greenhouse board URL (`boards.greenhouse.io/<token>`) or paste the full URL into `boardUrls`. The three default boards are just examples - replace them with the companies you follow.

Add `keyword` to keep only matching job titles and `location` to keep only matching locations:

```json
{
  "companyBoards": ["stripe"],
  "keyword": "engineer",
  "location": "remote",
  "maxItems": 20
}
```

#### Input reference

| Field | Type | Notes |
|---|---|---|
| `companyBoards` | string\[] | Board tokens such as `airbnb`, `stripe`, `databricks` |
| `boardUrls` | string\[] | Full board or API URLs; the token is extracted automatically |
| `keyword` | string | Case-insensitive filter on the job title |
| `location` | string | Case-insensitive filter on the job location |
| `maxItems` | integer | Total results per run, default 50, max 5000 |
| `proxy` | object | Off by default; this source does not need one |

#### Output

Every row is flat JSON and always carries `url` and `scrapedAt`:

```json
{
  "board": "airbnb",
  "jobId": "8231416",
  "title": "Associate Principal, Procurement Innovation",
  "location": "United States",
  "department": "Financial Planning and Analysis",
  "company": "Airbnb",
  "url": "https://careers.airbnb.com/positions/8231416?gh_jid=8231416",
  "absoluteUrl": "https://careers.airbnb.com/positions/8231416?gh_jid=8231416",
  "updatedAt": "2026-09-29T20:00:54-04:00",
  "scrapedAt": "2026-10-31T03:04:55+00:00"
}
```

#### Why run it on Apify instead of doing it yourself

- **Reliability** - retries, backoff, proxy rotation and polite crawling are handled for you, so a run does not die halfway.
- **Scheduling and history** - run it every hour and keep only what is new; the Actor remembers what it already returned.
- **One API** - the same Actor is available from the API, from a scheduled task, and to AI agents over MCP.
- **Integrations** - Google Sheets, Slack, Airtable, webhooks, n8n, Zapier and Make work out of the box.

#### Built for reliability

Every row is validated before it is published, every row carries `url` and `scrapedAt`, and a checkpoint means a rerun returns only what changed. Fields the source does not publish are left empty rather than guessed.

#### Troubleshooting

- **No results** - check that your board tokens or filters match the source and lower `maxItems` to test quickly.
- **Blocked or slow** - the Actor already retries and rotates; reduce the batch size or slow the interval.
- **Duplicate rows** - the Actor keeps a `seen_urls` checkpoint, so reruns skip what it already returned.
- **A board returns nothing** - the board may have moved off Greenhouse; the run continues with the remaining boards.

#### Something missing?

Open the **Issues** tab on the Actor page and tell us what you need - we ship fixes for the whole fleet.

# Actor input Schema

## `companyBoards` (type: `array`):

Greenhouse board tokens, one per line. Find the token in the board URL: boards.greenhouse.io/<token>. Example: airbnb, stripe, databricks.

## `boardUrls` (type: `array`):

Full Greenhouse board URLs, one per line, e.g. https://boards.greenhouse.io/airbnb. Use this instead of companyBoards if you have URLs.

## `keyword` (type: `string`):

Only return jobs whose title contains this text (case-insensitive). Leave empty to return every job.

## `location` (type: `string`):

Only return jobs whose location contains this text (case-insensitive). Leave empty to return every location.

## `maxItems` (type: `integer`):

Maximum number of new jobs to return in one run (1-5000).

## `proxy` (type: `object`):

Apify Proxy settings. Disabled by default - this source is an open API and does not need a proxy. Residential proxy costs $8/GB and is paid by the Actor developer, so use datacenter unless blocking forces it.

## Actor input object example

```json
{
  "companyBoards": [
    "airbnb",
    "stripe",
    "databricks"
  ],
  "boardUrls": [],
  "keyword": "",
  "location": "",
  "maxItems": 5,
  "proxy": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `items` (type: `string`):

Greenhouse company boards - one item per extracted result, in the default dataset.

## `checkpoint` (type: `string`):

Identifiers already returned by previous runs, so reruns skip them.

# 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 = {
    "companyBoards": [
        "airbnb",
        "stripe",
        "databricks"
    ],
    "boardUrls": [],
    "keyword": "",
    "location": "",
    "maxItems": 5,
    "proxy": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("boldprotocol/jobs-greenhouse").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 = {
    "companyBoards": [
        "airbnb",
        "stripe",
        "databricks",
    ],
    "boardUrls": [],
    "keyword": "",
    "location": "",
    "maxItems": 5,
    "proxy": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("boldprotocol/jobs-greenhouse").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 '{
  "companyBoards": [
    "airbnb",
    "stripe",
    "databricks"
  ],
  "boardUrls": [],
  "keyword": "",
  "location": "",
  "maxItems": 5,
  "proxy": {
    "useApifyProxy": false
  }
}' |
apify call boldprotocol/jobs-greenhouse --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,boldprotocol/jobs-greenhouse"
        }
    }
}
```

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/dvktVEDIIdduOcw7n/builds/OWWnRrvbfBgFOYCrZ/openapi.json