Greenhouse Job Board Scraper — Company Hiring Signals 🚀

foXLabs hiring series: Lever · Ashby · Workday · SmartRecruiters · Personio · Teamtailor

🎉 Turn any company's Greenhouse board into clean, structured hiring data — no login, no API key, one row per open role. Built for recruiters, sales & competitive-intelligence teams, and anyone scoring hiring intent at scale.

🔍 What is the Greenhouse Job Board Scraper — and when should you use it?

Greenhouse powers the careers page of a large slice of venture-backed tech. Give this actor a board token (stripe) or a board URL and it returns that company's entire open-roles list — title, department, location, remote flag, posting date, the full description and the apply link — as clean rows you can filter, export, or feed to a spreadsheet, a database or an AI agent.

Use it when you need: every open role at a target company; hiring-intent signals (which functions a company is growing); a recruiter sourcing list across many companies; or a Chinese-wall-clean read of a competitor's headcount plans — all from the public Greenhouse board API, no key.

Use something else when: the company doesn't run on Greenhouse. Point the matching actor at its ATS instead — Lever, Ashby, Workday, SmartRecruiters, Personio or Teamtailor. Every one emits the same schema, so their outputs concatenate into one hiring-intent table.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/greenhouse-job-board-scraper.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered role, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull a company's open roles from its Greenhouse board using the Apify Actor
`foxlabs/greenhouse-job-board-scraper`.

Input: `queries` is a list of Greenhouse board tokens (e.g. "stripe", "airbnb") or board URLs.
`maxResultsPerQuery` caps rows per company (default 200). Each row has jobTitle, department,
location, isRemote, postedAt, description and applyUrl.

Start with:
{ "queries": ["stripe"], "maxResultsPerQuery": 50 }

Ask me which companies to track, run the Actor, then summarise the roles as a table.

Things you can ask your agent for:

• "Pull every role Stripe has open and group them by department."
• "Across airbnb, databricks and stripe, list the sales roles opened this month."
• "Track this board weekly and tell me which functions are growing."

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/greenhouse-job-board-scraper.md.

📋 Overview

Everything you need to turn a Greenhouse careers board into clean, structured data — full role details, engagement-ready metadata and hiring signals — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole board in one call — one request returns every open role with descriptions, no per-job follow-up.
• ⚡ Token- or URL-native — paste stripe or a full board URL; the actor resolves the rest.
• 🎯 Clean, real fields — department id-prefixes stripped, descriptions HTML-stripped to plain text, no empty-promise columns.
• 🔗 Same schema across the series — join Greenhouse output with the six other ATS actors on companyBoard.
• 💰 Pay only for results — per-row pricing, empty/failed lookups never billed.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Full open-roles list — every published role on the board by token or URL.
• 📄 Complete descriptions — title, department, location, remote flag, posted date, full description (HTML stripped), apply URL.
• 🏢 Departments & offices — structured arrays alongside the primary values.
• 🔁 Stable join key — companyBoard ties rows across runs and across the six sibling ATS actors.
• 📦 Clean export — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~greenhouse-job-board-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries": ["stripe"], "maxResultsPerQuery": 50}'

🚀 Getting Started (3 steps)

1. Choose your companies — Greenhouse board tokens (stripe, airbnb) or full board URLs.
2. Set the cap — maxResultsPerQuery limits rows per company (default 200).
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{
  "queries": ["stripe", "airbnb", "https://job-boards.greenhouse.io/databricks"],
  "maxResultsPerQuery": 200,
  "maxConcurrency": 5,
  "includeRaw": false
}

Field	Type	Description
queries	array	Board tokens (stripe) or board URLs. The token is the last path segment of a Greenhouse careers URL.
maxResultsPerQuery	integer	Caps rows per company (default 200).
maxConcurrency	integer	How many companies to fetch at once (default 5).
includeRaw	boolean	Attach the source's untouched record under raw.
requestDelayMs	integer	Politeness delay between requests.
proxyConfiguration	object	Optional — the Greenhouse board API answers datacenter IPs directly.

📤 Output

