Greenhouse Jobs Scraper

Export open jobs from company Greenhouse boards you supply for recruiting research, job-board feeds, hiring-market analysis, or a careers-page archive. Each row contains the job title, description, location, departments, application URL and source timestamps. No login or API key is needed.

This is not a global jobs index. It does not discover all companies or provide historical, closed, private or internal openings. Supply a board token such as stripe, a boards.greenhouse.io / job-boards.greenhouse.io company URL, or a documented boards-api.greenhouse.io/v1/boards/TOKEN/jobs URL. Job URLs select that job's company board, not just the individual job. Custom company career domains and embedded-board URLs are not supported; extract their Greenhouse token yourself.

Start with one job

{"boards":["stripe"],"maxJobs":1,"keyword":"","location":""}

This explicitly targets Stripe's public board and returns at most one job total. No board is silently substituted when input is missing or invalid.

Several boards and optional filters

{"boards":["stripe","https://job-boards.greenhouse.io/databricks"],"maxJobs":100,"keyword":"engineer","location":""}

• boards: 1–50 supported board tokens or HTTPS board URLs. Duplicate tokens/URLs resolve to one board.
• maxJobs: 1–10,000, default 1. One global cap across all boards, in caller order.
• keyword: optional case-insensitive substring of the job title, not a full-text or regex search.
• location: optional case-insensitive substring of the public location name. “Remote” is a text match, not a remote-work guarantee.
• Both filters must match. No filters means all currently available jobs, up to the global cap. Source order is preserved; no guaranteed newest-first sort.

Output

The dataset overview displays title, company, board, location, departments, link and update time. JSON/CSV/Excel export is available through Apify. Fields: boardToken, jobId, title, companyName, location, departments, offices, descriptionHtml, descriptionText, jobUrl, updatedAt, firstPublishedAt, requisitionId, sourceUrl, scrapedAt. Optional source fields can be null; departments/offices are lists. scrapedAt is extraction time, not posting time. Descriptions and external links are untrusted source content; sanitize HTML before rendering it.

Pricing

The Actor charges $0.0004 per delivered job ($0.40 / 1,000), with one job event and no start fee. Examples: 1 delivered job = $0.0004; 100 = $0.04; 1,000 = $0.40. These are Actor event fees, not a promise about any separately billed Apify services. Consult the live pricing tab for the effective price.

The SDK clips delivered rows to the event budget, and the Actor stops fetching before starting another request when no further job fits. Set Apify's maximum charge to a positive amount: a cap below $0.0004 delivers no jobs. Do not use zero as a zero-spend guarantee: the platform may treat zero as unset. Empty results generate no job events; platform resources may still be consumed.

Source and practical limits

Uses only the documented public Greenhouse Job Board GET API, pinned to https://boards-api.greenhouse.io. No authentication, applications POST endpoint, proxies, cookies, redirects or access bypass. No individual applicant, resume or application data is requested. Greenhouse is not affiliated with this Actor. Respect applicable source terms, rights and privacy laws; public access does not grant unlimited republication rights.

The API lists a whole company board, not a paginated global database. Small requests retrieve a description-free list plus selected job details; larger requests retrieve descriptions with the board list. Consequently a one-job cap does not limit upstream bytes to one job. Responses above 25 MB fail safely. The default runtime is 128 MB / 180 seconds; unusually large boards may need 256 MB. A missing board, malformed data, non-2xx HTTP response, redirect or network failure fails the run instead of quietly producing sample data. Earlier delivered rows may remain if a later board fails. Zero matching jobs on a valid board is a successful empty result.

Duplicates are suppressed by board token + job ID within a run and its durable resume. Separate runs intentionally produce fresh snapshots. On resume, durable rows are compared against restored charged-event counts. Unreadable, duplicated or inconsistent history fails closed rather than charging twice. Dataset writes and charge API calls are not transactional: an interrupted write/charge sequence can leave an orphan row and requires investigation, not automatic rebilling. One compact SUMMARY record reports source requests, board sizes, delivered counts and why extraction stopped.