# Greenhouse Jobs Scraper - Any Company's Job Board (`afterstar/greenhouse-jobs`) Actor

All open jobs from any company's Greenhouse job board, with departments, offices and pay ranges where published.

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

## Pricing

from $1.05 / 1,000 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/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

**Pricing: $1.50 per 1,000 jobs. On a schedule (only new jobs): $0.006 per board checked + $1.50 per 1,000 new, changed or removed jobs.**

### What does Greenhouse Jobs Scraper do?

All open jobs from any company's Greenhouse job board, with departments, offices and pay ranges where published. Every job comes in one clean table: company, title, department, team, locations, remote or on-site,
employment type, salary (where the company publishes it), posting date, the job link, the apply link and the full
description as plain text.

Run it once for a list, or **schedule it to get only the new jobs** each day. The tool remembers what it has seen, so
a daily check costs a fraction of a cent when nothing is new.

### What you get

|  |  |
|---|---|
| **Input** | A Greenhouse board name like `stripe`, or its link https://job-boards.greenhouse.io/stripe |
| **Per job** | Company, title, department, offices, remote where the job says so, pay range where published, dates, job and apply links, description |
| **Schedule** | Only new jobs, or new + changed + removed jobs |
| **Price** | $1.50 per 1,000 jobs; on a schedule $0.006 per board checked |

### Use cases

- Track hiring at your target companies or competitors: new roles, closed roles, pay changes.
- Feed a job board, a newsletter or a Slack channel with fresh openings.
- Sales and recruiting signals: which companies are hiring for what, right now.

### Input

