Greenhouse Job Board Scraper — Multi-Department, Multi-Office Postings

No company list needed. Pick a verified company bundle and hit Start - every board token in it was checked against the live Greenhouse API, so you get real postings without researching a single one.

The only one of our ATS board scrapers that keeps every department and every office a job is filed under, not just the first one. Query any company's public Greenhouse board and get one normalized JSON record per role, with departments and offices returned as full arrays plus Greenhouse's own internal requisitionId — useful for spotting when the same underlying req is posted to more than one office.

Pain points

• Greenhouse's board API is public, but there's no bulk endpoint across companies — you have to already know each company's board token, then call each board separately.
• A posting tagged to more than one department, or filed under more than one office, gets flattened to a single value by most scrapers, losing the rest of the tags.
• HTML job descriptions come back with entities encoded (&, ', ...) — unusable until decoded.
• Watching a list of companies for genuinely new roles means storing what you already pulled and diffing every run yourself.

What we solve

• Full multi-value tagging. departments and offices are returned as complete arrays — every tag a posting carries, not just the first.
• Internal requisition id included. requisitionId is Greenhouse's own req identifier, separate from the per-posting job id — a way to spot when the same underlying req is posted more than once.
• Decoded HTML descriptions. Turn on includeDescription and entities are decoded for you.
• Multi-board in one run. Pass a list of companies; a board that fails or was renamed is skipped with a logged warning, not a fatal error — the rest of your list still comes back.
• Dedup built in. onlyNewSinceLastRun (default on) persists the last 20,000 job ids seen, so a recurring schedule only bills for postings that are genuinely new.

Who uses it

Recruiters and sourcers, job-board and ATS aggregators, sales teams tracking a target account's hiring, labor-market analysts, and anyone building a "new roles at companies I follow" alert.

Company bundles - no company list needed

You do not need to know a single board slug to run this. Pick a bundle in presetLists, hit Start, and you get live postings straight away.

Bundle	Greenhouse boards	What it covers
top-tech	59	Large, well-known technology employers.
ai-ml	28	AI labs, ML infrastructure and applied-AI companies.
devtools	27	Developer tools, infrastructure, observability and security.
yc-backed	28	Y Combinator alumni, from recent batches to public companies.
fintech	26	Payments, banking, lending, crypto and financial infrastructure.
remote-first	26	Companies that hire remote-first or distributed by default.

Every slug in a bundle was checked against its live board on 2026-08-24 - a 200 response with at least one open role. Each bundle file carries its own verifiedAt date, and any board that stops answering is reported in the run's FAILED_TARGETS record instead of silently shrinking your results.

Bundles merge with anything you list yourself and are deduped, so you can start from a bundle and add your own companies to it.

Search every board we know - no company list at all

Turn on Search every board we know and you do not supply companies, slugs or bundles. The run queries our index of 617 verified greenhouse boards - 30,685 open roles at the last check on 2026-08-24 - and applies your title, location and remote filters across all of them.

Ask it things a company list cannot answer:

• every remote senior backend role posted this week
• everything matching "machine learning" across every board in the index
• new postings only, across the whole index, on a daily schedule

ATS	Boards
greenhouse	617

Every board in the index answered its ATS with at least one open role when the index was built. Boards are fetched most-active first and capped by Maximum boards to search (default 200), because each board is one request. The index is rebuilt on a refresh sweep; a board that stops answering three sweeps running is retired from it, and anything that fails during your run is reported in FAILED_TARGETS rather than silently shrinking your results.

Input

Field	What it does
searchIndex	No company list at all. Query every board in the shipped index and apply your filters across all of them. See the section above.
maxBoards	Only used with searchIndex. Each board is one request, so this caps run length. Boards are searched most-active first.
presetLists	Start here if you have no company list. One or more verified company bundles; every board in them was checked against the live API. Merges with anything you list yourself, deduped.
companies	One or more Greenhouse board tokens — the slug in job-boards.greenhouse.io/<token> (e.g. airbnb, stripe, gitlab).
maxPerCompany	Stop after this many jobs from each board, so one large employer cannot fill the whole result. Recommended with bundles. Empty = no cap.
titleIncludes	Keep only jobs whose title contains one of these keywords (case-insensitive). Empty = all. Applied before billing.
locationIncludes	Keep only jobs whose location contains one of these keywords. Empty = all. Applied before billing.
remoteOnly	Keep only remote-flagged roles (or locations mentioning remote). Applied before billing.
postedWithinDays	Keep only postings published in the last N days — 7 gives you this week's roles. Postings on boards that publish no date are left out, because they cannot be shown to be recent. Applied before billing.
includeDescription	Fetch each posting's full HTML description, decoded. Off by default for lean records.
includeSalary	Read pay out of the posting body into the salary fields. On by default; costs no extra requests, and does not add the body to the record.
onlyNewSinceLastRun	Recommended for schedules — skips jobs already returned by a previous run, so you're only charged for genuinely new postings. Default true.
maxItems	Stop after this many normalized records.
syncEnabled	Optional, off by default. Also send each new job straight to a connected app — see Sync below.
syncDestination, syncWriteTool, syncFieldMap, syncExtraArgs	Only used when syncEnabled is on.

Output

Field	Description
jobId	Greenhouse's per-posting job id.
company	The board token you queried.
title	Job title.
location	Primary posting location, as Greenhouse displays it.
departments	Array — every department this posting is tagged with.
offices	Array — every office this posting is filed under.
updatedAt	Last-modified timestamp on the posting.
firstPublished	When the posting first went live.
requisitionId	Greenhouse's internal requisition id — shared across postings that are really the same underlying req.
url	Public apply-page URL.
descriptionHtml	Decoded HTML description, only when includeDescription is on; otherwise null.
source	Always "Greenhouse".
companyName	The employer's display name, as opposed to the board token you queried.
employmentType	Always null — Greenhouse publishes no employment-type label. Use employmentTypeNormalized.
internalJobId	Greenhouse's internal job id.
education	Education requirement, where the board sets one.
applicationDeadline	Closing date, where the board sets one.
language	Posting language.
salaryMin / salaryMax	Pay range as plain numbers, so you can sort and filter on it. null when the posting does not state pay — never a guess.
salaryCurrency	ISO code (USD, EUR, GBP, …) where the posting makes it clear.
salaryInterval	YEAR, MONTH, WEEK, DAY or HOUR.
salaryText	The pay exactly as the posting worded it, kept so you can audit the parse.
salarySource	ats when the board published structured pay, ats-summary or description when it was read out of the posting text. null when no pay was found.
cityDerived / regionDerived / countryDerived / countryCodeDerived	The location string split into parts, so "Austin, TX" is filterable by state and country instead of by substring.
locationType	REMOTE, HYBRID or ONSITE.
seniorityLevel	INTERN, JUNIOR, SENIOR, STAFF, PRINCIPAL, MANAGER, DIRECTOR, VP or EXECUTIVE, read from the title. null when the title carries no signal.
employmentTypeNormalized	FULL_TIME, PART_TIME, CONTRACT, INTERN, APPRENTICESHIP or VOLUNTEER — one enum across every ATS, so records are comparable.
daysSincePosted	Whole days since the posting went live, precomputed.
organizationUrl	The public careers board this posting came from.

Pay coverage. Greenhouse publishes no structured pay field, so salaryMin/salaryMax are read out of the posting body. Coverage tracks how many of a board's postings state pay in the text — measured at 25 of 573 postings on a large US board in 08/2026. Boards in pay-transparency states fill far more of it.

This is a real record, captured live from the stripe board on 08/21/2026 — not a placeholder. locationType, seniorityLevel and employmentTypeNormalized are null on this one because the posting states nothing this actor could read them from; that is the intended behaviour, not a gap:

{
  "presetLists": ["top-tech"],
  "jobId": "7922618",
  "company": "stripe",
  "companyName": "Stripe",
  "title": "Account Executive, Existing Business, Platforms",
  "location": "New York, NY",
  "departments": [
    "Global Operations"
  ],
  "offices": [
    "US-PERM"
  ],
  "updatedAt": "2026-08-18T17:38:43-04:00",
  "firstPublished": "2026-06-02T16:49:53-04:00",
  "requisitionId": "See Opening ID",
  "url": "https://stripe.com/jobs/search?gh_jid=7922618",
  "descriptionHtml": null,
  "source": "Greenhouse",
  "salaryMin": 182208,
  "salaryMax": 236580,
  "salaryCurrency": "USD",
  "salaryInterval": "YEAR",
  "salaryText": "$182,208 - $236,580",
  "salarySource": "description",
  "cityDerived": "New York",
  "regionDerived": "NY",
  "countryDerived": "United States",
  "countryCodeDerived": "US",
  "locationType": null,
  "seniorityLevel": null,
  "employmentType": null,
  "employmentTypeNormalized": null,
  "daysSincePosted": 80,
  "organizationUrl": "https://job-boards.greenhouse.io/stripe",
  "internalJobId": "3443870",
  "education": "education_required",
  "applicationDeadline": null,
  "language": "en"
}

Which actor do I want?

• Tracking Greenhouse boards specifically, and want department/office tagging or the internal req id? You're in the right place.
• Tracking companies across Greenhouse and Lever, Ashby, SmartRecruiters, Recruitee or Workable in one feed? Use Job Postings Aggregator — one schema, one dedup layer, across all six ATS platforms. Its unified schema doesn't carry departments/offices/requisitionId — pull from here directly if you need those.
• Need a different single board? Lever Jobs Scraper (remote/hybrid/onsite detail) · Ashby Jobs Scraper (published salary) · Workable Jobs Scraper (description, requirements and benefits, split out)

Sync to your CRM, Notion, HubSpot, Airtable or Supabase (optional)

Turn on syncEnabled to also send each new job straight to a connected app — free, with no extra charge. Connect the app under Integrations in Apify Console, pick it as syncDestination, and set syncWriteTool to the name of the tool that creates one record there (run the dataset-sync-connector Actor in list-tools mode against the same connector if you don't know the name). A sync failure is logged as a warning and never blocks the dataset — your jobs always land here first regardless of what the destination does.

Pricing (Pay-Per-Event)

• query — charged once per run for the board poll, regardless of how many companies you list.
• job-record — charged per normalized job pushed (after dedup). This is the primary event.
• apify-actor-start (Apify-managed) — covers baseline compute per run.
• Sync to a connected app (optional) — free. No event is charged for records sent to a destination; it's an added convenience on top of the dataset you already paid for.

A daily monitor of a handful of companies returns a few new roles for pennies; a full-board pull of a large employer is a larger one-time run you control with maxItems.

Source & reliability

Data comes from Greenhouse's public boards-api.greenhouse.io service. No API key, no proxy needed. A board that 404s or fails is skipped with a logged warning — it doesn't fail the rest of your run. Run npm test for the offline self-test covering the normalizer and its edge cases.

FAQ

How am I charged?

A flat query event once per run, plus one job-record event per normalized job actually pushed to the dataset. With onlyNewSinceLastRun on (the default), a job already returned in a previous run (tracked by id, for the most recent 20,000 seen) is skipped and not re-charged.

Where does the data come from?

Greenhouse's public Job Board API (boards-api.greenhouse.io) — the same data Greenhouse's own careers pages are built from. No API key or proxy required.

How fresh is it?

Live at request time — there's no bundled or cached dataset behind this actor, it calls Greenhouse directly on every run. Schedule it (daily or weekly) to keep catching new postings; onlyNewSinceLastRun means a recurring schedule only bills for roles you haven't seen yet.

Which actor do I want?

See Which actor do I want? above — short version: single Greenhouse boards with department/office/req-id detail, stay here; multiple ATS platforms in one feed, use jobs-aggregator.

---

SEO keywords: Greenhouse jobs scraper, Greenhouse board API, job posting scraper, ATS scraper, new jobs feed, hiring signals, recruiting data API, job board aggregator