Greenhouse Jobs Scraper — Company Job Boards

Claude / Codex skill to describe and setup this actor: SKILL.md

Scrape any company's Greenhouse job board through the official public JSON API — pass company slugs, get clean structured postings. No login, no proxies, no breakage.

Why this Actor

Most Greenhouse scrapers parse careers-page HTML or drive a headless browser through proxy pools — and the Store's public run stats show it: some of the most-installed Greenhouse scrapers succeed on fewer than half of their runs. This Actor reads Greenhouse's official public JSON API instead. There is nothing to render, nothing for a bot-blocker to block, and nothing to break when a careers page is redesigned.

	This Actor	Typical Greenhouse scrapers
Data source	Official public Greenhouse JSON API	HTML parsing / headless browser
Proxies	None needed (no proxy cost hidden in the price)	Often datacenter → residential escalation
Reliability	Runs succeed even when a board 404s — you get a warning row, never a failed run	Failed runs on blocks and redesigns
Start fee	None — pay per posting only	Varies
Filters (title/location/department/date)	Applied before billing — you only pay for postings you keep	Applied after scraping, if at all

Input

Field	Type	Default	Description
companies	array	—	Company slugs as used on boards.greenhouse.io/<slug> (full board URLs also accepted). Leave empty to run against a built-in list of ~20 well-known Greenhouse boards (zero-setup first run).
keyword	string	—	Case-insensitive substring match on the job title. Applied before billing.
titleExclude	array	—	Drop postings whose title contains any of these substrings (case-insensitive). Applied before billing.
locationFilter	string	—	Case-insensitive substring match on the location. Applied before billing.
departmentFilter	string	—	Case-insensitive substring match on the department/team (e.g. engineering). Applied before billing.
postedWithin	string	any	Keep only jobs published inside this window. Use any for no date filter, or a duration — 1h, 24h, 3d, 2w, 6m. Jobs the source gave no date for are dropped rather than guessed at. Replaces postedSince, still accepted for existing integrations.
includeDescription	boolean	true	Include a plain-text description snippet per posting.
includeQuestions	boolean	false	Fetch each posting's application-form questions → questions array ({label, required}). One extra request per posting.
maxItemsPerCompany	integer	100	Cap postings returned per company (0 = no cap). Each result is a billed event. If the cap actually cuts postings for a company, one extra dataset row flags it (warnings: ["truncated ..."]) — see "Warning rows".
maxItems	integer	200	Hard cap on total postings returned (0 = no cap). Each result is a billed event. If the cap actually cuts postings, one extra dataset row flags it (warnings: ["truncated ..."]) — see "Warning rows".
concurrency	integer	8	Companies fetched in parallel (advanced).

What Greenhouse jobs data does this scraper extract?

Published postings follow nomad-agent-job-row-v1. The shared fields carry source identity, title and company, parsed locations, dates, the complete plain-text body when available, source markup when usable, and work type. Unavailable scalar facts are null; no parsed location is []. Source-only facts appear in versioned custom.data only when mapped there. See the Output example section for the exact dataset fields and diagnostic rows.

remote and employmentType are always null on this Actor. Both keys are still present on every record — kept for schema consistency with the Lever / Ashby / Workable / Company Careers Bundle Actors — but Greenhouse's public API exposes neither a remote/workplace-type signal nor an employment-type field on any endpoint, so this Actor never guesses. Use locationFilter (e.g. "remote") as the closest available proxy for remote roles.

How to scrape Greenhouse jobs with this Actor

