Greenhouse Jobs Scraper — Company Job Boards

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
Delta monitoring	Built-in: only-new-since-last-run plus closed-posting detection, dedup rows never billed	Rare
Salary data	Structured pay-transparency ranges + optional AI fallback	Often absent
AI enrichment	Opt-in, bring your own Anthropic/Mistral key — you pay provider token prices, not a marked-up tier	Fixed-price add-on or absent
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.
postedSince	integer	—	Keep only postings first published within this many days. Postings with no posting date are dropped when this is set.
includeDescription	boolean	true	Include a plain-text description snippet per posting.
includeCompensation	boolean	false	Fetch structured pay data (pay_input_ranges) per posting → fills salary/salaryMin/salaryMax/salaryCurrency. One extra request per posting; only a minority of boards publish a range. See "Salary".
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".
onlyNewSinceLastRun	boolean	false	Delta/monitoring mode: only output postings not seen on a previous run made with this flag on (see "Delta mode / monitoring").
aiEnrichment	boolean	false	Adds aiKeySkills/aiExperienceLevel/aiWorkArrangement/aiVisaSponsorship per posting via the Anthropic or Mistral API — BYOK (see "AI enrichment").
aiProvider	string	anthropic	Which AI provider runs enrichment: anthropic (default, uses anthropicApiKey) or mistral (uses mistralApiKey).
anthropicApiKey	string (secret)	—	Your Anthropic API key. Only used when aiEnrichment is on and aiProvider is anthropic; billed separately by Anthropic, not by this Actor.
aiModel	string	claude-haiku-4-5-20251001	Claude model for AI enrichment (when aiProvider is anthropic): claude-haiku-4-5-20251001 (fast/cheap) or claude-sonnet-4-5 (higher quality).
mistralApiKey	string (secret)	—	Your Mistral API key. Only used when aiEnrichment is on and aiProvider is mistral; billed separately by Mistral, not by this Actor.
mistralModel	string	mistral-small-latest	Mistral model for AI enrichment (when aiProvider is mistral): mistral-small-latest (default, fast/cheap — matches larger Mistral models on this task), mistral-medium-latest, or mistral-large-latest.
concurrency	integer	8	Companies fetched in parallel (advanced).

What Greenhouse jobs data does this scraper extract?

One flat JSON record per live posting:

Field	Meaning
ats	Which ATS served the posting (always "greenhouse" here)
company	Real company display name, resolved from Greenhouse's own data (falls back to the input slug if unresolvable)
id	Greenhouse's internal job ID
title	Job title as posted
department	Department or team where provided
location	Location text (may include remote hints)
url	Direct link to the posting
postedAt	First-published date (YYYY-MM-DD) where provided
snippet	Plain-text description excerpt (optional)
salary	Display-text pay summary (e.g. 100,000-150,000 USD) — see "Salary". Null when unavailable
salaryMin / salaryMax	Numeric pay range when available, else null
salaryCurrency	ISO 4217 currency code (e.g. USD) when available, else null
salaryPeriod	Pay interval (year/hour) when the source states it; null on Greenhouse
questions	Only present when includeQuestions is on — application-form questions as {label, required} objects
globalId	Stable composite id <ats>:<company-slug>:<id> — unique across the whole ATS-actor family, handy for merging with the Lever/Ashby/Workable Actors or the Company Careers Bundle
warnings	Array of data-quality notes for this record (e.g. ["postedAt missing"]); empty array when there's nothing to flag
isNew	Only present when onlyNewSinceLastRun is on — always true (already-seen postings are dropped, never emitted with isNew: false)
isClosed	Only present in delta mode — a diagnostic row (true) for a posting seen on a prior run that is gone now (removed/closed). Not billed
aiKeySkills	Only present when aiEnrichment is on — array of skills/technologies explicitly named in the posting text, never invented
aiExperienceLevel	Only present when aiEnrichment is on — one of entry/mid/senior/lead/unknown
aiWorkArrangement	Only present when aiEnrichment is on — one of onsite/hybrid/remote/unknown
aiVisaSponsorship	Only present when aiEnrichment is on — true/false only if the posting explicitly states a policy, otherwise null

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 / postedSince / 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

{
  "ats": "greenhouse",
  "company": "Stripe",
  "id": "7954688",
  "title": "Senior Software Engineer",
  "department": "Engineering",
  "location": "San Francisco, CA",
  "url": "https://stripe.com/jobs/search?gh_jid=7954688",
  "postedAt": "2026-06-25",
  "employmentType": null,
  "remote": null,
  "snippet": "We are hiring a Senior Software Engineer...",
  "salary": null,
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "salaryPeriod": null,
  "globalId": "greenhouse:stripe:7954688",
  "warnings": []
}

Delta mode / monitoring

Set onlyNewSinceLastRun: true to turn this Actor into a "what's new" monitor. Postings already seen on a previous run made with this flag on are dropped before push — you are not billed for them, so pairing this with an Apify schedule (cron) means every run only returns, and only charges for, postings that showed up since the last flagged run.

How it works: seen postings are tracked in a dedicated key-value store, keyed by each posting's globalId, capped at roughly 50,000 entries (oldest evicted first). The first run made with the flag on has nothing to compare against yet, so it emits everything — all isNew: true. Every emitted record gets isNew: true stamped on it; there's no isNew: false in the output, since unseen postings just aren't included.

