Greenhouse Job Boards Scraper - All Openings, No API Key avatar

Greenhouse Job Boards Scraper - All Openings, No API Key

Pricing

from $0.50 / 1,000 results

Go to Apify Store
Greenhouse Job Boards Scraper - All Openings, No API Key

Greenhouse Job Boards Scraper - All Openings, No API Key

$0.5/1K ๐Ÿ”ฅ Greenhouse job board scraper! Every opening from any company career page with full descriptions. No key. JSON, CSV, Excel or API in seconds. Build job boards & hiring intel โšก

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

ninhothedev

ninhothedev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Greenhouse Job Boards Scraper

The dedicated Greenhouse board reader. Point it at any company slug and get every open position from that company's Greenhouse job board โ€” with the full, readable job description. No API key, no login, no cookies.

Greenhouse is the single most-used applicant tracking system among tech companies. Thousands of employers โ€” from seed startups to public companies โ€” publish their openings on boards.greenhouse.io/<slug> or an embedded Greenhouse widget on their own careers page. This Actor reads those boards directly through Greenhouse's free public Job Board API, so the data is exactly what the company publishes: structured, complete and current.


What you get

One dataset item per job opening:

FieldDescription
companyThe board token (company slug) the job came from
job_idGreenhouse public job ID
internal_job_idGreenhouse internal job ID
titleJob title
locationLocation string as published
departmentsList of department names
officesList of office names
descriptionFull description as clean, readable plain text (HTML entities decoded, tags stripped, max 8,000 chars)
description_htmlOriginal description markup (max 20,000 chars)
updated_atLast update, normalised to UTC ISO 8601
requisition_idCompany-internal requisition ID
is_remotetrue when the location or title signals remote / anywhere / distributed
employment_typeEmployment type, when the board publishes it as job metadata
metadataCompact [{name, value}] list of the board's custom fields (max 15)
apply_urlDirect link to the application page
sourceAlways greenhouse
scraped_atRun timestamp

Every field is nullable โ€” boards differ in how much they publish, and the Actor never invents data.

Sample output

{
"company": "figma",
"job_id": 5364702004,
"internal_job_id": 5178563004,
"title": "Account Executive, Emerging Enterprise (Berlin, Germany)",
"location": "Berlin, Germany",
"departments": ["Sales"],
"offices": ["Berlin, DE"],
"description": "Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all...",
"description_html": "<div class=\"content-intro\"><p>Figma is growing our team...</p></div>",
"updated_at": "2026-07-22T09:37:08Z",
"requisition_id": "1334",
"is_remote": false,
"employment_type": null,
"metadata": null,
"apply_url": "https://boards.greenhouse.io/figma/jobs/5364702004?gh_jid=5364702004",
"source": "greenhouse",
"scraped_at": "2026-07-28T17:44:02Z"
}

How to find a board token

The board token is the company slug in the Greenhouse URL. It is always lowercase.

  1. Straight from a Greenhouse board URL โ€” https://boards.greenhouse.io/stripe โ†’ token is stripe. New-style URLs work the same way: https://job-boards.greenhouse.io/figma โ†’ figma.
  2. From a company careers page โ€” open the careers page, click a job, and look at the URL or the apply link. If you see gh_jid= in the query string, the company uses Greenhouse. Then open the page source and search for greenhouse.io/ โ€” the segment right after it is the token. Many careers pages embed Greenhouse in an iframe pointing at boards.greenhouse.io/embed/job_board?for=<token>.
  3. Guess and check โ€” the token is very often the plain company name (gitlab, reddit, coinbase, robinhood, airbnb). Just try it: an unknown token is logged as a warning and skipped, it never kills the run.

Note that the token is not always the brand name โ€” DoorDash, for example, publishes under doordashusa, not doordash.

You can also paste a full board URL into boardTokens; the Actor reduces it to the slug for you.


Input

{
"mode": "boards",
"boardTokens": ["stripe", "figma", "doordashusa"],
"includeContent": true,
"titleFilter": "engineer",
"locationFilter": "remote",
"maxItemsPerBoard": 200,
"maxItems": 500
}
InputDefaultWhat it does
modeboardsCurrently one mode: read all jobs of the given company boards
boardTokens["stripe","figma","doordashusa"]The company slugs to scrape. Full board URLs are accepted too
includeContenttrueFetch full descriptions. Turn off for a much faster listing-only run
titleFilterโ€”Case-insensitive substring on the job title
locationFilterโ€”Case-insensitive substring on location and office names
maxItemsPerBoard200Cap per company โ€” handy when scraping many boards
maxItems500 (max 5,000)Global cap on dataset items

Unknown board tokens produce a warning and are skipped. The run only fails when no board returned a single job.


Pricing

Roughly $0.50 per 1,000 jobs. Each board is a single API call, so a run over dozens of companies costs cents and finishes in seconds. Descriptions come along in the same request โ€” there is no per-job fetch penalty.


Use cases

  • Job aggregators & job boards โ€” Greenhouse boards are the primary source for tech roles. One call per company gives you title, location, department, apply URL and the full description, ready to index and dedupe.
  • Recruiting intelligence โ€” track which teams a competitor is staffing, where they are opening offices, how quickly requisitions appear and disappear, and which roles stay open longest.
  • Hiring-trend analysis โ€” snapshot boards on a schedule and chart headcount plans by department, seniority and location. updated_at and requisition_id make it easy to diff runs.
  • Sales prospecting on hiring signals โ€” a company hiring five data engineers is buying a data stack. Filter descriptions for tools, certifications or platforms and turn open roles into a timed, well-qualified outbound list.

Notes

  • Data comes from Greenhouse's public Job Board API โ€” the same content any visitor sees on the board. No credentials are used and no candidate data is touched.
  • Greenhouse returns job descriptions HTML-entity-encoded. This Actor decodes them properly and gives you both a clean-text and an HTML version, so you never end up with &lt;p&gt; in your dataset.
  • Boards do not paginate: one request returns every open position, so results are complete and consistent.