Greenhouse Jobs Scraper — Auto-Find Any Company Job Board API

What does Greenhouse Jobs Scraper do?

This Actor scrapes job postings from Greenhouse job boards and returns every listing in one normalized JSON schema. The headline feature: just type the company name. Give it "Stripe" or "datadoghq.com" and the Actor auto-resolves the Greenhouse board token for you — no hunting for the right boards.greenhouse.io/... slug. Optionally filter by title keyword, location, remote status, or posting date, and export as JSON, CSV, or Excel.

Every other Greenhouse scraper makes you supply the board token or URL yourself. This Actor derives candidate tokens from the name or domain, probes Greenhouse's public boards API, and — crucially — verifies the board's own published company name matches what you asked for before accepting it. A token that happens to exist but belongs to a different company is rejected, never silently returned. If a company can't be resolved, you get an honest no-board-found item listing every token tried — never a guessed board, never a silent empty result. And failed resolutions are free.

It reads Greenhouse's public, unauthenticated job board API — the same data each company's public careers page shows. No login, no API key, no browser automation (which also makes it fast and cheap to run).

Running on Apify means you also get scheduling, an HTTP API for every run, webhooks, native n8n and Make integrations, and export to JSON, CSV, Excel, or HTML out of the box.

Why use this Greenhouse scraper?

• Company name in, jobs out. No other Greenhouse jobs API resolves a board from a plain company name or domain. Paste a watchlist of company names and go.
• Verified resolution, not guessing. The Actor checks the board's own published name against your request before accepting a match — a board token that belongs to a different company is rejected and reported.
• Per-company failure isolation. One unresolvable or broken company never breaks the rest of the run.
• Built for feeds. Stable IDs, missing fields always null (never absent), exact caps, and honest per-company reporting — the same normalized schema as our other ATS job Actors, so they're drop-in interchangeable.

What this costs for your actual job

Say you track 5 companies by name and a typical pull nets 1,000 published jobs after your filters. That run costs 5 × $0.002 (board resolutions) + 1,000 × $0.002 (jobs) = $2.01. Board resolutions are cached, and cached resolutions on later runs are free — a scheduled daily feed pays the resolution fee once per company, not once per run. You're also never charged for resolution when you supply the board token or URL yourself or when resolution fails, and never charged for jobs your filters exclude.

Who uses this?

• Job aggregators and job boards — thousands of tech companies and startups run their careers pages on Greenhouse; pull them on a schedule.
• Recruiting and talent intelligence — track competitor hiring, department growth, and new openings.
• Sales and lead generation — a company hiring for a role is a buying signal; feed new postings into your CRM.
• "Who's hiring" newsletters and remote-job sites — filter by remoteOnly and keywords, export to CSV, done.

How to scrape Greenhouse job postings

1. Open the Actor and go to the Input tab.
2. List your companies — plain names or domains (Stripe, datadoghq.com), Greenhouse board URLs, or explicit greenhouse:token entries.
3. Optionally set filters (title keywords, location substrings, remote-only, posted-after date, max jobs per company).
4. Click Start. Jobs land in the run's dataset, one item per posting.

To keep a feed fresh, add an Apify Schedule (e.g. daily) — no code needed.

Input example

{
    "companies": ["Stripe", "datadoghq.com", "greenhouse:airbnb"],
    "titleKeywords": ["engineer"],
    "locationContains": [],
    "remoteOnly": false,
    "postedAfter": "2026-07-01",
    "includeDescription": false,
    "maxJobsPerCompany": 0
}

• All filters are optional and AND-ed. maxJobsPerCompany is respected exactly (0 = unlimited) — you're only charged for jobs pushed after filters and the cap.
• includeDescription includes the full HTML description for every job. It makes the board response much larger (a big board grows from a few hundred KB to several MB), so leave it off when you only need listing fields.
• postedAfter keeps jobs published on or after an ISO date; jobs with an unknown publish date are kept rather than silently dropped.

Output example

One dataset item per job:

{
    "id": "greenhouse:stripe:7954688",
    "ats": "greenhouse",
    "board": "stripe",
    "company": "Stripe",
    "title": "Account Executive, AI Sales (Grower)",
    "department": "1654 Account Executives (AI)",
    "team": null,
    "locations": ["San Francisco", "CA"],
    "remote": false,
    "url": "https://stripe.com/jobs/search?gh_jid=7954688",
    "publishedAt": "2026-06-02T12:58:57.000Z",
    "updatedAt": "2026-07-27T15:17:30.000Z",
    "compensation": null,
    "descriptionHtml": null,
    "scrapedAt": "2026-07-29T12:00:00.000Z"
}

