Greenhouse Job Board API - Jobs & Departments avatar

Greenhouse Job Board API - Jobs & Departments

Pricing

from $1.50 / 1,000 results

Go to Apify Store
Greenhouse Job Board API - Jobs & Departments

Greenhouse Job Board API - Jobs & Departments

Greenhouse job board API alternative: scrape jobs, departments and offices without an API key. Export Greenhouse ATS career-page data to CSV or JSON.

Pricing

from $1.50 / 1,000 results

Rating

0.0

(0)

Developer

Logiover

Logiover

Maintained by Community

Actor stats

0

Bookmarked

34

Total users

0

Monthly active users

5 days ago

Last modified

Features

Limited permissions

Share

Greenhouse Job Board API Scraper โ€” Tech Jobs, Departments & Offices (No API Key)

Greenhouse Job Board Scraper โ€” Jobs, Departments & Offices

Apify Actor No API key Pay per result Jobs Export

The unofficial Greenhouse Job Board API in a single Apify Actor. Scrape every open job, full description, department and office from any company hosted on Greenhouse โ€” Airbnb, Stripe, Anthropic, Mistral AI, Datadog, Doctolib, Ramp and 5,000+ more tech companies โ€” all with one input. Pure HTTP, no login, no captcha, no API key, sub-second per board.

๐Ÿ† Why this Greenhouse scraper?

5,000+ companies in one Actor ยท 5 modes (jobs / jobDetail / board / departments / offices) ยท full HTML + plain-text descriptions ยท pay ranges & compliance fields ยท client-side filters ยท export to JSON / CSV / Excel. The unofficial Greenhouse Job Board API alternative for HR tech, hiring-signal lead-gen and AI career agents.


โœจ What this Actor does / Key features

  • ๐Ÿข 5,000+ companies in one Actor โ€” pass a list of board tokens and cover every Greenhouse customer.
  • ๐Ÿ”€ 5 modes โ€” jobs (all open jobs), jobDetail (questions and pay ranges for specific job IDs), board (company board profile), departments (department tree), offices (office tree).
  • ๐Ÿ”“ No auth, no anti-bot โ€” Greenhouse's GET endpoints are fully public and not rate-limited.
  • ๐Ÿ“„ Full job content โ€” complete HTML descriptions, decoded by default, with an optional plain-text version.
  • ๐Ÿงฉ Structured metadata โ€” custom fields like employment type, full/part-time and visa sponsorship as a keyโ†’value map.
  • ๐ŸŒณ Departments & offices โ€” returned as structured trees with parent/child relationships.
  • โœ… Compliance fields โ€” GDPR dataCompliance flags, plus EEOC and demographic questions in jobDetail mode.
  • ๐Ÿ’ต Pay ranges โ€” salary data via includePayRanges when the employer publishes it.
  • ๐Ÿ”Ž Client-side filters โ€” by department, office, location, title keyword and language.
  • โšก Parallel fetching โ€” configurable concurrency across many boards in one run.

๐Ÿš€ Quick start (3 steps)

  1. Configure โ€” pick a mode (start with jobs) and add one or more boardTokens (the slug after boards.greenhouse.io/, e.g. anthropic).
  2. Run โ€” click Start. The Actor fetches every board in parallel, applies your filters and streams jobs into your dataset.
  3. Get your data โ€” open the Output tab and export to JSON, CSV, Excel, HTML or JSONL, or pull it via the Apify API.

๐Ÿ“ฅ Input

Set mode and at least one boardTokens value. Everything else is optional.

Example โ€” all engineering & research jobs at three AI labs

{
"mode": "jobs",
"boardTokens": ["anthropic", "mistralai", "ramp"],
"fullContent": true,
"stripHtml": true,
"filterDepartments": ["Engineering", "Research"],
"filterLocations": ["San Francisco", "London", "Remote"],
"concurrency": 5
}

Example โ€” job detail with pay ranges & application questions

