# Greenhouse Job Board Scraper (`sourcesauce/greenhouse-job-feeds`) Actor

Fresh job postings straight from Greenhouse-hosted career pages. Full posting content, departments, offices and dates for any company on Greenhouse - compliance-safe output with no personal contact data. Ideal for job-board backfill and hiring-trend analysis.

- **URL**: https://apify.com/sourcesauce/greenhouse-job-feeds.md
- **Developed by:** [Source Sauce](https://apify.com/sourcesauce) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 job postings

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Greenhouse Job Board Scraper

Pull fresh job postings from any **Greenhouse-hosted career page** — the same public
job board API behind `boards.greenhouse.io` and `job-boards.greenhouse.io` company
sites. Give it a list of company board tokens and get every open role as structured
records with the full posting HTML, straight from the source with no database
staleness.

Sample output (live run, 2026-08-04):

| company\_name | title | location | first\_published | updated\_at |
|---|---|---|---|---|
| Stripe | Account Executive, Bridge | London | 2026-07-30 | 2026-08-04 |
| Duolingo | Ad Sales Lead, Central | Remote - Illinois | 2026-07-28 | 2026-07-28 |
| Airtable | Account Executive, SLED | Austin, TX; Remote - US | 2026-01-26 | 2026-06-15 |

Built for **job board backfill**, job aggregator feeds, **hiring trend analysis**,
competitor hiring monitoring, and jobs-posted-by-company datasets. One board = one
company; a watchlist of tokens gives you a daily multi-company feed of open positions.

### Why this one

- **Direct from the API, every run.** No cached database between you and the source —
  `first_published` and `updated_at` come from Greenhouse itself, so freshness is the
  API's, not a crawler's.
- **Compliance-safe by construction.** No hiring-manager names, no AI-extracted
  contact enrichment, no personal data fields — and email addresses / phone numbers
  inside posting text are redacted before delivery. The output schema is a fixed
  allowlist you can audit below.
- **Honest billing.** You pay per delivered job posting. Unknown or dead board tokens
  return an uncharged error row instead of failing the run, so long watchlists are safe.

### Output

| field | type | description |
|---|---|---|
| board\_token | string | The Greenhouse board the posting came from (your input token). |
| id | integer | Greenhouse public job id. |
| internal\_job\_id | integer | Greenhouse internal requisition link id. |
| requisition\_id | string | The employer's own requisition number. |
| title | string | Posting title. |
| company\_name | string | Company name as published on the board. |
| location | string | Posting location line (as the employer wrote it). |
| departments | array of strings | Department names. |
| offices | array of strings | Office names. |
| first\_published | string (ISO datetime) | When the posting first went live. |
| updated\_at | string (ISO datetime) | Last change to the posting. |
| application\_deadline | string or null | Deadline if the employer set one. |
| language | string | Posting language code. |
| absolute\_url | string | The public application URL. |
| content | string (HTML) | Full posting body, renderable HTML, contacts redacted. |
| content\_chars | integer | Length of the delivered content. |

### Input

| field | required | prefill | description |
|---|---|---|---|
| boardTokens | yes | stripe, duolingo, airtable | Greenhouse board tokens — the company slug in career-page URLs like `boards.greenhouse.io/stripe` or `job-boards.greenhouse.io/<token>`. |
| maxRecords | no | 150 | Stop after this many rows in total (0 = no cap). |

**Finding a board token:** open the company's careers page; if applications go through
Greenhouse the URL contains `boards.greenhouse.io/<token>`, `job-boards.greenhouse.io/<token>`
or `greenhouse.io` embed links with the same slug. The token is usually the company name
in lowercase.

### Notes

- A board token that is not on Greenhouse returns one **uncharged** error row naming the
  token, and the rest of the watchlist still delivers.
- A company with zero open roles is a valid empty result, not an error.
- Postings are delivered per run (stateless). Dedupe across runs on `id` or
  `absolute_url` on your side; `updated_at` tells you what changed.

***

This is an **unofficial** tool and is **not affiliated** with, endorsed or sponsored by
Greenhouse Software, Inc. It reads only the public, unauthenticated Greenhouse Job Board
API and delivers employer-published job postings.

# Actor input Schema

## `boardTokens` (type: `array`):

Greenhouse board tokens — the company slug in careers URLs like boards.greenhouse.io/stripe or job-boards.greenhouse.io/<token>. One board = one company. Unknown tokens return an uncharged error row, so a long watchlist is safe.

## `maxRecords` (type: `integer`):

Stop after this many rows in total (0 = no cap). Postings are charged per delivered record.

## Actor input object example

```json
{
  "boardTokens": [
    "stripe",
    "duolingo",
    "airtable"
  ],
  "maxRecords": 150
}
```

# 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 = {
    "boardTokens": [
        "stripe",
        "duolingo",
        "airtable"
    ],
    "maxRecords": 150
};

// Run the Actor and wait for it to finish
const run = await client.actor("sourcesauce/greenhouse-job-feeds").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 = {
    "boardTokens": [
        "stripe",
        "duolingo",
        "airtable",
    ],
    "maxRecords": 150,
}

# Run the Actor and wait for it to finish
run = client.actor("sourcesauce/greenhouse-job-feeds").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "boardTokens": [
    "stripe",
    "duolingo",
    "airtable"
  ],
  "maxRecords": 150
}' |
apify call sourcesauce/greenhouse-job-feeds --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=sourcesauce/greenhouse-job-feeds",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/J4DHIh62DRvpwjdhz/builds/2zJXOJQVpyUUCflB8/openapi.json