# Greenhouse Jobs Scraper — New Postings Since Any Date (`publicrecords/greenhouse-jobs-scraper`) Actor

Scrape open jobs from any Greenhouse job board and return only postings published since a date or window (24h, 7d, 30d). Title, location, department, URL, description. Pay per result.

- **URL**: https://apify.com/publicrecords/greenhouse-jobs-scraper.md
- **Developed by:** [Public Records](https://apify.com/publicrecords) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 1,000 job posting returneds

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Greenhouse Jobs Scraper — New Postings Since Any Date

Give it one or more Greenhouse board tokens and a date or window. It returns every open job posting on those boards that was published since then — title, location, department, employment type, URL and (optionally) the full description — newest first. Leave `since` empty to get every open posting.

**The one question it answers:** which roles did these companies post on Greenhouse since my last run?

Built for recruiters and sourcers watching target companies, sales and partnership teams prospecting on hiring activity, job-board aggregators, and anyone scheduling a daily "new roles" feed into Sheets, Slack, Make, Zapier or n8n.

### How it works

- Reads the company's public Greenhouse job-board API directly (comes from the same board response — no extra requests). No login, no proxies, no scraping of HTML pages.
- `since` is applied to the board's `first_published` timestamp (when the job was first published; later edits do not move it). Timestamps are returned in UTC ISO-8601.
- `updated_at` is also returned.
- Runs are stateless: a run with `since: 24h` on a daily schedule is a clean daily delta, with no storage to manage.

### Input

| Field | What to put | Default |
|---|---|---|
| `companies` | Greenhouse board tokens, one per line — or paste the board URLs (https://boards.greenhouse.io/\<token>) | required |
| `since` | `24h`, `7d`, `2w`, or an ISO date/time (`2026-09-01`, `2026-09-01T10:00:00Z`). Empty = all open postings | empty |
| `maxResults` | Cap across all companies, newest first. Each returned posting is one result | 500 |
| `includeDescription` | Add the plain-text description to each posting | false |

Identifiers can be pasted as full URLs; the Actor extracts the slug.

### Output

One dataset item per posting:

`ats`, `company`, `job_id`, `title`, `url`, `apply_url`, `published_at`, `updated_at`, `location`, `locations[]`, `workplace_type`, `department`, `team`, `employment_type`, `compensation`, `description`, `source_url`, `fetched_at`, `run_since`

Fields the board does not state are `null` — nothing is inferred from text. `source_url` is the exact API URL each record came from.

The run's key-value store holds `RUN_SUMMARY`: per-company status (`ok`, `ok_empty`, `not_found`, `rate_limited`, `upstream_error`, `malformed_payload`, `contract_drift`), counts of postings found, matched, charged and pushed, and the build that produced them. A company that an unknown board token returns `not_found` for that company; the run still returns the other companies.

### Pricing

Pay per result: a small run start fee plus a fee per posting returned. Postings are charged only when they are delivered — errors, empty boards and unknown identifiers cost nothing beyond the start fee. Set **Max total charge** on the run to cap spend; the Actor returns the newest postings up to that cap and reports how many it left out.

### Limits and guarantees

- Public boards only — private or internal postings are not available from the API and are not returned.
- Up to 1,000 identifiers per run; up to 100,000 results.
- Rate limits and outages are retried with backoff; if a board still fails, its status is reported and the run continues.
- If every identifier fails, the run fails — so a scheduled run never silently returns nothing.

### Integrations

Works with the Apify API, scheduler and webhooks, and with Make, Zapier, n8n, Google Sheets, Slack and MCP through the standard Apify integrations. A daily schedule with `since: 24h` plus a Slack or Sheets integration is the common setup.

### Attribution

Data from the company's public Greenhouse job-board API. This Actor is not affiliated with Greenhouse.

# Actor input Schema

## `companies` (type: `array`):

The token in the board URL: https://boards.greenhouse.io/<token> or https://job-boards.greenhouse.io/<token>. One per line, or paste the URLs.

## `since` (type: `string`):

Return only postings published on or after this point. A window like 24h, 7d, 2w, or an ISO date/time such as 2026-09-01 or 2026-09-01T10:00:00Z. Leave empty for every open posting.

## `maxResults` (type: `integer`):

Cap on postings returned across all companies, newest first. Each returned posting is one billable result.

## `includeDescription` (type: `boolean`):

Add the plain-text job description to every posting.

## Actor input object example

```json
{
  "companies": [
    "gitlab",
    "cloudflare"
  ],
  "since": "30d",
  "maxResults": 50,
  "includeDescription": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        "gitlab",
        "cloudflare"
    ],
    "since": "30d",
    "maxResults": 50,
    "includeDescription": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("publicrecords/greenhouse-jobs-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "companies": [
        "gitlab",
        "cloudflare",
    ],
    "since": "30d",
    "maxResults": 50,
    "includeDescription": True,
}

# Run the Actor and wait for it to finish
run = client.actor("publicrecords/greenhouse-jobs-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 '{
  "companies": [
    "gitlab",
    "cloudflare"
  ],
  "since": "30d",
  "maxResults": 50,
  "includeDescription": true
}' |
apify call publicrecords/greenhouse-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,publicrecords/greenhouse-jobs-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 <APIFY_API_TOKEN>` 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/MQKJ08m31wtmSvzAN/builds/J2K3rErgg7hpxQ2UY/openapi.json