Greenhouse Jobs Scraper - Any Company Job Board

Read the open jobs of any company that hires through Greenhouse and get them as clean, normalized JSON, CSV or Excel: title, department, location(s), remote flag, employment type, posting date, salary when published, full description (text and HTML) and apply link. No API key, no proxy, no browser and no login needed.

Two modes. Companies mode: you list Greenhouse companies (the board token, the last part of boards.greenhouse.io/<token> or job-boards.greenhouse.io/<token>) and get all their jobs. Discovery mode: leave Companies empty and the Actor scans the bundled directory of Greenhouse companies (biggest boards first, maxCompanies default 200) and filters the jobs live. Need other systems too? Use the Career Site Jobs Scraper, which covers Greenhouse, Lever, Ashby, Workable, Recruitee, Personio and Workday.

The directory: 4,140 Greenhouse company job boards, each checked live when the directory was built, with about 165,000 open jobs between them at that time. Companies not in the directory can always be read in Companies mode.

Who is it for

• Recruiters and sourcers who want a clean list of open roles at target companies, with location, department and salary.
• Job boards, newsletters and aggregators that need a fresh, structured feed taken from the employer's own career site.
• Market and talent analysts tracking who is hiring, for what, where and at what pay.
• AI agents and MCP users: every field is described in the dataset schema, so an agent can answer "which remote data jobs were posted this week" from the output.

What you get

One dataset item per job:

• jobId, ats, companyId, companyName
• title, department, team
• location, locations[], country, countryCode, isRemote, workplaceType (remote / hybrid / onsite), employmentType
• postedAt, updatedAt (ISO 8601, UTC)
• jobUrl, applyUrl
• descriptionText (clean text) and descriptionHtml
• salary with min, max, currency, period and the original raw text, when the employer published a range
• scrapedAt, sourceUrl, and an extras block with requisition id, offices, departments, custom metadata fields (such as the workplace type), application deadline

Only what the employer publishes in the job posting is returned. Names and e-mail addresses are not extracted into separate fields. Full field reference: ./SCHEMA.md and the Actor's dataset schema.

Input

Field	Description
companies	Greenhouse careers URLs, greenhouse:id entries or bare ids (the board token, the last part of boards.greenhouse.io/<token> or job-boards.greenhouse.io/<token>). Empty = Discovery mode
keywords	Keep jobs whose title contains any of these words (case-insensitive)
excludeKeywords	Drop jobs whose title contains any of these words
locations	Keep jobs whose location or country contains any of these texts; Remote also matches remote-flagged jobs
remoteOnly	Only jobs the employer marks as remote
postedWithinDays	Only jobs first published in the last N days (0 = no limit; jobs with no date are excluded when set)
includeDescription	Include description text and HTML (default true)
maxItems	Maximum jobs, newest first (default 20)
maxCompanies	Discovery mode: how many directory companies to scan (default 200)

Leaving the input empty reads one well-known company so the default run always works and returns 20 jobs in a few seconds.

Input example (Companies mode)

{
  "companies": [
    "airbnb",
    "stripe",
    "https://boards.greenhouse.io/databricks"
  ],
  "keywords": [
    "engineer"
  ],
  "locations": [
    "Remote"
  ],
  "maxItems": 100
}

Input example (Discovery mode)

{
  "companies": [],
  "keywords": [
    "data scientist"
  ],
  "remoteOnly": true,
  "postedWithinDays": 14,
  "maxCompanies": 100,
  "maxItems": 200
}

Output example