1. Enter one or more company slugs (stripe, gitlab, duolingo). Open the company's careers page and look for boards.greenhouse.io/
2. Optionally set keyword / titleExclude / locationFilter / postedWithin / caps.
3. Run and export JSON, CSV or Excel — or call it over the API:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("nomad-agent/greenhouse-jobs-scraper").call(run_input={
    "companies": ["stripe", "gitlab", "duolingo"],
    "keyword": "engineer",
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["company"], "|", item["title"], item["url"])

curl -X POST \
  "https://api.apify.com/v2/acts/nomad-agent~greenhouse-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["stripe", "gitlab", "duolingo"]}'

Output example

Every row follows nomad-agent-job-row-v1, the one shape shared by all of this fleet's job Actors. A row carries every field; null means the source did not publish that fact, and locations: [] means no usable location was parsed from the posting. Nothing is guessed.

{
  "schemaVersion": "nomad-agent-job-row-v1",
  "recordType": "posting",
  "source": "greenhouse",
  "id": "a1b2c3",
  "url": "https://example.com/greenhouse/jobs/a1b2c3",
  "title": "Senior Backend Engineer",
  "company": "Example Company",
  "locations": [
    "Bilbao",
    "Spain"
  ],
  "postedAt": "2026-09-02T00:00:00Z",
  "deadline": "2026-10-15",
  "description": "The complete posting body as plain text, exactly as the source published it — never truncated.",
  "descriptionHtml": "<p>The complete posting body as the source's own markup.</p>",
  "workType": "remote",
  "custom": {
    "schemaId": "nomad-agent-job-custom-greenhouse-v1",
    "data": {
      "globalId": "…",
      "department": "…",
      "questions": "…"
    }
  }
}

Field	Meaning
schemaVersion	Always "nomad-agent-job-row-v1".
recordType	"posting" for a job, "diagnostic" for a row reporting something about the run itself.
source	Which job source the posting came from, from the collector registry's vocabulary — not the Actor name.
id	Stable identifier for the posting within source.
url	Canonical public URL of the posting on the source site.
title	Job title exactly as the source publishes it, untruncated.
company	Employer name as published.
locations	Places the role is based, most specific first — e.g. ["Bilbao", "Spain"].
postedAt	When the source published the posting, ISO-8601 UTC (YYYY-MM-DDTHH:MM:SSZ).
deadline	Closing date for applications as an ISO-8601 calendar date (YYYY-MM-DD).
description	The complete posting body as plain text — never truncated, never summarised.
descriptionHtml	The posting body as the source's own markup, preserving lists, headings and links.
workType	Working arrangement: "remote", "hybrid" or "onsite".
custom	Facts only this source publishes, as {"schemaId", "data"}.

A run also emits diagnostic rows — recordType: "diagnostic" with a warnings array — when it has something to report, such as a source returning nothing. They are never billed and are easy to filter out on recordType.

Warning rows

Diagnostic rows use schemaVersion: "nomad-agent-job-row-v1", recordType: "diagnostic", a warnings array and optional docs. They carry no posting fields and are not billed as job results. A dataset consumer can filter them by recordType:

Trigger	Example warnings
A requested company slug 404'd (or hard-failed) on every ATS probed	["not found on any ATS probed (greenhouse): 'acme-corp' (404 on every probe)"]
maxItemsPerCompany actually cut postings for one company	["truncated for 'acme-corp': maxItemsPerCompany=100 returned 100 of 137 matching postings — raise maxItemsPerCompany to get the rest"]
maxItems actually cut the total run	["truncated: maxItems=200 returned 200 of 340 matching postings — raise maxItems to get the rest"]
An unexpected run-level error (run still ends succeeded)	["run error (...): ... — no further postings returned; see the run log. This row is not billed."]

None of these warning rows are billed as a result event — only genuine postings are. Pass 50 company slugs in one run and you can tell exactly which ones need fixing straight from the dataset, instead of hunting through the run log.

Integrations

Export results as JSON, CSV or Excel/XLSX, or pipe them straight into Make, Zapier or n8n. Call this Actor synchronously with run-sync-get-dataset-items, or plug it into any AI agent through the Apify MCP server.

Pricing

Pay per posting returned — the current per-result rate is on this page's pricing tab. No subscription, no proxy surcharge (none are used), and you only pay for postings you keep:

• Every filter (keyword, titleExclude, locationFilter, departmentFilter, postedWithin, caps) is applied before the billed push step — a filtered-out posting is never charged.
• Warning and diagnostic rows are never billed.

Use cases

• Track hiring at specific companies (competitors, targets, portfolio)
• Build company-careers pages and job boards without HTML scraping
• Recruiting intelligence: who opens which roles, where, how fast
• Feed AI matching agents with reliable ATS-direct data

FAQ

Is it legal to scrape Greenhouse jobs? The data comes from the ATS providers' official, public, unauthenticated JSON APIs — the same data any visitor sees on the company's careers page. Review the providers' terms for your use case.

Do I need an API key or login? No. These are public job-board APIs — no authentication of any kind.

What if a company isn't found? The run continues with the other companies and emits an unbilled diagnostic row whose warnings names the missing slug and whether it was a clean 404 or a fetch failure. Full board URLs are also accepted and reduced to slugs automatically. See "Warning rows".

Why is remote always null? How do I get remote jobs only? Greenhouse's public API doesn't expose a remote/workplace-type field on any endpoint — not on the job list, not on the board root. Rather than guess from free-text location strings, this Actor reports null faithfully. Use locationFilter: "remote" to approximate it instead.

How fresh is the data? Every run hits the ATS APIs live. No caching layer in between.

Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and fixes ship fast.

Related Actors

• Lever Jobs Scraper — Company Job Postings API
• Ashby Jobs Scraper — Company Job Boards API
• Workable Jobs Scraper — Company Job Boards
• Company Careers Scraper — Greenhouse Lever Ashby
• Web Developer Jobs Scraper — 10 Boards in One
• LinkedIn Jobs Scraper — No Login, No Cookies

---

From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.