# Greenhouse Jobs API (`istenotools/greenhouse-jobs-api`) Actor

Extract normalized public jobs, descriptions, offices, departments, and changes from Greenhouse job boards.

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

## Pricing

from $1.20 / 1,000 greenhouse jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

<p align="center">
  <img src="https://api.apify.com/v2/key-value-stores/28WlO7n0iHj8sJN95/records/actor-icon-greenhouse-jobs-api.png" alt="Greenhouse Jobs API icon" width="180">
</p>

> **Unofficial independent tool.** Not affiliated with or endorsed by Greenhouse Software, Inc.
> The Greenhouse name identifies compatible public job-board URLs only.

Extract public Greenhouse jobs from one or many company boards into a clean dataset. Run current
snapshots or monitor added, updated, and removed hiring signals—without a login or private API key.

### Best for

- Recruiting and job-search products
- Hiring-signal lead generation
- Company and competitor hiring trackers
- Search indexes, alerts, and research datasets

### What you get

- Stable job and content fingerprints
- Company, title, office/location, department, employment type, dates, and application URL
- Plain-text and HTML descriptions when requested
- Keyword, location, department, remote, and date filters
- Exact `maxItems` result and spend control
- Persistent change monitoring with false-removal protection when a board fails

### Run it

```json
{
  "startUrls": [
    { "url": "https://boards.greenhouse.io/greenhouse" }
  ],
  "maxItems": 1000,
  "mode": "snapshot",
  "includeDescription": true
}
```

The board token is read from standard Greenhouse board and Job Board API URLs. You may add several
boards in one run.

### Monitor changes

Set `"mode": "changes"` and schedule the same input. The first changes run emits current jobs as
`added`; later runs emit only meaningful content changes and removals from healthy boards. A failed
board is retained in state and cannot create a paid removal flood.

Every default-dataset item is one normalized public Greenhouse job or one job-change event.
Diagnostics and source failures are stored in the unpaid `OUTPUT` record.

### Cost and reliability

`maxItems` is a hard result cap. Apify shows the active price before the run and its maximum total
charge setting remains authoritative. Temporary board failures are reported in `OUTPUT`; they do
not generate a paid removal flood.

### FAQ

**Does it need Greenhouse credentials?** No. It reads published Job Board data only.

**Can one run process multiple companies?** Yes. Add multiple public board URLs.

**Does it apply to jobs or access candidates?** No.

Only published Job Board data is read. The Actor does not submit applications or access
candidates, resumes, private jobs, customer accounts, cookies, or API keys.

# Actor input Schema

## `startUrls` (type: `array`):

Add one or more public Greenhouse job-board URLs. HTTPS only.

## `sources` (type: `array`):

Optional advanced source objects with url, provider, companyName, and label.

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

Hard cap across all sources. One default-dataset item is one chargeable result.

## `mode` (type: `string`):

Snapshot emits current jobs. Changes emits only added, updated, and removed jobs versus saved state.

## `stateStoreName` (type: `string`):

Optional stable key-value store name. If omitted, one is derived from sources and filters.

## `titleKeywords` (type: `array`):

Emit jobs whose title contains at least one term. Leave empty for all titles.

## `excludeTitleKeywords` (type: `array`):

Drop jobs whose title contains any term.

## `locations` (type: `array`):

Case-insensitive location substrings. Leave empty for every location.

## `departments` (type: `array`):

Case-insensitive department substrings. Leave empty for every department.

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

Emit only records identified as remote or hybrid.

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

Optional ISO date in YYYY-MM-DD format.

## `includeDescription` (type: `boolean`):

Fetch and normalize descriptions when the source exposes them.

## `includeCompensation` (type: `boolean`):

Include public salary or compensation fields when the source exposes them.

## `maxConcurrency` (type: `integer`):

Bounded request concurrency across sources and detail pages.

## `requestTimeoutSecs` (type: `integer`):

Maximum time allowed for each source request.

## `retryCount` (type: `integer`):

Retries timeout, rate-limit, and server errors with backoff.

## `failOnSourceError` (type: `boolean`):

When disabled, healthy sources still return results and failed sources cannot create false removals.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://boards.greenhouse.io/greenhouse"
    }
  ],
  "sources": [],
  "maxItems": 1000,
  "mode": "snapshot",
  "titleKeywords": [],
  "excludeTitleKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "includeDescription": true,
  "includeCompensation": true,
  "maxConcurrency": 5,
  "requestTimeoutSecs": 30,
  "retryCount": 2,
  "failOnSourceError": false
}
```

# Actor output Schema

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

No description

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

No description

# 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 = {
    "startUrls": [
        {
            "url": "https://boards.greenhouse.io/greenhouse"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("istenotools/greenhouse-jobs-api").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 = { "startUrls": [{ "url": "https://boards.greenhouse.io/greenhouse" }] }

# Run the Actor and wait for it to finish
run = client.actor("istenotools/greenhouse-jobs-api").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 '{
  "startUrls": [
    {
      "url": "https://boards.greenhouse.io/greenhouse"
    }
  ]
}' |
apify call istenotools/greenhouse-jobs-api --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/OkHHWbK3PqruclbTU/builds/nxeuKq07JfIYGEiAx/openapi.json