{
"mode": "jobDetail",
"boardTokens": ["stripe"],
"jobIds": [5501234, 5501987],
"includeQuestions": true,
"includePayRanges": true
}

Example โ€” department tree for a single company

{
"mode": "departments",
"boardTokens": ["airbnb"]
}
FieldTypeDescription
modestring (enum)Required. jobs, jobDetail, board, departments, or offices. Default jobs.
boardTokensarrayGreenhouse board tokens โ€” the slug after boards.greenhouse.io/ (e.g. airbnb, stripe, anthropic). Fetched in parallel.
jobIdsarrayNumeric job IDs to fetch in jobDetail mode. Scoped to the first board token.
fullContentbooleanIn jobs mode, include full HTML description, departments and offices. Default true.
includeQuestionsbooleanIn jobDetail mode, include application, EEOC, location and demographic questions. Default false.
includePayRangesbooleanIn jobDetail mode, include configured pay ranges. Default false.
decodeContentbooleanDecode HTML entities in the content field. Default true.
stripHtmlbooleanAlso produce a plain-text contentText field. Default false.
filterDepartmentsarrayCase-insensitive substring match against department names.
filterOfficesarrayCase-insensitive substring match against office names.
filterLocationsarrayCase-insensitive substring match against the job's location name.
filterTitleKeywordsarrayCase-insensitive substring match against job titles.
filterLanguagesarrayMatch the job's language field (ISO 639-1 codes like en, fr).
maxResultsPerBoardintegerCap jobs saved per board. 0 = no cap.
concurrencyintegerParallel board fetches, 1โ€“20. Default 5.

Finding a company's board token: open the company's careers page. If the URL is boards.greenhouse.io/<slug>, that slug is the token. If they embed a Greenhouse iframe, view source and look for boards-api.greenhouse.io/v1/boards/<slug>/....

Additional input fields

These optional fields are also available in the input form and API:

FieldTypeDefaultDescription
maxResultsinteger333Global cap across all boards. Keeps the default empty-input run fast and cheap. Set 0 for no overall limit.

๐Ÿ“ค Output

Every item is tagged with _mode, boardToken and scrapedAt. Here is a trimmed sample record from jobs mode:

{
"_mode": "jobs",
"boardToken": "anthropic",
"id": 4757432,
"internalJobId": 4409871,
"title": "Staff Software Engineer, Inference",
"companyName": "Anthropic",
"requisitionId": "ENG-1187",
"locationName": "San Francisco, CA | London, UK",
"absoluteUrl": "https://boards.greenhouse.io/anthropic/jobs/4757432",
"language": "en",
"departmentNames": ["Engineering"],
"officeNames": ["San Francisco", "London"],
"updatedAt": "2026-07-03T18:22:11-04:00",
"firstPublished": "2026-06-18T09:00:00-04:00",
"applicationDeadline": null,
"contentText": "About the role: We are looking for a Staff Software Engineer toโ€ฆ",
"scrapedAt": "2026-07-06T12:00:00Z"
}

๐Ÿ’ก Use cases

  • HR tech & job aggregators โ€” power a meta-search with near-real-time tech job inventory.
  • Sales intelligence & lead generation โ€” hiring signals are a strong B2B growth proxy; a spike in Engineering hires flags a hot lead.
  • Recruitment agencies โ€” track which companies open which roles, in which cities, with what salary bands.
  • VC & scout tools โ€” hiring velocity is leading-indicator data for portfolio monitoring.
  • Compensation intelligence โ€” combine pay ranges, titles and locations to build salary benchmarks.
  • AI agents & career tools โ€” feed structured job data into assistants for career-coaching and company research.

๐Ÿ‘ฅ Who uses it

HR-tech & ATS product teams ยท job-board & meta-search operators ยท recruitment & staffing agencies ยท B2B sales & growth teams mining hiring signals ยท VCs & scouts tracking hiring velocity ยท comp-intelligence analysts ยท AI career-agent builders.

๐Ÿ’ฐ Pricing

This Actor runs on a simple pay-per-result model โ€” you pay for the items you extract, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

