# Greenhouse Job Board Scraper (Official JSON API) (`ahmdshrif/greenhouse-jobs-api-scraper`) Actor Reads the official boards-api.greenhouse.io JSON feed for one or more company slugs and exports one flat row per job posting with title, location, requisition ID, apply URL, and posting dates. - **URL**: https://apify.com/ahmdshrif/greenhouse-jobs-api-scraper.md - **Developed by:** [Ahmed](https://apify.com/ahmdshrif) (community) - **Categories:** Jobs, Lead generation - **Stats:** 3 total users, 1 monthly users, 100.0% runs succeeded, 3 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing $0.05 / 1,000 run starteds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Greenhouse Job Board Scraper Reads the official `boards-api.greenhouse.io` JSON feed for one or more company slugs and exports one flat row per job posting — title, location, requisition ID, apply URL, and posting dates. Built for recruiters, sourcers, and job-board aggregators who need a clean, structured feed of every open role on a company's Greenhouse board without maintaining their own API integration. ### Why this scraper - Reads the official JSON API rather than the HTML board page, so postings come back as structured fields (job ID, requisition ID, dates, GDPR flag) instead of text scraped off a rendered page — nothing to break when Greenhouse changes its page layout. - Charged once per run, not per job. A board with 500+ open roles (Stripe, Databricks) costs the same flat fraction of a cent as a board with 5 roles, instead of scaling with job count. - No login, no CAPTCHA, no browser rendering — it's a direct read of a public API endpoint, so there's nothing fragile in the pipeline between you and the data. ### Output fields | Field | Type | Description | |---|---|---| | job\_id | integer | Greenhouse job posting ID | | title | string | Job title | | company\_name | string | Employer name as returned by Greenhouse | | company\_slug | string | Greenhouse board token parsed from the input URL, e.g. `stripe` | | location | string | Free-text location string for the posting | | absolute\_url | string | Public apply/listing URL for the job | | requisition\_id | string | Company-internal requisition identifier | | internal\_job\_id | integer | Greenhouse internal job ID | | updated\_at | string | ISO timestamp the posting was last updated | | first\_published | string | ISO timestamp the posting first went live | | application\_deadline | string | Application deadline if the company sets one, else empty | | education | string | Education requirement flag from Greenhouse | | language | string | Language code of the posting | | gdpr\_consent\_required | boolean | Whether the posting's GDPR data\_compliance entry requires applicant consent | ### Input ```json { "startUrls": [ { "url": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs" } ], "maxItems": 50 } ``` Add one object per company board to `startUrls` to pull multiple companies in a single run. ### Output ```json { "job_id": 8130725, "title": "Account Executive, AI Startups (Hunter)", "company_name": "Stripe", "company_slug": "stripe", "location": "San Francisco", "absolute_url": "https://stripe.com/jobs/search?gh_jid=8130725", "requisition_id": "See Opening ID", "internal_job_id": 3520748, "updated_at": "2026-08-19T14:02:07-04:00", "first_published": "2026-08-19T14:02:07-04:00", "application_deadline": "", "education": "education_required", "language": "en", "gdpr_consent_required": false } ``` ### Pricing Pay per event: **$0.00005 per run started** (charged once, regardless of how many boards or jobs are in that run). Scraping a single company's full board, or several boards in one run, costs a fraction of a cent. ### Use cases - Sourcers building a lead list of open roles at target companies for outbound recruiting. - Job-board aggregators syncing a Greenhouse-powered employer's listings into their own site on a schedule. - Talent teams tracking a competitor's hiring velocity by monitoring new `first_published` dates on their board over time. # Actor input Schema ## `startUrls` (type: `array`): Pages to export. ## `maxItems` (type: `integer`): Stop after this many records. ## Actor input object example ```json { "startUrls": [ { "url": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/databricks/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/figma/jobs" } ], "maxItems": 50 } ``` # Actor output Schema ## `results` (type: `string`): One structured record per input URL. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/databricks/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/figma/jobs" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("ahmdshrif/greenhouse-jobs-api-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [ { "url": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/databricks/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/figma/jobs" }, ] } # Run the Actor and wait for it to finish run = client.actor("ahmdshrif/greenhouse-jobs-api-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/databricks/jobs" }, { "url": "https://boards-api.greenhouse.io/v1/boards/figma/jobs" } ] }' | apify call ahmdshrif/greenhouse-jobs-api-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,ahmdshrif/greenhouse-jobs-api-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/YnKHn0rFvyPfTn7aw/builds/VVSLLdwys0OZoZHEp/openapi.json