Greenhouse Jobs API & Scraper

Rocketyard’s Greenhouse Jobs API & Scraper exports every open job from Greenhouse job boards through Greenhouse’s official public job-board API and returns one clean record per job: title, company, location, workplace type, employment type, department and more. It runs on the Apify platform, so you can start it from the Apify Console, the REST API, an AI agent or a no-code tool.

Run it on Apify

$1.00 per 1,000 jobs, no subscription. You run it with your own Apify account, and Apify handles billing.

Who it’s for

Recruiters and staffing agencies tracking which companies are hiring
Sales teams using new openings as a buying signal
Developers of job boards, job alerts and salary tools
Analysts building hiring and compensation datasets

What you can do with it

Export every open role from companies that hire with Greenhouse, with salary ranges and full descriptions
Track new and closed roles at target companies every day
Build a job or salary dataset from thousands of Greenhouse boards

How it works

Greenhouse publishes every open job of a company through a public job-board API (documentation), the feed companies use to show openings on their own sites. The Actor reads that API for each board you give it (a board URL such as https://job-boards.greenhouse.io/discord or just the board name discord), without a browser, and applies your keyword, location, department and remote filters before anything is billed. Reading the API instead of scraping HTML means complete records, including pay ranges when the company publishes them, and nothing breaks when a company redesigns its careers page.

Example output

A real record from a test run on job-boards.greenhouse.io on 2026-11-05. Fields the page didn’t publish are left out here; the Actor returns them as null.

{
  "url": "https://job-boards.greenhouse.io/discord/jobs/8917177002",
  "type": "JobPosting",
  "title": "Associate Commercial Counsel",
  "company": "Discord",
  "location": "San Francisco Bay Area or Remote (U.S.)",
  "workplaceType": "remote",
  "department": "Legal",
  "datePosted": "2026-11-03T16:27:16.000Z",
  "dateUpdated": "2026-11-03T16:31:51.000Z",
  "salaryMin": 200000,
  "salaryMax": 225000,
  "salaryCurrency": "USD",
  "salaryUnit": "YEAR",
  "salaryText": "USD 200,000 - 225,000 per year",
  "locations": [
    "San Francisco Bay Area or Remote (U.S.)",
    "San Francisco, California, United States"
  ],
  "country": "United States",
  "remote": true,
  "description": "Discord has a highly engaged community of millions of daily active users who use the platform for many different reasons, but there’s one thing that nearly everyone does: play video games. Discord plays a uniquely important role in the future of gaming, and we are focused on making it easier and…",
  "applyUrl": "https://job-boards.greenhouse.io/discord/jobs/8917177002",
  "requisitionId": "R-107469",
  "ats": "greenhouse",
  "board": "discord",
  "jobId": "8917177002",
  "sourceUrl": "https://job-boards.greenhouse.io/discord",
  "scrapedAt": "2026-11-05T18:08:59.131Z"
}

Fields

Field	Description	Filled in latest test
`title`	Job title	100%
`company`	Company name	100%
`location`	Primary location as published	100%
`workplaceType`	`remote`, `hybrid`, `on-site`, or empty when the posting does not say	30%
`employmentType`	schema.org value (`FULL_TIME`, `PART_TIME`, `CONTRACTOR`, `INTERN`, `TEMPORARY`) or the label as published	0%
`department`	Department	100%
`team`	Team	0%
`datePosted`	First published (ISO 8601)	100%
`dateUpdated`	Last updated (ISO 8601), when the API publishes it	100%
`salaryMin`	Lowest salary of the published range	60%
`salaryMax`	Highest salary of the published range	60%
`salaryCurrency`	ISO 4217 currency code	60%
`salaryUnit`	`YEAR`, `MONTH`, `WEEK`, `DAY` or `HOUR`	60%
`salaryText`	The published pay range as text	60%
`locations`	Every location of the job	100%
`country`	Country	40%
`remote`	`true` for remote jobs, `false` for hybrid or on-site, empty when not stated	30%
`description`	Full job description as plain text	100%
`applyUrl`	Application page	100%
`requisitionId`	Requisition ID, when published	100%
`ats`	Applicant tracking system	100%
`board`	Job-board name (the company part of the board URL)	100%
`jobId`	Job ID in the applicant tracking system	100%
`sourceUrl`	Job board the record came from	100%
`url`	the page the record came from	100%
`scrapedAt`	ISO timestamp of the extraction	100%

A field is filled when the source publishes it. The Actor never guesses a value: a missing field comes back as null. “Filled in latest test” is the share of records from the latest test run (discord on Greenhouse) that had the field; other sources publish more or less.

Pricing

You pay $1.00 per 1,000 jobs, plus a start fee of $0.00005 per run. Jobs removed by your keyword, location, department or remote filters are not charged.

Jobs	Cost
1,000	$1.00
10,000	$10.00
100,000	$100.00

Set maxItems or the run’s Maximum cost per run in Apify to cap spending.

API

Every Apify Actor is also a REST endpoint, so Greenhouse Jobs API & Scraper works as a Greenhouse jobs API, a Greenhouse job board API or an ATS jobs API. Call it from any language with the Apify REST API, or with Apify’s JavaScript and Python clients. You need an Apify API token.

Greenhouse jobs API request

curl -s -X POST "https://api.apify.com/v2/acts/rocketyard~greenhouse-jobs-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'content-type: application/json' \
  -d '{"startUrls":[{"url":"https://job-boards.greenhouse.io/discord"}],"maxItems":1000}'

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('rocketyard/greenhouse-jobs-scraper').call({"startUrls":[{"url":"https://job-boards.greenhouse.io/discord"}],"maxItems":1000});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("rocketyard/greenhouse-jobs-scraper").call(run_input={"startUrls":[{"url":"https://job-boards.greenhouse.io/discord"}],"maxItems":1000})
items = client.dataset(run["defaultDatasetId"]).list_items().items

The synchronous endpoint returns the records directly. For long crawls, start the run asynchronously and read the dataset when it finishes.

MCP

Apify’s MCP server exposes this Actor as a tool to Claude, Cursor and other MCP clients. Open this Actor’s MCP setup page for setup steps per client, or connect it with this URL:

https://mcp.apify.com?tools=rocketyard/greenhouse-jobs-scraper

Claude Code:

claude mcp add --transport http apify "https://mcp.apify.com?tools=rocketyard/greenhouse-jobs-scraper"

Cursor (.cursor/mcp.json) and other clients that read an mcpServers config:

{
  "mcpServers": {
    "apify": { "url": "https://mcp.apify.com?tools=rocketyard/greenhouse-jobs-scraper" }
  }
}

On first use your browser opens so you can sign in to Apify. Then ask the agent, for example: “Export every open role from companies that hire with Greenhouse, with salary ranges and full descriptions”. The tool returns JSON records, and the runs are billed to that Apify account at $1.00 per 1,000 jobs.

Automation

n8n, Make and Zapier all connect to Apify. Each example below uses Actor rocketyard/greenhouse-jobs-scraper with this input:

{
  "startUrls": [
    {
      "url": "https://job-boards.greenhouse.io/discord"
    }
  ],
  "maxItems": 1000
}

n8n

Copy this workflow and paste it onto an n8n canvas. It runs the Actor every morning through an HTTP Request node and returns the records as n8n items.

{
  "name": "Greenhouse Jobs API & Scraper daily",
  "nodes": [
    {
      "parameters": {
        "rule": {
          "interval": [
            {
              "field": "days",
              "daysInterval": 1,
              "triggerAtHour": 7
            }
          ]
        }
      },
      "id": "c1f6a2d0-4a57-4b5e-9d7a-0a1b2c3d4e01",
      "name": "Every day at 07:00",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        0
      ]
    },
    {
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/acts/rocketyard~greenhouse-jobs-scraper/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpBearerAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"startUrls\": [\n    {\n      \"url\": \"https://job-boards.greenhouse.io/discord\"\n    }\n  ],\n  \"maxItems\": 1000\n}",
        "options": {
          "timeout": 300000
        }
      },
      "id": "c1f6a2d0-4a57-4b5e-9d7a-0a1b2c3d4e02",
      "name": "Run Greenhouse Jobs API & Scraper",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        0
      ],
      "credentials": {
        "httpBearerAuth": {
          "name": "Apify API token"
        }
      }
    }
  ],
  "connections": {
    "Every day at 07:00": {
      "main": [
        [
          {
            "node": "Run Greenhouse Jobs API & Scraper",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {}
}

Then open the HTTP Request node and create an HTTP Bearer Auth credential named Apify API token, with your token from Apify Console as the bearer token. The token stays in n8n’s credential store; the workflow only names the credential. Change the input in the node’s JSON body to your own. The node waits up to 300 seconds, which is also the limit of Apify’s synchronous endpoint. An input that yields nothing comes back as an item with an error field, which you can drop with a Filter node. Apify also publishes a community node, @apify/n8n-nodes-apify, with a Run an Actor and get dataset operation.

Make

Add Apify’s Run an Actor module and connect your Apify account.
Choose rocketyard/greenhouse-jobs-scraper, paste the input above and set Run synchronously to Yes. Make limits how long a synchronous run can take, depending on your plan. For longer runs, start the scenario from Watch Actor Runs instead.
Add Get Dataset Items with the run’s default dataset ID.
Send the items wherever you need them, for example with Google Sheets Add a Row, mapping title, company, location and workplaceType.

Zapier

Add Apify’s Run Actor action, connect your Apify account, choose rocketyard/greenhouse-jobs-scraper and paste the input above.
Zapier stops synchronous runs after 30 seconds. For anything larger than a small run, let the run continue in the background and start a second Zap from the Finished Actor run trigger.
Add Fetch dataset items with the run’s dataset ID, then map title, company, location and workplaceType into your app.
Test with a small input and check that the Zap handles every record before you turn it on.

Limits

Only companies whose careers pages are hosted on Greenhouse, with a public job board.
Pay ranges appear only when the company publishes one on the posting.
Jobs that a company has closed are no longer on its board, so each run returns the roles open right now.

FAQ

How much does it cost?

$1.00 per 1,000 jobs plus $0.00005 per run, billed by Apify. 10,000 jobs cost $10.00. There is no subscription, and you can cap any run with Maximum cost per run. Your Apify plan sets your discount tier (Platinum and Diamond are enterprise tiers):

Tier	Per 1,000 jobs
Free	$1.00
Bronze	$1.00
Silver	$0.80
Gold	$0.65
Platinum	$0.65
Diamond	$0.65

How do I call it from the API?

One request starts a run and returns its results, using your Apify API token:

curl -X POST "https://api.apify.com/v2/acts/rocketyard~greenhouse-jobs-scraper/run-sync-get-dataset-items" -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" -d '{"startUrls":[{"url":"https://job-boards.greenhouse.io/discord"}],"maxItems":1000}'

What happens when a URL fails?

The dataset gets one free error item for it, with a code and the reason, and the other inputs in the run carry on. Error codes explains each code, whether a retry helps and what to do.

Which companies does it work on?

Any company whose careers page is hosted on Greenhouse, with URLs like https://job-boards.greenhouse.io/discord. The board name is the part after the domain (discord).

What happens when a field is missing?

The field comes back as null. The Actor reports what the source publishes and never fills in guesses.

Is it allowed to scrape this data?

The Actor reads only job postings that companies publish for anyone to see, through Greenhouse’s public API, honours robots.txt, and returns no data about applicants or recruiters. You are responsible for how you use the data under the applicable terms and the law (for example GDPR).

Can I use it from an AI agent?

Yes. Connect Apify’s MCP server as shown in MCP, and the agent can call the Actor as a tool.

Alternatives

See how it compares with other greenhouse job scrapers on price, users and run success, from Apify Store data. Need a field or site behaviour that isn’t covered? Open an issue on the Actor page.

Run it on Apify

​Who it’s for

​What you can do with it

​How it works

​Example output

​Fields

​Pricing

​API

​Greenhouse jobs API request

​MCP

​Automation

​n8n

​Make

​Zapier

​Limits

​FAQ

​How much does it cost?

​How do I call it from the API?

​What happens when a URL fails?

​Which companies does it work on?

​What happens when a field is missing?

​Is it allowed to scrape this data?

​Can I use it from an AI agent?

​Alternatives

​Guides