Closed detection: delta mode also emits an isClosed: true row for any posting that was seen on a prior flagged run and is gone now (removed/closed), giving you both halves of the diff — what opened and what closed — in one run. Closed rows are only emitted for companies that fetched successfully this run (a transient 404/network error never mass-marks a board's postings closed), carry just the globalId/company/ats (the posting content is already gone), and are not billed. Each closed posting is reported once.

Runs made with the flag off never read or write this cache — turning it on and off between runs is safe and has no side effects on normal runs.

Salary

Every record carries five compensation keys — salary (display text), salaryMin, salaryMax, salaryCurrency, salaryPeriod — the same shape the Lever and Ashby Actors populate from their own APIs, so a consumer merging the ATS family sees one consistent salary schema.

Greenhouse's public list API exposes no pay data at all, so these are null by default. There are two honest ways to fill them, neither fabricated:

• includeCompensation — fetches each posting's per-job detail endpoint and reads Greenhouse's structured pay-transparency data (pay_input_ranges). Costs one extra request per posting. Only a minority of boards publish a range, so many postings still come back with null salary — but when a board does publish, you get an exact structured min/max/currency.
• aiEnrichment (BYOK, see below) — the AI reads the description text and extracts a stated pay range into the same salary fields, only when the text explicitly states one (never guessed, never currency-converted). This is usually the higher-coverage path on Greenhouse, since pay-transparency ranges most often live in the description body rather than the structured field.

When both are on, a structured range from includeCompensation always wins; the AI-read value is only a fallback for postings that had no structured range.

AI enrichment

Turn on aiEnrichment and supply your own anthropicApiKey (or mistralApiKey, with aiProvider: "mistral") to add four AI-extracted fields to every posting:

Field	Meaning
aiKeySkills	Specific skills/technologies/tools explicitly named in the title or description — the model is instructed to never invent one.
aiExperienceLevel	One of entry / mid / senior / lead / unknown.
aiWorkArrangement	One of onsite / hybrid / remote / unknown.
aiVisaSponsorship	true / false only when the posting explicitly states a sponsorship policy, otherwise null.
salary / salaryMin / salaryMax / salaryCurrency	Filled from an explicit pay range stated in the description text (never guessed or currency-converted) — only when a structured range from includeCompensation isn't already present. See "Salary".

The extraction prompt is explicit about never guessing: when the text doesn't clearly support a value you get "unknown" / null / an empty array, not a fabricated answer. Pick the model with aiModel (Anthropic: claude-haiku-4-5-20251001 default, fast/cheap, or claude-sonnet-4-5 higher quality) or mistralModel (Mistral: mistral-small-latest default — matches larger Mistral models on this task, mistral-medium-latest, mistral-large-latest).

Postings are batched (~12 per call) through whichever provider's API you picked (aiProvider). Your Anthropic or Mistral API key is billed separately by that provider, not by this Actor. Rough cost with Haiku or Mistral Small: enriching 100 postings runs well under $0.05 in provider token spend (short prompts, small JSON replies); Sonnet/Mistral Large cost roughly 4-5x that for the same batch.

Enrichment needs a posting's description text even when you have includeDescription off — this Actor fetches it internally for enrichment either way, then still honors your includeDescription choice for what actually ends up in the output snippet field.

If aiEnrichment is on but no matching key is available (anthropicApiKey/ANTHROPIC_API_KEY for aiProvider: "anthropic", or mistralApiKey/MISTRAL_API_KEY for aiProvider: "mistral"), enrichment is skipped: you get one extra dataset row explaining why (warnings: ["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]), a run status message, and every other posting is still returned normally, just without the ai* fields.

This is the same class of field fantastic-jobs' career-site-api prices a whole tier on (ai_key_skills, work arrangement, visa signals) — comparable output here, opt-in and BYOK instead of bundled into every row's price.

Warning rows

Alongside normal posting records, this Actor can push a handful of extra rows that are all null except company/ats/warnings — same flat schema as a posting record, so a dataset-only consumer (no access to the run log) still sees every problem:

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"]
aiEnrichment requested but no API key available	["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]
An unexpected run-level error (run still ends succeeded)	["run error (...): ... — no further postings returned; see the run log. This row is not billed."]

Delta mode additionally emits isClosed: true rows (see "Delta mode / monitoring"). None of these 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, postedSince, caps) is applied before the billed push step — a filtered-out posting is never charged.
• Delta mode (onlyNewSinceLastRun) drops already-seen postings before billing, so a scheduled monitor only ever pays for genuinely new postings.
• Warning rows, closed-posting rows, and diagnostic rows are never billed.

If you turn on aiEnrichment, your Anthropic or Mistral key is billed separately by that provider for the enrichment calls themselves — see "AI enrichment" above for a rough per-100-postings cost estimate.

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 — since 2026-07 — you also get one dataset row for it: {"company": "<slug>", "ats": "...", "warnings": ["not found on any ATS probed (...): '<slug>' (404 on every probe)"]} (or "fetch failed on every ATS probed ..." for a network/5xx failure rather than a clean 404). Previously this was only visible in the run log, easy to miss across a 50-slug batch. 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.