{
  "schemaVersion": "1.0",
  "jobId": "8306554",
  "ats": "greenhouse",
  "companyId": "airbnb",
  "companyName": "Airbnb",
  "title": "AirCover Specialist, Claims Experience",
  "department": "Community Support",
  "team": null,
  "location": "Canada",
  "locations": [
    "Canada"
  ],
  "country": null,
  "countryCode": null,
  "isRemote": true,
  "workplaceType": "remote",
  "employmentType": null,
  "postedAt": "2026-10-28T14:52:05+00:00",
  "updatedAt": "2026-10-28T14:52:05+00:00",
  "jobUrl": "https://careers.airbnb.com/positions/8306554?gh_jid=8306554",
  "applyUrl": "https://careers.airbnb.com/positions/8306554?gh_jid=8306554",
  "descriptionText": "Airbnb was born in 2007 when two hosts welcomed three guests to their San Francisco home, and has since grown to over 5 million hosts who have welcomed over 2 b...",
  "descriptionHtml": "<div class=\"content-intro\"><p><span style=\"font-family: helvetica, arial, sans-serif; font-size: 12pt;\">Airbnb was born in 2007 when two hosts welcomed three gu...",
  "salary": null,
  "scrapedAt": "2026-11-06T12:00:00+00:00",
  "sourceUrl": "https://boards-api.greenhouse.io/v1/boards/airbnb/jobs/8306554",
  "extras": {
    "requisitionId": "ONE",
    "internalJobId": 3591434,
    "language": "en",
    "offices": [
      "Canada"
    ],
    "departments": [
      "Community Support"
    ],
    "metadata": {
      "Is this job part of ACC?": false,
      "Workplace Type": "Remote"
    }
  }
}

Use cases

• Talent sourcing: every open engineering role at 50 target companies, refreshed daily.
• Job aggregation: a deduplicated feed of jobs taken from the employer's own site (stable job URLs and apply links).
• Hiring-trend research: count open roles by department, country or remote policy over time (schedule the Actor and compare datasets).
• Pay transparency: collect published salary ranges by role and country.
• AI agents (MCP): ask in plain language, get structured jobs back.

Data sources

• Greenhouse: Greenhouse Job Board API (boards-api.greenhouse.io), the public API Greenhouse offers so companies can show their jobs on their own website. Its documentation states that GET endpoints need no authentication.

All of these are public endpoints that need no account, key or login. The Actor identifies itself honestly with the User-Agent NexusScrapers-CareerSiteJobs/0.1 (+https://nexus-tools-dev.github.io/), reads robots.txt of every host (including Crawl-delay), limits concurrency per host, and backs off and retries on HTTP 429/5xx, then skips the company with a warning. It uses no proxies, no browser and no captcha handling. The employers' postings remain their property; you are responsible for using the data in line with the employer's terms and applicable law (for example, do not use postings to contact individuals).

Limits and good to know

• Greenhouse: salary is filled only when the company publishes a pay range on the board (common for US postings because of pay-transparency laws, rarer elsewhere). Up to 4 parallel requests per host.
• Company websites: only the single page you give is read. If that page builds its job list with JavaScript and does not mention the job board in its HTML (many do not), no board is found: give the job-board URL instead.
• Jobs are returned newest first within the companies scanned; in Discovery mode each company contributes at most max(10, maxItems/4) jobs, so results come from several companies, and scanning stops once enough matching jobs are collected.
• locations and keywords are plain text matches on what the employer wrote (no translation, no synonyms).
• A company that does not exist, has no open jobs or blocks access is skipped with a warning in the log; the run still succeeds if at least one company was read.

FAQ

Do I need an API key or a proxy? No. These are the public feeds the systems provide for career pages.

Is this legal? The Actor only reads publicly available job postings through public endpoints that allow anonymous access, respects robots.txt and rate limits, and does not collect personal data. This is not legal advice; check your own use case.

How fresh is the data? Live at run time: the feeds are read when the Actor runs. postedAt is the date the employer published the job.

Why is salary often empty? Only some employers publish ranges. When they do, you get min, max, currency and period.

Can I get only new jobs since my last run? Not built in yet; schedule the Actor and compare jobId values between runs, or use postedWithinDays.

What happens at the budget limit? The Actor stops at maxItems or when your run's maximum charge is reached, and returns what it already collected.

Pricing

Pay per result: each job written to the dataset is one result. You are never charged for more results than maxItems or your run's spending limit allow. See the Actor's pricing tab for the current price.

API, MCP and AI agents

Call the Actor from the Apify API, the JavaScript or Python clients, or schedule it. The dataset schema documents every field, so MCP-enabled AI agents can use the output directly.