| Field | What it does |
|---|---|
| Greenhouse job boards | One per line: `stripe` or `https://job-boards.greenhouse.io/stripe` |
| Company names | Or type names (Stripe, SpaceX): looked up in our directory of 4,175 public Greenhouse boards |
| Keywords + where to search | Only jobs with these words in the title, or in the title and description |
| Posted after / before | A date window (jobs without a date are kept) |
| Location contains / exclude / remote only | Match the location text and the country the board gives (Germany also matches a board's `DE`); drop places; only remote jobs |
| Minimum salary / only with salary | Filter by the top of the published salary range |
| Max jobs per board | No fixed cap (default 10,000 per board) |
| Output mode | All jobs, only new jobs, or new + changed + removed jobs |

### Output

One row per job, with the same keys for every job system:

```json
{
  "id": "greenhouse:<company>:<job id>",
  "changeType": "new",
  "firstSeenAt": "2026-10-04T19:30:00Z",
  "ats": "greenhouse",
  "company": "…",
  "title": "Senior Backend Engineer",
  "department": "Engineering",
  "locations": ["Berlin, Germany"],
  "remote": true,
  "employmentType": "FullTime",
  "salaryMin": 70000,
  "salaryMax": 90000,
  "salaryCurrency": "EUR",
  "postedAt": "2026-10-01T09:00:00Z",
  "url": "…",
  "applyUrl": "…",
  "descriptionText": "…"
}
```

Every row has every key (`null` when the job system doesn't give a value). `changeType` is `new`, `changed`,
`unchanged` or `removed`; a `changed` row lists `changedFields` and the `previous` values. Emails and phone numbers
inside descriptions are replaced by `[redacted]` unless you switch that off. Rows have no recruiter name or contact
fields.

If a board doesn't exist or doesn't answer, you get one row with `changeType: "status"` and a `statusCode`
(`not_found`, `rate_limited`, `source_error`) instead of an error, and you're not charged for it.

### Schedule it: only new jobs, every day

1. Add your boards and **save it as a task**.
2. Run it once with **Baseline only** switched on. It remembers today's jobs and lists nothing. Or skip this and
   accept that the first run lists every current job once.
3. Set **Output mode** to **Only new results** (or **New, changed and removed**) and add a **schedule**.
4. Connect an **integration** (Slack, Google Sheets, Zapier, Make, n8n), or put a **webhook URL** in the input.

Each saved task keeps its own memory, and switching a task between modes keeps it.

**Apify webhook template** (Integrations → Webhook → payload):

```json
{"datasetUrl": "https://api.apify.com/v2/datasets/{{resource.defaultDatasetId}}/items?clean=true&format=json"}
```

Each run also saves a summary (`OUTPUT` in the run's key-value store): counts of new, changed, unchanged and removed
jobs per board.

### How much does it cost?

- **$1.50 per 1,000 jobs** listed (on paid Apify plans 10-30% less).
- **On a schedule** (only new, changed or removed jobs): **$0.006 per board checked** plus $1.50 per 1,000 new, changed
  or removed jobs. Checking 10 boards daily with a few new jobs costs about $2.70 a month.
- Status rows (errors) are free. Set a spending limit on the run and the tool stops there.

### Good to know

- `salaryPeriod` is `year`, `month`, `week`, `day` or `hour`, whatever word the board uses (its own wording stays in `salaryText`); a rare period (every 2 weeks, one-time) comes as the board wrote it.
- "Removed" jobs are reported only when a board was fetched completely and without filters, so a hiccup never reports every job as closed.
- Freshness: every run reads each job board live (no cache); `fetchedAt` on each row says when.
- Pay ranges come from Greenhouse's pay-transparency field. Many companies leave it empty, so not every job has pay.

### How it compares

| Instead of | With this tool |
|---|---|
| Checking career pages by hand | Every open job of every board in one table, with the same columns for every company |
| A general web scraper | Reads the job board's own job data, so titles, locations, salaries and dates come as fields, not page text |
| Re-running a full export daily | 'Only new' mode lists just the jobs added since the last run; nothing new costs a fraction of a cent |

### FAQ

**What do I put in?** The company's Greenhouse board name, like `stripe`, or its link `https://job-boards.greenhouse.io/stripe`.

**Does every job have pay?** No. Pay comes from Greenhouse's pay-transparency field, and many companies leave it empty.

**How do I get only new jobs every day?** Save the input as a task, set Output mode to 'Only new results' and add a schedule. The first run can be a 'Baseline only' run, so it remembers today's jobs and lists nothing.

**Can I check several companies at once?** Yes, one per line. Every job row says which company it belongs to.

**Does it output recruiter names or e-mails?** The tool has no recruiter name or contact fields. E-mail addresses and phone numbers inside descriptions are replaced by `[redacted]` unless you switch that off.

**Source:** each company's public job board on Greenhouse. This tool is not affiliated with or endorsed by
Greenhouse.

### More Afterstar tools

- [ATS Jobs Scraper - Career Site Jobs: Greenhouse, Lever, Workday](https://apify.com/afterstar/careers-jobs-ats): Paste company career-page links (Greenhouse, Lever, Ashby, Workday and 3 more) and get every open job in one table.
- [Workday Jobs Scraper - All Jobs from Any Workday Career Site](https://apify.com/afterstar/workday-jobs): All open jobs from any company's Workday career site, with descriptions and posting dates.
- [Ashby Jobs Scraper - Any Company's Job Board + Pay](https://apify.com/afterstar/ashby-jobs): All open jobs from any company's Ashby job board, with compensation where the company publishes it.
- [Arbeitsagentur Jobs Scraper - Germany Jobs from the Jobbörse](https://apify.com/afterstar/arbeitsagentur-jobs): Jobs from Germany's federal job board (Bundesagentur für Arbeit) for any search and place, with full descriptions and, where given, salary ranges. Schedule it in new-only mode to get just the new jobs.

Found a problem or need a field? Open an issue on the Issues tab.

# Actor input Schema

## `boards` (type: `array`):

One per line: `stripe` or `https://job-boards.greenhouse.io/stripe`.

## `companyNames` (type: `array`):

Type company names instead of links, like Stripe or SpaceX. Each name is matched to a board's name or its address in our directory of 4,175 public Greenhouse job boards (found in Common Crawl's public index, 2026-08 to 2026-09, and checked live on 2026-10-05). A name with several boards takes the one with the most open jobs. One free row per name shows the board it was matched to and any others with that name; a name we don't know gives a free row too. If it's not the right board, paste the careers page or job board link instead.

## `keywords` (type: `array`):

Only jobs whose title (or title and description, see below) contains one of these words. Short keywords (up to 3 letters, like AI, IT, HR, Go) match whole words only; 4-5 letters match the start of a word ('Java' finds 'JavaScript'); longer ones match anywhere ('Entwickler' finds 'Softwareentwickler').

## `keywordScope` (type: `string`):

Where the keywords must appear.

## `locationContains` (type: `array`):

Only jobs where one of these appears as whole words in the location text or the country the board gives, like Germany, Berlin, Remote or US. A country name or code also matches the board's country field (Germany = DE) and the country's name in the location text. Accents don't matter (Zurich = Zürich). Country codes (US, DE, UK) and short words typed in capitals match only in capitals; other short names (Zug, Ulm) match in any case. US state codes look like country codes (CA, DE, IN), so full country names are safer. A board that lists only a city (Berlin) without a country is matched by the city, not by Germany.

## `excludeLocations` (type: `array`):

Drop jobs whose country field matches one of these, or whose every listed location contains one (whole words), like United States or London. A job also open in another place stays; regions like EMEA or North America count as another place, and an entry that only says Remote doesn't. A board that writes only a city (San Francisco, CA) without a country is not dropped by United States.

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

Only jobs the board marks remote, with a remote workplace type, or with 'remote' in the location text. Anything marked hybrid is left out.

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

A date like 2026-10-01. Jobs without a posting date are kept.

## `postedBefore` (type: `string`):

A date like 2026-10-31.

## `minSalary` (type: `integer`):

Only jobs whose top of the salary range reaches this number (any currency, as published). Jobs without salary are kept unless you tick the next box.

## `onlyWithSalary` (type: `boolean`):

Drop jobs that publish no salary (works on its own or with a minimum salary).

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

The most jobs per board in one run (no fixed cap; default 10,000).

## `outputMode` (type: `string`):

'All' lists everything found now. 'Only new' lists results never seen in earlier runs. 'New, changed and removed' also lists results that changed or disappeared. The first scheduled run counts everything as new; use 'Baseline only' to start cheaply.

## `baselineOnly` (type: `boolean`):

Saves what exists now without listing it, so the next scheduled run shows only what's new. Charged like a run with nothing new.

## `stateKey` (type: `string`):

Leave empty: each saved task keeps its own memory. Set a name to share one memory between tasks, or a new name to start over.

## `resetState` (type: `boolean`):

Starts from an empty memory: every result counts as new again.

## `webhookUrl` (type: `string`):

We POST a summary plus up to 100 new, changed or removed results here when something changed. Works with Slack incoming webhooks (choose the Slack format), Zapier, Make and n8n.

## `webhookFormat` (type: `string`):

JSON for automation tools; 'Slack message' sends one line of text.

## `webhookAlways` (type: `boolean`):

By default the webhook is called only when something changed or a source failed.

## `keepContactsInText` (type: `boolean`):

By default, emails and phone numbers inside free text (like job descriptions) are replaced by \[redacted].

## Actor input object example

```json
{
  "boards": [
    "greenhouse"
  ],
  "keywordScope": "title",
  "remoteOnly": false,
  "onlyWithSalary": false,
  "maxItems": 5,
  "outputMode": "all",
  "baselineOnly": false,
  "stateKey": "",
  "resetState": false,
  "webhookUrl": "",
  "webhookFormat": "json",
  "webhookAlways": false,
  "keepContactsInText": false
}
```

# Actor output Schema

## `results` (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 = {
    "boards": [
        "greenhouse"
    ],
    "maxItems": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("afterstar/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 = {
    "boards": ["greenhouse"],
    "maxItems": 5,
}

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

```

## MCP server setup

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