โ“ Frequently Asked Questions

Do I need a Greenhouse API key or login? No. The Greenhouse Job Board API GET endpoints are fully public. This Actor is read-only โ€” you only need an Apify account.

Is it legal to use this data? The Actor consumes the public Greenhouse Job Board API, which Greenhouse documents as publicly accessible. The data is what employers chose to publish on boards.greenhouse.io. Respect each employer's terms and your local data-protection laws when redistributing. This Actor is not affiliated with Greenhouse Software, Inc.

Can I filter the jobs? Yes โ€” by department, office, location, title keyword and language. Filtering is client-side because the Greenhouse public API does not accept query filters; the Actor fetches the full list and filters before saving.

How fresh is the data? Real-time. The Greenhouse Job Board API serves the current state of each board the moment you call it โ€” there is no scraping lag.

Is there a salary field? Sometimes. Check metadata/metadataMap (some employers publish salary as a custom field), payInputRanges in jobDetail mode with includePayRanges enabled, and the free-form content HTML.

Can I detect newly posted jobs since my last run? Yes โ€” diff against id, or use updatedAt and firstPublished to identify brand-new posts.

Is this a Greenhouse job board API alternative?

Yes. It wraps the public Greenhouse Job Board API and normalizes the output, so you get a ready-to-use Greenhouse job board API alternative without building or maintaining your own integration.

How do I scrape Greenhouse jobs without an API key?

Just pass one or more board tokens โ€” no API key, login or captcha is required. Greenhouse's GET endpoints are public, so this Actor reads them directly to scrape Greenhouse jobs without any credentials.

How do I export Greenhouse jobs to CSV or JSON?

Run the Actor and download the dataset as CSV, JSON, Excel, HTML or JSONLines. This makes it a simple way to export Greenhouse ATS career-page data to CSV or JSON for spreadsheets, databases or AI agents.

How do I scrape all open jobs from a company's Greenhouse board?

Set mode to jobs and add the company board token (the slug after boards.greenhouse.io/). The scraper returns every open role with full HTML description, department and office, ready to export.

๐Ÿ”— More job & hiring scrapers by logiover

Building a jobs dataset or a hiring-signals pipeline? Pair the Greenhouse scraper with the rest of the jobs suite:

ActorWhat it does
Lever Postings ScraperJobs from any Lever-hosted careers board
Welcome to the Jungle Jobs ScraperEuropean tech & startup job listings
SEEK Jobs ScraperAustralia & New Zealand's largest job board
USAJOBS ScraperUS federal government job openings
Jobicy Remote Jobs ScraperCurated remote-job listings
The Muse Jobs ScraperJobs plus company culture profiles
Indeed Jobs ScraperThe world's largest job aggregator
Himalayas Remote Jobs ScraperGlobal remote jobs with company data
Hacker News "Who is Hiring?" ScraperMonthly HN hiring thread by company/role/stack
Built In Tech Jobs ScraperUS tech-hub startup & scale-up jobs

๐Ÿ‘‰ Browse all logiover scrapers on Apify Store โ€” 180+ actors across real estate, jobs, crypto, social media & B2B data.

โฐ Scheduling & integration

Schedule the Actor on Apify to run daily for an always-fresh tech-jobs dataset. Export to JSON, CSV or Excel, call it from the Apify API, or wire it into Airtable, Google Sheets, Postgres, S3 or Slack with webhooks and no-code tools like Make, n8n and Zapier.

๐Ÿค– AI Agents, MCP & RAG Integration

Greenhouse Job Board API works natively as an on-demand data tool for AI assistants and autonomous workflows.

Connect this Actor directly to Apify AI, Claude Desktop, Cursor, VS Code, Windsurf, LangChain, or LlamaIndex via the official Apify MCP Server โ€” no custom wrapper code needed:

{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com?tools=logiover/greenhouse-job-board-scraper"
}
}
}
  • Schema-typed inputs & outputs: Clean JSON records with explicit .actor/input_schema.json and .actor/output_schema.json definitions so LLM agents infer parameters and parse fields accurately without HTML noise.
  • Bounded & predictable runs: Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
  • RAG & automation ready: Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.

