# Greenhouse Jobs Scraper — official Job Board API, no login (`pappy-dev/greenhouse-jobs`) Actor

Fetch every open job posting from any company's Greenhouse job board (board token) via Greenhouse's official public Job Board API. Title, location, department, office, description HTML, apply URL, published/updated dates. No login, no proxies, one request per board.

- **URL**: https://apify.com/pappy-dev/greenhouse-jobs.md
- **Developed by:** [Backyard Tools](https://apify.com/pappy-dev) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 job posting 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 — official Job Board API, no login

Pull every open job posting from any company that runs its careers page on **Greenhouse**,
using Greenhouse's own public Job Board API. No login, no proxies, nothing to fight — the API exists
so that job posts can be shown on other sites.

### Tested (2026-09-02)

| Board | Jobs returned | Time |
|---|---:|---:|
| `gitlab` | 220 | 0.93s |

One run, all currently open postings of the board.

### Greenhouse jobs — input

```json
{
  "targets": ["gitlab", "stripe"],
  "maxItems": 500
}
```

Each target is the company's Greenhouse board token — the `<...>` part of `job-boards.greenhouse.io/<token>`.
A company that does not use Greenhouse simply returns 0 items (no charge).

### Greenhouse jobs — output fields

One dataset item per job posting:

| Field | |
|---|---|
| `job_id` | Greenhouse job id |
| `title` | job title |
| `company` | company name as shown on the board |
| `location` | location label |
| `department` | first department |
| `office` | first office |
| `url` | public job page |
| `published_at` | first published (ISO 8601) |
| `updated_at` | last updated (ISO 8601) |
| `requisition_id` | company requisition id, if set |
| `language` | posting language code |
| `description_html` | full job description (HTML, as Greenhouse serves it) |

No personal data: these are company job posts, not people.

### Use Cases

- **Hiring-trend tracking** — monitor how many roles a company posts on Greenhouse over time
- **Talent market research** — compare job counts and departments across companies on the same ATS
- **Recruiter lead generation** — surface companies actively hiring in a specific department or office
- **Localization coverage** — the `language` field shows which markets a company is hiring into

### Pricing

Pay per event: **$1.00 per 1,000 job postings** collected. Nothing else.

# Actor input Schema

## `targets` (type: `array`):

会社の Greenhouse ボード名（URL job-boards.greenhouse.io/<token> の <token>。例: gitlab, stripe）。複数指定可

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

1 run で取得する最大件数

## Actor input object example

```json
{
  "targets": [
    "gitlab"
  ],
  "maxItems": 500
}
```

# Actor output Schema

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

取得した各件（type=item）と、選択した分析の結果（type=analysis）

## `overview` (type: `string`):

件数・平均評点・期間・ネガティブ比率（下側信頼限界つき）

# 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 = {
    "targets": [
        "gitlab"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pappy-dev/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 = { "targets": ["gitlab"] }

# Run the Actor and wait for it to finish
run = client.actor("pappy-dev/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 '{
  "targets": [
    "gitlab"
  ]
}' |
apify call pappy-dev/greenhouse-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pappy-dev/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/e08Rb1IwNvM9qOWby/builds/AOhWalU6WKCUTH7O2/openapi.json