Greenhouse Jobs Scraper
Pricing
from $0.50 / 1,000 job results
Greenhouse Jobs Scraper
Scrape job postings from any Greenhouse job board: title, location, remote flag, department, apply URL and dates. Official public API — no key, no proxies. Pay per result, no subscription.
Pricing
from $0.50 / 1,000 job results
Rating
0.0
(0)
Developer
Fabrikit
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
15 hours ago
Last modified
Categories
Share
Scrape job postings from any company's Greenhouse job board — just paste board slugs or careers-page URLs and get every open position back as clean JSON: title, location, remote flag, department, direct apply URL and posting dates. No API key, no login, no proxies, no browser: the Actor reads Greenhouse's official public Job Board API, so runs finish in seconds and never break when a careers page changes its design. Export to JSON, CSV, Excel, Google Sheets or your database.
What you get from a single run:
- Every open job at every company you list — thousands of companies hire through Greenhouse (Stripe, GitLab, Duolingo, Databricks, ...), and each posting comes back with the same clean fields, deduplicated.
- Zero setup and zero breakage risk: this is the same battle-tested Greenhouse connector that powers our multi-ATS scraper, reading
boards-api.greenhouse.iodirectly instead of parsing HTML. - A per-company summary (jobs found, boards not found, any errors) in the run's key-value store, so pipelines can verify coverage automatically.
Example output item (real posting from a live run):
{"ats": "greenhouse","company": "gitlab","companyName": "GitLab","sourceId": "8620720002","title": "Backend Engineer (Ruby), AI Engineering: Agent Observability","location": "Remote, Canada","allLocations": ["Remote, Canada"],"remote": true,"department": "AI Engineering","url": "https://job-boards.greenhouse.io/gitlab/jobs/8620720002","applyUrl": "https://job-boards.greenhouse.io/gitlab/jobs/8620720002","publishedAt": "2026-07-08T10:30:39.000Z","updatedAt": "2026-08-10T20:52:46.000Z","description": null,"scrapedAt": "2026-08-21T01:59:56.231Z"}
How to scrape Greenhouse job postings
- Add one entry per company to companies. Any of these formats works:
- The board slug — the identifier in the careers URL:
boards.greenhouse.io/stripe→stripe. - The full board URL —
https://boards.greenhouse.io/gitlaborhttps://job-boards.greenhouse.io/stripe(embed URLs with?for=<slug>work too).
- The board slug — the identifier in the careers URL:
- Press Start. Results land in the dataset within seconds and can be downloaded as JSON, CSV or Excel, or pushed to Sheets, webhooks, Zapier, Make or the Apify API.
Example input
{"companies": ["duolingo","https://boards.greenhouse.io/gitlab"],"maxJobsPerCompany": 50,"includeDescription": false}
- companies (required) — list of Greenhouse board slugs or URLs.
- maxJobsPerCompany — cap per company;
0= the full board. The form prefills50so your first run stays small and cheap. - includeDescription — add the full plain-text job description to each item (larger dataset).
Example: full boards with descriptions
{"companies": ["stripe", "databricks"],"maxJobsPerCompany": 0,"includeDescription": true}
A run like this returns 1,000+ postings in well under a minute.
Greenhouse job board API — output fields
| Field | Type | Description |
|---|---|---|
ats | string | Always greenhouse (compatible with our multi-ATS scraper's schema) |
company | string | The board slug you passed in |
companyName | string | Company display name from the board |
sourceId | string | Greenhouse posting ID (stable across runs — perfect for diffing) |
title | string | Job title |
location | string | null | Primary location as shown on the posting |
allLocations | string[] | All listed offices/locations |
remote | boolean | null | true if detected as remote, null if the posting doesn't say |
department | string | null | Department |
url | string | Public posting URL |
applyUrl | string | Direct application URL |
publishedAt | string | null | ISO 8601 first-published date |
updatedAt | string | null | ISO 8601 last-updated date |
description | string | null | Plain-text description (only if includeDescription) |
scrapedAt | string | ISO 8601 timestamp of this run |
What can you build with Greenhouse jobs data?
- Niche job boards — remote-only, one industry, one region — refreshed automatically on a schedule.
- Recruiting intelligence & talent mapping: which target companies are hiring for which roles, right now.
- Sales & investing signals: a competitor opening 30 engineering roles is a growth signal you can query daily.
- Lead generation for recruiters and agencies: companies actively hiring for the roles you place.
- LLM pipelines: one consistent schema means one prompt — pipe the dataset into an LLM via Apify integrations or MCP.
Pricing — how much does it cost to scrape Greenhouse jobs?
This Actor uses Apify's pay-per-event model and charges per job returned (event job-result) plus a tiny run-start fee. Platform usage is included: no subscription, no rental fee, no proxy costs — the Actor talks to an official public API, so compute usage is minimal. From 30 October 2026, 1,000 jobs cost US$2 on the Apify Free plan; paid Apify plans pay less per job — see the Pricing tab for your plan's rate. At the Free-plan rate, a 50-company sweep returning 5,000 jobs costs about US$10. You only pay for jobs actually delivered to your dataset.
Integrations
Run the Actor and read results from your own code with the Apify API — or connect the dataset to Google Sheets, n8n, Zapier, Make, Slack or webhooks directly from Apify Console with no code at all. Schedule it hourly, daily or weekly, and use LangChain or LlamaIndex through their Apify integrations. AI agents in Claude, ChatGPT, Cursor and other MCP clients can find and run it through Apify's MCP server. Downloads come as JSON, CSV or Excel.
Python (pip install apify-client):
from apify_client import ApifyClientclient = ApifyClient("<YOUR_API_TOKEN>")run = client.actor("fabrikit/greenhouse-jobs-scraper").call(run_input={"companies": ["stripe", "gitlab"],"maxJobsPerCompany": 0,})for job in client.dataset(run["defaultDatasetId"]).iterate_items():print(job["title"], "-", job["location"], job["url"])
JavaScript (npm i apify-client):
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });const run = await client.actor('fabrikit/greenhouse-jobs-scraper').call({companies: ['stripe', 'gitlab'],maxJobsPerCompany: 0,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(`${items.length} jobs`);
Performance & limits
- Speed: one HTTP request per company board — a full 800-job board downloads in ~2 seconds; 1,379 jobs from two boards took under 10 seconds in testing.
- No pagination limits: Greenhouse's board API returns the complete board in one response;
maxJobsPerCompany: 0always gets everything. - No proxies, no browser: minimal platform usage, no extra costs, nothing to configure.
- Reliability: the source is the official API Greenhouse itself serves careers pages from. If a board doesn't exist, the Actor logs it in
SUMMARYwith"error": "board not found"and continues with the rest.
Tips for best results
- Start with the prefilled input (2 companies, 50 jobs each) to see the schema, then set
maxJobsPerCompany: 0for full boards. - Leave
includeDescriptionoff unless you need the text — datasets stay small and exports fast. - Monitoring: schedule the Actor daily and diff on
sourceId— it is stable per posting, so new/removed IDs are new/closed jobs, andupdatedAtcatches edits. - Filter remote jobs downstream on the
remotefield (true/null), or onallLocationsfor specific offices. - Company not on Greenhouse? Use our ATS Jobs Scraper — same schema, and it auto-detects Greenhouse, Lever, Ashby and SmartRecruiters boards.
FAQ
Does Greenhouse have a public API for job postings?
Yes. Greenhouse publishes an official, unauthenticated Job Board API (boards-api.greenhouse.io/v1/boards/<slug>/jobs) — the same one that powers companies' careers pages. This Actor reads it directly, which is why it needs no API key, no login and no proxies, and why it's far more reliable than scrapers that parse careers-page HTML.
How do I find a company's Greenhouse board slug?
Open the company's careers page and look at the URL: boards.greenhouse.io/stripe → slug stripe. Or don't bother — paste the full URL and the Actor extracts the slug itself. Embedded boards (boards.greenhouse.io/embed/job_board?for=acme) work too.
Can I export Greenhouse jobs to CSV or Excel? Yes. Every Apify dataset downloads as CSV, Excel, JSON, XML or HTML with one click, or syncs to Google Sheets — no code needed.
Is it legal to scrape Greenhouse job postings? See Is it legal to scrape Greenhouse? below.
How many companies can I scrape in one run? There's no hard limit — one request per company means even hundreds of boards complete in minutes. For very large sweeps, split the list across scheduled runs.
Can it monitor new job postings on a schedule?
Yes — schedule the Actor in Apify Console (hourly, daily, weekly) and connect the dataset to Sheets, a webhook, Slack or your ATS. sourceId is stable per posting, so downstream dedup across runs is trivial.
What if a company uses Lever or Ashby instead of Greenhouse? Use our ATS Jobs Scraper — Greenhouse, Lever, Ashby & SmartRecruiters: the same normalized schema across the four biggest ATS platforms, with auto-detection when you don't know which one a company uses.
Does it include the full job description?
Yes — set includeDescription: true and each item carries the full plain-text description (HTML stripped), ready for keyword filtering or LLM processing.
Support
Found an issue or need a field this Actor doesn't return yet? Open an issue on the Actor's Issues tab — we aim to answer issues within 24 hours.
Is it legal to scrape Greenhouse?
This Actor only reads job data that Greenhouse publishes through an official public API intended for exactly this purpose (powering careers pages and job boards), without logging in. The structured fields describe jobs, not people, but full descriptions (includeDescription) can mention a recruiter or hiring manager by name, which is personal data under laws such as the EU GDPR, Chile's Ley 21.719 or the California CCPA; you are responsible for a lawful purpose. Respect Greenhouse's and each employer's terms, and link back to the original posting when you republish jobs. This is general information, not legal advice.
Use with AI agents
Use this actor to list every open job on one or more companies' Greenhouse job boards (by slug or careers URL), optionally with the full description.
{ "companies": ["gitlab"], "maxJobsPerCompany": 20 }
Main output fields: company, companyName, title, location, allLocations, remote, department, url, applyUrl, publishedAt, updatedAt, and description with includeDescription. It is pay-per-event: an agent pays a small start fee plus a fixed price per job saved, not for compute time.
Related actors
- ATS Jobs Scraper — Greenhouse, Lever, Ashby & SmartRecruiters — need more than Greenhouse? The same normalized job schema across the four biggest ATS platforms, with ATS auto-detection and a remote-only filter.
- Seek Jobs Scraper — job ads from Seek Australia and New Zealand.
- GetOnBrd Jobs Scraper — tech jobs in Latin America with USD salary ranges.
- TrustRadius Reviews Scraper — what customers say about the software companies you track.
- App Reviews Scraper — App Store & Google Play — reviews from both mobile stores in one run and one schema.
Ready-made examples
Technical details
- Data source (official, public, unauthenticated):
boards-api.greenhouse.io/v1/boards/<slug>/jobs?content=true. - Accepts bare slugs,
boards.greenhouse.io/job-boards.greenhouse.io/ EU-region URLs, and embed URLs (?for=<slug>). - Items are deduplicated within a run by
company:sourceId. - Plain HTTP with a 30 s timeout per request; no headless browser, no proxy usage.
- A per-company run summary is stored in the key-value store under
SUMMARY. - Output schema is a strict subset of our ATS Jobs Scraper's schema — you can switch or mix the two without changing downstream code.
Changelog
- 2026-10-16 — README: legal notes, AI-agent usage, related actors, example task and more integrations added; pricing text updated.
- 2026-10-15 — Tiered pricing announced, effective 2026-10-30 (lower per-job price on paid Apify plans).
- 2026-08-26 — Published on the Apify Store with pay-per-event pricing.
- 2026-08-21 — Build 0.1.1: initial release — slugs and careers URLs (including embed and EU boards), full boards in one request, optional descriptions, per-company summary.