# Greenhouse Jobs Scraper: Open Roles, Salaries & Descriptions (`larkmoor/greenhouse-jobs`) Actor

Get every open job from any company's Greenhouse job board via the official public API: title, departments, offices, remote flag, salary range (official pay ranges + parsed), posted date and full description. Filter by keyword, location, department, date. $1 per 1,000 jobs.

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

## Pricing

from $0.85 / 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

## Greenhouse Jobs Scraper: Open Roles, Salaries & Descriptions

Get every open job from any company that hires through Greenhouse — Airbnb, Stripe, Figma, Discord, Coinbase, Duolingo, Reddit and thousands more — as one clean row per job: title, departments, offices, location, a remote flag, the salary range, when the job was first published, the job URL and the full description as plain text and HTML.

It reads Greenhouse's **official public Job Board API** (`boards-api.greenhouse.io`), the same feed companies use to embed their job boards on their own careers pages. No browser, no login, no proxies, no blocked runs.

### What you can use it for

- **Job boards and aggregators**: keep a niche job board (remote, AI, fintech, climate, a city) filled with fresh roles from the companies you track
- **Recruiting and sales leads**: see which companies are hiring for which teams right now — a company opening 20 sales roles is a company with budget
- **Salary research**: collect published pay ranges by title, level and location across hundreds of companies
- **Competitive intelligence**: watch a competitor's hiring by department and office week by week
- **Job alerts**: a daily scheduled run with `postedWithinDays: 1` sends only new roles to Slack, email or a sheet
- **Career search**: one list of every open "product designer" or "data engineer" role across your target companies

### Why this one

- **$1 per 1,000 jobs**, $0.001 per run start — about half of what other Greenhouse actors charge
- **Reliable**: official public API, so runs do not fail on bot checks or page redesigns
- **Salary built in**: the official pay-transparency range each company publishes (turn on `includePayRanges`), plus a salary parsed from the description text, with currency and period (year or hour)
- **Accepts anything**: a board slug (`stripe`), a job-board URL (`https://boards.greenhouse.io/stripe`, `job-boards.greenhouse.io/...`) or a company website / careers page that embeds a Greenhouse board — it finds the board for you
- **Real filters**: keywords (title or full text), locations, departments, remote only, posted within N days, salary only — and you only pay for the jobs that pass them
- **256 MB memory**, finishes a 700-job company in seconds

### Input

| Field | What it does |
|---|---|
| `companies` | Greenhouse board slugs, job-board URLs or company websites |
| `keywords` | Keep jobs mentioning any of these words |
| `keywordsInTitleOnly` | Match keywords in the title only |
| `locations` | Keep jobs whose location or office contains any of these ("New York", "London", "Remote") |
| `departments` | Keep jobs in matching departments ("Engineering", "Sales") |
| `remoteOnly` | Only remote roles |
| `postedWithinDays` | Only jobs first published in the last N days |
| `withSalaryOnly` | Only jobs with a salary range |
| `includePayRanges` | Also read each job's official pay-transparency range (one extra request per job) |
| `includeDescription` | Include the description text and HTML (default on) |
| `maxJobsPerCompany` / `maxResults` | Caps per company and for the whole run |

Example:

```json
{
  "companies": ["airbnb", "https://boards.greenhouse.io/stripe", "figma"],
  "keywords": ["engineer"],
  "keywordsInTitleOnly": true,
  "locations": ["United States", "Remote"],
  "includePayRanges": true,
  "maxResults": 500
}
```

### Output

```json
{
  "company": "Figma",
  "boardSlug": "figma",
  "jobId": "5551234004",
  "title": "Compliance Engineer",
  "department": "Business Operations",
  "departments": ["Business Operations"],
  "offices": ["San Francisco, CA", "New York, NY"],
  "location": "San Francisco, CA • New York, NY • United States",
  "remote": false,
  "employmentType": null,
  "salaryMin": 169000,
  "salaryMax": 296000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salarySource": "pay_transparency",
  "firstPublished": "2026-10-16T11:51:12-04:00",
  "updatedAt": "2026-10-20T09:02:11-04:00",
  "url": "https://boards.greenhouse.io/figma/jobs/5551234004",
  "descriptionText": "Figma is growing our team of passionate creatives and builders...",
  "descriptionHtml": "<p>Figma is growing...</p>"
}
```

Other columns: `requisitionId`, `language`, `salaryText` (the range exactly as written), and `metadata` (the custom fields a company publishes, such as employment type or level).

### How much does it cost?