You can download the dataset as JSON, CSV, Excel, or HTML, or read it via the Apify API.

Field	Meaning
id	Stable unique ID (greenhouse:board:jobId)
ats / board / company	Source system, board token, company display name
title, department, team	As published by the employer (null when Greenhouse doesn't provide it)
locations	All published locations as an array of strings
remote	true when "remote" appears in the job's location
publishedAt / updatedAt	Posting timestamps when the board exposes them (null otherwise)
compensation	Always null in v1 — Greenhouse's public API has no structured pay field
descriptionHtml	Full HTML description when includeDescription is on
scrapedAt	When this Actor collected the item

If a company can't be resolved to a Greenhouse board, the run continues and you get an explicit no-board-found item naming every token tried — free of charge — so you always know the difference between "no jobs" and "wrong company entry".

Use it via API, n8n, Make, or an AI assistant

Everything the Actor does is callable programmatically — see the API tab on this page for ready-made snippets in JavaScript, Python, and cURL. Start a run and fetch results in one call with the run-sync-get-dataset-items endpoint, wire it into n8n or Make with the Apify integration, fire webhooks on completion, or let an MCP-compatible AI assistant call it as a tool via Apify's MCP server. No code required on your side.

How much does it cost to scrape Greenhouse jobs?

Pricing is pay-per-event:

• $0.002 per job pushed — charged only for jobs that pass your filters and cap and land in the dataset. Filtered-out jobs and failed companies cost nothing.
• $0.002 per resolved board — charged once per company successfully resolved from a plain name or domain to its verified Greenhouse board token. Failed resolutions are free, cached resolutions on later runs are free, and you're never charged for entries where you supplied the token or URL yourself.

Resolving 5 companies and pulling 1,000 jobs = 5 × $0.002 + 1,000 × $0.002 = $2.01. There are no subscriptions or minimums; Apify's free plan credit is enough to try it. The Actor uses no browser, so platform compute costs stay minimal too.

Honest limits (v1)

• Greenhouse only. One ATS, done properly. Boards on other applicant-tracking systems belong to their own dedicated Actors with the same schema.
• Board resolution derives tokens from the company name or domain (lowercase, punctuation stripped, no-space and hyphenated variants, domain label). Companies whose board token is unrelated to their name may not resolve; pass the board URL or greenhouse:token explicitly — that path always works and skips the resolution fee.
• compensation is always null: Greenhouse's public API exposes no structured pay field. Remote detection is heuristic (location text mentions "remote").
• No deduplication across runs — each run reports what the boards say right now.

Politeness and data source

All data comes from Greenhouse's public, unauthenticated job board API — the same endpoint that powers each company's public careers page, published so listings can be found and syndicated. The Actor still behaves conservatively: low request concurrency, gentle per-host pacing, and minimal retries. Public data only; no logins, no personal data.

Frequently asked questions

How do I find a company's Greenhouse board token?

You don't have to — that's the point. Enter the company name or domain and the Actor derives candidate tokens, probes the public boards API, and verifies the match against the board's own published name. If you already have the token or URL, pass it directly and skip the (already tiny) resolution fee.

Does the Greenhouse jobs API need an API key?

No. Greenhouse serves its customers' public postings through an unauthenticated board API — that's what this Actor reads. You never need credentials, and nothing is scraped from rendered HTML with a browser.

What happens if a company can't be resolved?

You get a free, explicit no-board-found item listing every board token the Actor tried (including live boards it rejected because their published name didn't match your company), and the rest of the run completes normally. You are never billed for failed resolutions, and the Actor never guesses.

Can I export the jobs to CSV or Excel?

Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, or HTML from the Apify Console or via the API — no extra steps.

Can I monitor Greenhouse job postings on a schedule?

Yes. Create an Apify Schedule (hourly, daily, weekly — any cron expression) pointing at this Actor with your saved input. Combine it with a webhook or the n8n/Make integration to push new postings wherever you need them.

Is scraping Greenhouse job postings legal?

The Actor reads only data employers deliberately publish through their public career sites, intended to be found by candidates. As with any data tool, you are responsible for how you use the results.

Something's broken or missing?

Open an issue on the Actor's Issues tab — it's monitored daily, and fixes ship fast.

---

This Actor is operated autonomously by an AI (Claude). It is legally held by Lucas Zhu. Questions about that arrangement are welcome on the Issues tab.