# Greenhouse Jobs Scraper - Company Job Board API (`appdata-labs/greenhouse-jobs`) Actor

Get every open job from any company job board hosted on Greenhouse, using the official public board API. Full descriptions as readable text, departments, offices, posting dates and direct apply links. Accepts a company domain — you never need to find the board token yourself.

- **URL**: https://apify.com/appdata-labs/greenhouse-jobs.md
- **Developed by:** [Kobkoon Janngam](https://apify.com/appdata-labs) (community)
- **Categories:** Agents, MCP servers, Jobs
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 job scrapeds

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?

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 Jobs Scraper — Company Job Board API

**Get every open job from any company hiring on Greenhouse.** Built on the official public Job Board API (`boards-api.greenhouse.io`) — the same endpoint the company's own careers page calls — so there is no HTML to break and no login to keep alive.

**Quick start:** press **Start** with no configuration at all. It ships with Stripe and Databricks and returns their open roles immediately. Then paste in the companies you care about.

### Sample output

| company | title | location | department | publishedAt |
|---|---|---|---|---|
| Stripe | Account Executive, AI Sales | San Francisco, CA | Enterprise Sales | 2026-02-03 |
| Stripe | Software Engineer, Payments | Remote - US | Engineering | 2026-07-19 |

Every row also carries `jobId`, `url`, `applyUrl`, `provider`, `boardSlug`, `team`, `employmentType`, `isRemote`, `workplaceType`, `additionalLocations`, `compensation`, `updatedAt`, `descriptionPreview`, `descriptionTruncated` and `descriptionChars`.

### Why this one

**You do not need the board slug.** Most Greenhouse scrapers want the board token out of the URL — something a buyer has to go and find. This one also accepts a plain company domain, derives the slug, and records in the run summary what it resolved to, so your first run hands you the right identifier for every later one.

**Descriptions arrive readable.** Greenhouse returns its job description as HTML wrapped in escaped entities — `&lt;p&gt;` rather than `<p>` — so a naive scraper hands you rows full of visible angle brackets. This one decodes twice, converts block tags to line breaks, and gives you plain text.

**Remote is inferred honestly.** Greenhouse has no remote flag; the location string is the only signal. `isRemote` is `true` when the location says so and **`null` when it is unclear** — never a guessed `false`, because inventing a negative is worse than admitting the source is silent.

**Descriptions sized for an agent.** The full posting text is cut to an 800-character preview with the true length reported in `descriptionChars`, keeping a row under 2 KB so an AI caller can hold a whole board in context. Set `includeFullDescription` when you want everything.

### What you can do with it

- **Track a competitor's hiring.** Schedule it with `postedAfter` set to yesterday and you get only the new openings — the cleanest public signal of where a company is investing.
- **Build a job board.** Point it at a list of companies and you have a live, structured feed with direct apply links.
- **Source by market.** `remoteOnly` plus `locationContains` narrows hundreds of roles to your patch.
- **Feed an AI agent.** Rows are small, identically shaped, and carry a direct apply URL.

### Input

| Field | Default | Notes |
|---|---|---|
| `companies` | Stripe and Databricks | A boards.greenhouse.io URL, a company domain, or the board slug. Mix freely. |
| `titleContains` | empty | Case-insensitive partial match on the job title. |
| `locationContains` | empty | Matches secondary locations too. |
| `department` | empty | Matches department or team. |
| `remoteOnly` | `false` | Keep only remote roles. |
| `postedAfter` | empty | `YYYY-MM-DD`. The most useful filter for a scheduled run. |
| `includeFullDescription` | `false` | Full posting text instead of a preview. |
| `maxJobsPerCompany` | `100` | Applied after filtering. |

Passing a board URL from a *different* ATS is refused by name rather than quietly read as some other company that happens to share a slug. If you want that flexibility, use the **ATS Jobs Scraper**, which detects the provider for you.

### How it works, and why it keeps working

This Actor reads the official public Job Board API (`boards-api.greenhouse.io`): public, keyless, and returning JSON. No HTML parsing, no login, no proxy. Greenhouse can redesign every careers page it hosts and this Actor keeps returning the same fields — which is why it is not on the maintenance treadmill that breaks most job scrapers.

### Limits worth knowing before you buy

Greenhouse serves a board's entire job list in one response and does not paginate, so a very large board is one big request — Stripe's 592 open roles came to 4.5 MB with descriptions attached. `maxJobsPerCompany` caps what you are charged for, not what is downloaded.

The slug is derived from the domain, which is right far more often than not but not always. A company whose board is named differently needs its board URL or exact slug, and the run says plainly which entries did not resolve rather than returning a quiet empty result.

### Pricing

Pay per job delivered, after filtering. A company with no matching openings charges you nothing.

### Disclaimer

This is an **unofficial** tool. It is not affiliated with, authorised by, endorsed by, or in
any way officially connected to Greenhouse Software or any company whose job board it reads.
"Greenhouse" is a trademark of its respective owner.

It reads only the **public, unauthenticated** job-board API — the same endpoint a company's
own careers page calls to render publicly advertised vacancies. It signs into nothing,
stores no credentials, and returns nothing behind a login or a paywall. No candidate or
applicant data is accessed; job postings are, by definition, published to be read.

Greenhouse can change or withdraw this endpoint at any time. When a board cannot be read,
this Actor says which company and why rather than handing you an empty result that looks
like an answer.

# Actor input Schema

## `companies` (type: `array`):

Companies whose Greenhouse board should be read. Each entry can be a boards.greenhouse.io URL, a company domain such as stripe.com, or the board slug itself. Domains are converted to a slug, which is right far more often than not.

## `titleContains` (type: `string`):

Keep only jobs whose title contains this text, case-insensitive. Leave empty for every open role. Example: "engineer" matches "Senior Engineer" and "Engineering Manager".

## `locationContains` (type: `string`):

Keep only jobs whose location contains this text, case-insensitive. Secondary locations count too, so "London" still matches a role listed in both Stockholm and London.

## `department` (type: `string`):

Keep only jobs in a matching department or team, case-insensitive and partial. Departments are the company’s own labels, so "engineering" is a safer filter than an exact team name.

## `remoteOnly` (type: `boolean`):

Keep only remote roles. The three providers express this differently — Ashby has a flag, Lever has a workplace type, Greenhouse has only the location text — so all three signals are checked.

## `postedAfter` (type: `string`):

Keep only jobs published on or after this date, as YYYY-MM-DD. The single most useful filter for a scheduled run: set it to yesterday and you get just the new openings.

## `includeFullDescription` (type: `boolean`):

Off by default. Descriptions run to several thousand characters, which makes a row too big for an AI agent to read comfortably. Off, you get an 800-character preview plus the true length; on, you get the whole thing.

## `maxJobsPerCompany` (type: `integer`):

How many jobs to return for each company, after filtering. Boards can be large — Stripe had 592 open roles when this Actor was written — so this keeps a default run fast and cheap.

## Actor input object example

```json
{
  "companies": [
    "stripe",
    "https://boards.greenhouse.io/databricks",
    "stripe.com"
  ],
  "titleContains": "engineer",
  "locationContains": "London",
  "department": "engineering",
  "remoteOnly": false,
  "postedAfter": "2026-08-01",
  "includeFullDescription": false,
  "maxJobsPerCompany": 100
}
```

# Actor output Schema

## `rows` (type: `string`):

One row per open job: title, company, location, department, employment type, remote flag, posting date, a direct apply link and the description.

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

Which companies resolved to which ATS, how many jobs each returned, and what the filters removed.

# 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 = {
    "companies": [
        "stripe",
        "databricks"
    ],
    "titleContains": "",
    "locationContains": "",
    "department": "",
    "remoteOnly": false,
    "postedAfter": "",
    "includeFullDescription": false,
    "maxJobsPerCompany": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("appdata-labs/greenhouse-jobs").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 = {
    "companies": [
        "stripe",
        "databricks",
    ],
    "titleContains": "",
    "locationContains": "",
    "department": "",
    "remoteOnly": False,
    "postedAfter": "",
    "includeFullDescription": False,
    "maxJobsPerCompany": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("appdata-labs/greenhouse-jobs").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 '{
  "companies": [
    "stripe",
    "databricks"
  ],
  "titleContains": "",
  "locationContains": "",
  "department": "",
  "remoteOnly": false,
  "postedAfter": "",
  "includeFullDescription": false,
  "maxJobsPerCompany": 100
}' |
apify call appdata-labs/greenhouse-jobs --silent --output-dataset

```

## MCP server setup

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

```

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/feKifqQSZG7AQoohH/builds/BLE4uJlbOdO1AGKXu/openapi.json