Greenhouse Jobs Scraper

Greenhouse Jobs Scraper extracts one structured dataset record for each public Greenhouse opening. Recruiters, talent-intelligence teams, and job-market researchers can provide known board tokens or board URLs and receive titles, locations, departments, descriptions, application URLs, timestamps, and source provenance for current hiring analysis.

Best fit for this Actor

• Choose this actor when a company already exposes a public Greenhouse board and you need the board's current job records in a consistent dataset.
• Use board tokens or public board URLs, then filter on title, location, or department before results are written.
• Use each returned sourceApiUrl, jobUrl, and scrapedAt field to support a source-linked recruiting or market-research workflow.

Focused standalone workflow

This actor is designed as a focused standalone workflow for public Greenhouse boards. It works well for teams that already know the employer boards they want to monitor and want a clear, source-linked dataset for each collection.

Recruiting workflow: from board token to outreach priority

A talent researcher starts with a shortlist of employers that use Greenhouse. They provide the board tokens, then filter for engineering and remote roles. The actor returns title, location, departmentNames, updatedAt, and applyUrl; next, the researcher exports the dataset to compare open roles and prioritize employer outreach or job-market reporting.

Quick start input

{
  "boardTokens": ["stripe", "https://job-boards.greenhouse.io/openai"],
  "maxResultsPerBoard": 100,
  "titleIncludes": "engineer",
  "locationIncludes": "remote",
  "departmentIncludes": "engineering",
  "includeDescriptions": true
}

boardTokens accepts raw Greenhouse tokens and public board URLs. maxResultsPerBoard sets a clear collection boundary for each supplied board.

Input reference

Field	Type	What it controls
boardTokens	array	One or more public Greenhouse board tokens or board URLs.
maxResultsPerBoard	integer	Validated result boundary for each board.
titleIncludes	string	Case-insensitive title text selection.
locationIncludes	string	Case-insensitive public location selection.
departmentIncludes	string	Case-insensitive public department selection.
includeDescriptions	boolean	Detailed public description HTML and clean text in each record.

What data you receive

Each dataset item is one public Greenhouse job post. Source URLs and collection timestamps make the item useful for current, reviewable downstream work.

Field	Meaning
jobId, boardToken, companyName	Stable public identity for the job and its board.
title, location, departmentNames	Public role and organization fields for filtering and analysis.
descriptionText, applyUrl	Public role detail and direct employer application path.
updatedAt, scrapedAt, sourceApiUrl	Freshness and provenance for each observation.

{
  "jobId": "127817",
  "internalJobId": "144381",
  "companyName": "Example Labs",
  "boardToken": "example",
  "title": "Senior Software Engineer",
  "location": "Remote — United States",
  "departmentNames": ["Engineering"],
  "officeNames": ["New York"],
  "officeLocations": ["New York, NY"],
  "descriptionHtml": "<p>Build reliable APIs.</p>",
  "descriptionText": "Build reliable APIs.",
  "applyUrl": "https://boards.greenhouse.io/example/jobs/127817",
  "jobUrl": "https://boards.greenhouse.io/example/jobs/127817",
  "requisitionId": "REQ-50",
  "language": "en",
  "metadata": null,
  "sourceApiUrl": "https://boards-api.greenhouse.io/v1/boards/example/jobs?content=true"
}

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~greenhouse-jobs-scraper/runs?token=$APIFY_TOKEN" \
  -H "content-type: application/json" \
  -d '{"boardTokens":["stripe"],"maxResultsPerBoard":25}'

Read the default dataset after the collection completes. OUTPUT provides the compact outcome and RUN_SUMMARY provides board coverage, source diagnostics, and charged event counts.

Use with AI agents through Apify MCP

As an AI agent, collect up to 25 current public engineering roles from the Greenhouse board stripe. Return each title, location, department, application URL, updated timestamp, and source URL. Read the dataset and report the run outcome, preserve provenance, and keep the collection within the stated result boundary and cost scope.

The actor is read-only and returns the dataset plus an OUTPUT outcome. An agent can use sourceApiUrl, jobUrl, and scrapedAt to present a current, traceable collection.

Pricing

This actor uses Pay per event plus Apify platform usage. A validated job written to the dataset is the billable event; filters are applied before dataset writes. Open the live Pricing tab for current event details, and use the result boundary to align collection cost with the workflow.

Best results

• Provide known, public Greenhouse board tokens when the workflow starts with selected employers.
• Use title, location, and department text to create a focused current dataset for a specific recruiting question.
• Schedule repeat collections when ongoing hiring changes inform a decision, and compare updatedAt with scrapedAt for freshness context.
• Preserve sourceApiUrl and jobUrl when sharing results so collaborators can validate each public opening.

Builder's note

I designed the output around one public job post because that keeps filtering, dataset readback, and employer-level joins clear. I found that preserving both the public application URL and the Greenhouse API source gives researchers useful provenance while the clean description text supports direct analysis.

Responsible use

Use public or authorized data in accordance with applicable laws, site terms, and your organization's data-handling practices. Keep source URLs with shared records so recipients can review the employer's public posting.