# Greenhouse Jobs Scraper (`muhammadafzal/greenhouse-jobs-scraper`) Actor

Scrape public hosted Greenhouse job boards with titles, locations, departments, dates, full descriptions and source salary ranges. Filter and export jobs for recruiting and hiring analytics.

- **URL**: https://apify.com/muhammadafzal/greenhouse-jobs-scraper.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (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.60 / 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/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

Extract public jobs from hosted Greenhouse company boards for recruiting research, job feeds, hiring analytics, and vacancy monitoring. Supply company board slugs or hosted board URLs; filter by title keyword, location, and department. Export the default dataset as JSON, CSV, Excel, or via the Apify API.

```json
{"boards":["anthropic"],"keyword":"Engineer","location":"","department":"","maxItems":20,"maxPagesPerBoard":20,"includeDescription":true}
```

### Output

Each unique board/job ID produces one record: `jobId`, `boardToken`, `title`, `companyName`, `location`, `department`, `url`, `updatedAt`, `publishedAt`, `requisitionId`, `descriptionHtml`, `descriptionText`, `salaryRanges`, `source`, and `scrapedAt`. Nullable fields remain null when unavailable. Company names and descriptions require detail fetching. Salary ranges are source data; salaries are never inferred. SUMMARY contains outcome, counts, limits, warnings, request attempts, stop reason, and charged result events. Diagnostics never become job records.

### Limits and source coverage

Supports standard hosted `job-boards.greenhouse.io`, legacy `boards.greenhouse.io` board URLs (normalized to the current host), and `job-boards.eu.greenhouse.io` URLs. Individual job URLs and arbitrary websites are rejected. Custom careers-site redirects are unsupported and reported explicitly. No global company discovery or historical/closed jobs. Listings reflect the public board at run time and can change while pagination runs.

The scraper reads embedded page-owned structured data and follows bounded pagination. Defaults: 20 jobs, 20 pages per board, descriptions enabled. Maximum: 20 boards, 5,000 jobs, 100 pages per board; overall request attempts are capped at 250 and runtime at four minutes. These budgets can stop extraction before the requested count. Requests are sequential, with at most three attempts for transient errors. Deduplication state is checkpointed every 20 records and on SDK persistence/lifecycle events. Details that fail leave a valid listing record and a warning. Missing boards/access failures are distinct from truthful no-match results; complete source failure exits unsuccessfully. Verified free-plan production runs deliver at most **five jobs**; paid and unknown local environments use the requested bound.

### Pay per event

All prices include platform usage; no platform-usage pass-through. One synthetic start fee per run and one primary dataset-item event per delivered job. No manual synthetic charging or duplicate value event. The SDK enforces the total charge cap before writes. Live tiered pricing is active and includes platform usage. The Console and authenticated API both verify the following prices:

| Event | FREE | BRONZE (2.5%) | SILVER (5%) | GOLD (20%) |
|---|---:|---:|---:|---:|
| Start | $0.005 | $0.005 | $0.005 | $0.005 |
| Job | $0.002 | $0.00195 | $0.0019 | $0.0016 |

FREE-tier totals: one job $0.007, five $0.015, twenty $0.045. GOLD twenty-job total $0.037. PLATINUM and DIAMOND use the GOLD rates. Start fees apply even to empty or rejected runs if the container starts; no job events for empty results. Set a run charge cap appropriate to your expected volume. At least $0.007 permits a start and one job at the highest tier price. Page/request/runtime limits also bound usage when no jobs match.

### Development

Node.js 22, Apify SDK 3, Cheerio; no browser, external provider, or proxy dependency. `npm ci`, `npm test`, `npm run check`, and `apify run --purge`. The live tier contract is recorded in `.actor/pay_per_event.json` and `.actor/live_pay_per_event.json`. Deployment and repeatable private Tasks are managed by `scripts/cloud.mjs`; cloud evidence is saved in `qa-report.json`.

Uses publicly available job advertisements only. Respect source terms and applicable law. No authentication, applications, applicant data, or access-control bypass. This independent tool is not affiliated with Greenhouse or the employers. Actor and example Tasks remain private until the owner reviews and publishes them.

# Actor input Schema

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

1–20 company slugs or HTTPS hosted board URLs. Example: anthropic. Custom careers redirects are unsupported. EU hosted URLs are accepted.

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

Total unique jobs across all boards; verified free-plan runs are capped at five.

## `maxPagesPerBoard` (type: `integer`):

Bounds pagination and cost. Each page normally contains up to 50 jobs.

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

Fetch each matching public detail page for HTML/text descriptions, company name, and source salary ranges. Missing details are reported as warnings.

## `keyword` (type: `string`):

Case-insensitive substring filter on job title. Empty matches all.

## `location` (type: `string`):

Case-insensitive substring filter on location. Empty matches all.

## `department` (type: `string`):

Case-insensitive substring filter on department. Empty matches all.

## Actor input object example

```json
{
  "boards": [
    "anthropic"
  ],
  "maxItems": 20,
  "maxPagesPerBoard": 20,
  "includeDescription": true,
  "keyword": "",
  "location": "",
  "department": ""
}
```

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

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

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

```

## MCP server setup

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