# Greenhouse Jobs Scraper - Descriptions & Apply Links (`starbright_overlap/greenhouse-jobs-scraper`) Actor

Extract every live job posting from any Greenhouse job board - full descriptions, departments, locations and direct apply links. No login, no proxies. Give it a company slug or board URL.

- **URL**: https://apify.com/starbright\_overlap/greenhouse-jobs-scraper.md
- **Developed by:** [Sulle H](https://apify.com/starbright_overlap) (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.00 / 1,000 job results

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/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 Scraper

Extract every live job posting from any **Greenhouse** job board — full descriptions, departments, offices, locations and apply links.

Give it a company slug (`databricks`) or a board URL (`https://job-boards.greenhouse.io/databricks`) and it returns clean, structured job data. No login, no cookies, no proxies.

### What you get

| Field | Description |
|---|---|
| `company` / `companySlug` | Company name and its Greenhouse board slug |
| `jobId` | Greenhouse job ID (stable — good for deduping across runs) |
| `title` | Job title |
| `location` | Location string as shown on the board |
| `offices` | Structured office list |
| `departments` | Department / team |
| `firstPublishedAt` | When the job first went live |
| `updatedAt` | Last modification timestamp |
| `applyUrl` | Direct application link |
| `requisitionId` | Internal requisition ID, when the company exposes one |
| `descriptionText` | Full job description as plain text |

### Input

```json
{
  "boards": ["databricks", "https://job-boards.greenhouse.io/figma"],
  "includeDescription": true,
  "titleFilter": "engineer",
  "locationFilter": "remote"
}
```

- **boards** *(required)* — one entry per company; bare slugs and full URLs both work.
- **includeDescription** — set `false` for a faster, lighter run.
- **maxJobsPerBoard** — cap the rows per company.
- **titleFilter** / **locationFilter** — case-insensitive substring filters.

### Finding a board slug

Open the company's careers page. If the URL looks like `job-boards.greenhouse.io/acme` or `boards.greenhouse.io/acme`, the slug is `acme`. Embedded boards work too — look for `?for=acme` in the page source.

### Pricing

Pay per result: you are charged only for job rows actually delivered. Boards that fail or return nothing cost you nothing.

### Notes

- Bad or dead slugs never abort the run — they are collected into a `FAILED_BOARDS` record in the key-value store so you can see exactly what went wrong.
- Typical large board (800+ jobs) completes in well under a minute.

# Actor input Schema

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

One entry per company. Accepts a bare slug (`databricks`) or a full board URL (`https://job-boards.greenhouse.io/databricks`). Find the slug in the company's careers-page URL.

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

Fetch the complete description text for every posting. Slightly slower, much richer output.

## `maxJobsPerBoard` (type: `integer`):

Stop after this many jobs per company. Leave empty for all jobs.

## `titleFilter` (type: `string`):

Case-insensitive substring match on the job title, e.g. `engineer`. Leave empty for no filter.

## `locationFilter` (type: `string`):

Case-insensitive substring match on the location, e.g. `remote` or `london`. Leave empty for no filter.

## Actor input object example

```json
{
  "boards": [
    "databricks",
    "https://job-boards.greenhouse.io/figma"
  ],
  "includeDescription": true
}
```

# 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": [
        "databricks",
        "stripe"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("starbright_overlap/greenhouse-jobs-scraper").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": [
        "databricks",
        "stripe",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("starbright_overlap/greenhouse-jobs-scraper").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": [
    "databricks",
    "stripe"
  ]
}' |
apify call starbright_overlap/greenhouse-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/B4TbKUPeXTxAUEBUk/builds/tnCzNUeHKzFs5bftO/openapi.json