๐Ÿ’ฌ Support, Issues & Reviews

This Actor consumes the public Greenhouse Job Board API and extracts only data employers chose to publish. It is intended for legitimate research, analytics and lead-generation use. You are responsible for complying with each employer's terms and your local data-protection laws. This Actor is not affiliated with Greenhouse Software, Inc.


Keywords: greenhouse job board api, greenhouse scraper, greenhouse jobs scraper, tech jobs scraper, ats scraper, career page scraper, hiring signals data, recruitment intelligence, greenhouse api alternative, scrape greenhouse jobs without api key, export greenhouse jobs to csv, greenhouse career page data extraction


How much Greenhouse data can you extract in one run?

A single run returned 1,000 job ads in 3 seconds on the example input, and it was still going when the measurement stopped โ€” raise the result limit and it keeps paginating. That is roughly 10,000 job ads a minute.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Greenhouse itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing โ€” so it is worth starting small and scaling once the output looks right.

Greenhouse scraping โ€” frequently asked questions

Do I need a Greenhouse API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Greenhouse data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want โ€” CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Greenhouse scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the job ads you care about really do change that fast.

How many job ads can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

This Actor collects only information that Greenhouse publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Greenhouse blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows โ€” so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

๐Ÿ“ Changelog

2026-11-14

  • Verified live high-volume benchmark (2026-11-14): extracted 650 structured records in 2.6s on the production build.
  • Hardened internal proxy stall fallback and pay-per-event dataset instance budget protection.

2026-11-11

  • Added reliable terminal run status telemetry and structured Apify AI / MCP Server (mcp.apify.com) tool configuration.
  • Added direct Issues & Reviews support links and refreshed live maintenance verification.

2026-11-01

  • Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
  • README refreshed: 2 links to retired Actors removed; documented 1 additional input field.

2026-10-15

  • A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
  • A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
  • Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
  • Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
  • The default used when the field is left out for maxResults is now 6,666 (was 1,000).

2026-09-23

  • Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
  • Output verified on a live run: 24 columns returned, 83.3% of cells populated.
  • Run reliability reviewed: 100.0% of public runs succeeded in the last 30 days.
  • Input schema, output schema and pricing configuration reviewed.
  • Noted that 4 column(s) came back empty in this sample (applicationDeadline, contentText, metadata, metadataMap); these are under review.

2026-09-01

  • Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
  • Reviewed for the failure patterns that have cost this fleet runs โ€” unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
  • No change to input, output fields or scraping logic.

2026-08-11

  • Maintenance release: refreshed the build and dependencies.
  • Re-verified live execution, non-empty structured output and dataset field/type integrity.
  • Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

2026-08-01

  • Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
  • Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
  • Declared 24 dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder.
  • Declared 25 nullable dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder or brittle to sparse modes.

2026-07-06

  • โœจ README overhaul: shields badge row, richer trimmed output sample, collapsible full field reference, extra ready-to-run examples (jobDetail + departments), jobs-suite cross-links and clearer quick-start.

2026-07-01

  • Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
  • Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
  • Added ready-to-run example tasks that cover common real-world use cases.

2026-06-15

  • Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

2026-06-07

  • Docs: added coverage for using this as a Greenhouse job board API alternative, scraping Greenhouse jobs without an API key, and exporting Greenhouse jobs to CSV/JSON.

2026-06-05

  • ๐Ÿ›ก๏ธ Reliability fix: results are no longer dropped by strict output validation โ€” runs now complete cleanly even at high volume (thousands of results).
  • โšก Stability & performance hardening; fresh rebuild.

2026-06-04

  • Verified live & refreshed build โ€” reliability/maintenance pass.

2026-06-01

  • Maintenance & reliability pass: pulled the latest source and rebuilt the Actor on the current base image; build verified.

*Maintained: last verified 2026-11-14 โ€” checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).