One row per open role, saved to the dataset.

Field	Type	Description
companyName	string	Company as named on the board
companyBoard	string	Board token — the join key across runs
jobId	string	Greenhouse job ID
jobTitle	string	Role title
department	string	Department (internal id prefix stripped)
departments / offices	array	Structured department/office lists
location	string	Location as posted
isRemote	boolean	True when the role reads as remote
postedAt	string	First published date (ISO)
employmentType	string	Where the board publishes one
description	string	Full role description, HTML stripped
applyUrl / sourceUrl	string	Apply link / public posting URL

Every row also carries query, scrapedAt, and — when a lookup fails — an error explaining why.

{
  "source": "Greenhouse",
  "companyName": "Stripe",
  "companyBoard": "stripe",
  "jobId": "8172508",
  "jobTitle": "Abuse Investigator",
  "department": "Security Analytics",
  "location": "Dublin",
  "isRemote": false,
  "postedAt": "2026-09-03",
  "description": "Who we are\n\nAbout Stripe\n\nStripe is a financial infrastructure platform…",
  "applyUrl": "https://stripe.com/jobs/search?gh_jid=8172508",
  "sourceUrl": "https://job-boards.greenhouse.io/stripe/jobs/8172508"
}

💼 Use cases

1. Hiring-intent scoring — a company that just opened five sales roles is buying sales tooling. Input: target board tokens via queries, scheduled weekly. Output: roles by department + posted date. Use: rank accounts by what they're recruiting for.

2. Competitor headcount tracking — watch which functions a peer grows and which freeze. Input: the competitor's board, run weekly. Output: the full role list over time. Use: spot expansion and hiring freezes early.

3. Recruiter sourcing — every open role across a target list, with apply links. Input: many board tokens in one run. Output: one table of roles + apply URLs. Use: build a sourcing pipeline in minutes.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/greenhouse-job-board-scraper').call({
  queries: ['stripe'], maxResultsPerQuery: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/greenhouse-job-board-scraper').call(
    run_input={'queries': ['stripe'], 'maxResultsPerQuery': 50}
)
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your queries → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: $0.002 per delivered role. Empty or failed lookups are never billed. Bulk companies scale linearly; you pay for the roles you actually get. View current pricing.

❓ FAQ

Do I need a Greenhouse account, login or API key? No. This reads the public Greenhouse Job Board API — the same endpoint the company's own careers page calls.

What do I search by? A board token (stripe) or a full board URL. The token is the last path segment of the careers URL.

How current is the data? Every run queries the source live, so results are as fresh as the board itself.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

What happens when a board has no roles or the token is wrong? You get a row carrying your query and an error — nothing is silently dropped, and you're not charged.

Is scraping this legal? It reads a public job board API a company publishes deliberately so its openings can be syndicated. It contains job data, not personal data. See below.

🐛 Troubleshooting

• "Greenhouse has no public board named …" — take the token from the careers URL's last path segment rather than guessing; a token isn't always the company's domain.
• Fewer rows than expected — the board may simply have that many open roles, or maxResultsPerQuery is capping them; raise the cap.
• An error row instead of jobs — the board token is wrong or the board is private; confirm the careers URL loads publicly.

⚠️ Trademark

Independent, third-party tool. Not affiliated with, endorsed by or connected to Greenhouse Software, Inc. "Greenhouse" and related marks belong to their owners and are used here for identification only.

⚖️ Is it legal to scrape this data?

This actor reads only publicly published job-posting data — no private or personal user data. Your results can still contain personal data (e.g. a recruiter name in a description); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify's blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor's Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.4

• AI-agent payments (x402). Standby was removed to meet Apify's x402 eligibility; agents can now discover, run and pay for this actor over x402 (USDC on Base) or Skyfire with no Apify account. Batch and MCP usage unchanged.

0.3

• Output schema linked in actor.json so the Store shows the Output tab.

0.2

• Descriptions decoded to clean plain text; department id-prefixes stripped; empty-promise columns and the placeholder requisitionId removed.

0.1

• Initial release: full open-roles extraction from any Greenhouse board by token or URL.