**$1.00 per 1,000 jobs** on the Free plan plus **$0.001 per run**, with automatic discounts on paid Apify plans. Platform compute is included. Filters run before you are charged, so filtered-out jobs cost nothing.

Worked examples:

- **Daily alert for 50 companies**, about 40 new jobs a day: **$0.04 a day**, about $1.20 a month
- **Full snapshot of 200 companies** (about 30,000 open jobs): **$30**
- **Salary study**: every engineering role with a published range across 100 companies (about 2,500 jobs): **$2.50**

### FAQ

**Is this legal?**
Yes. It uses Greenhouse's public Job Board API, which Greenhouse documents for exactly this purpose (showing a company's open jobs anywhere). Job postings are public advertisements; no login, no candidate data and no personal data are touched.

**How do I find a company's slug?**
Open the company's careers page. If a job link goes to `boards.greenhouse.io/<slug>` or `job-boards.greenhouse.io/<slug>`, the slug is that last part. Or just paste the careers page URL and the actor looks for the board link in the page (if a careers page loads its job list only with JavaScript, give the slug instead).

**Can it search all Greenhouse companies at once?**
Greenhouse has no public directory of every board, so you give the companies. Lists of a few hundred work well in one run.

**Why is the salary empty for some jobs?**
Not every company publishes a range. Many US companies do (especially for roles in California, Colorado, New York and Washington). Turn on `includePayRanges` to read the official range; the parsed-from-text range is always on.

**Does it cover Lever, Ashby or Workday?**
This actor is focused on Greenhouse. For a mix of applicant tracking systems in one run, use our Career Site Jobs actor.

### Tips

- Schedule it daily with `postedWithinDays: 1` and connect a Slack or email integration for a zero-maintenance job alert.
- Use `keywordsInTitleOnly` for precise roles ("designer"), full-text keywords for skills ("Rust", "Kubernetes").
- Combine `locations: ["Remote"]` with `remoteOnly` off to also keep jobs listing several offices plus remote.

### Integrations

Works with Google Sheets, Slack, Zapier, Make, Airtable, webhooks, the Apify API and the Python and JavaScript clients. Download as JSON, CSV, Excel, XML or HTML.

### Changelog

- **2026-10-21** — First release: all open jobs per board, departments, offices, remote flag, official pay ranges and parsed salaries, posted-date, keyword, location and department filters, careers-page auto-detection.

# Actor input Schema

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

Greenhouse board slugs (e.g. 'airbnb', the part after boards.greenhouse.io/), job-board URLs, or company websites/careers pages that embed a Greenhouse board.

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

Keep jobs whose title or description contains any of these words (case-insensitive). Empty = all jobs.

## `keywordsInTitleOnly` (type: `boolean`):

Only look for the keywords in the job title (stricter).

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

Keep jobs whose location or office contains any of these (e.g. 'New York', 'London', 'Remote').

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

Keep jobs in departments containing any of these (e.g. 'Engineering', 'Sales').

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

Keep only jobs that mention remote work in the location, office or title.

## `postedWithinDays` (type: `integer`):

Keep only jobs first published in the last N days. Empty = any age.

## `withSalaryOnly` (type: `boolean`):

Keep only jobs where a salary range was found.

## `includePayRanges` (type: `boolean`):

Also read the official pay-transparency range each company publishes for a job (one extra request per job). The salary parsed from the description is always included.

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

Include the job description as plain text and HTML.

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

Stop after this many jobs from one company.

## `maxResults` (type: `integer`):

Hard cap on rows for the whole run (you pay per job row).

## Actor input object example

```json
{
  "companies": [
    "airbnb",
    "stripe",
    "figma"
  ],
  "keywords": [
    "engineer"
  ],
  "keywordsInTitleOnly": false,
  "remoteOnly": false,
  "withSalaryOnly": false,
  "includePayRanges": false,
  "includeDescription": true,
  "maxJobsPerCompany": 1000,
  "maxResults": 50
}
```

# Actor output Schema

## `results` (type: `string`):

All results as JSON items in the run's default dataset (also downloadable as CSV/Excel from the dataset).

# 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": [
        "airbnb",
        "stripe",
        "figma"
    ],
    "keywords": [
        "engineer"
    ],
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("larkmoor/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": [
        "airbnb",
        "stripe",
        "figma",
    ],
    "keywords": ["engineer"],
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("larkmoor/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": [
    "airbnb",
    "stripe",
    "figma"
  ],
  "keywords": [
    "engineer"
  ],
  "maxResults": 50
}' |
apify call larkmoor/greenhouse-jobs --silent --output-dataset

```

## MCP server setup

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