Greenhouse Job Change Feed

Turn public Greenhouse job boards into structured records with clean descriptions, stable IDs, source links and content fingerprints. Use the output for job-board feeds, hiring research, or automated agents that need to track postings from specified companies.

What it returns

Each delivered record contains one job observation. Missing source fields remain null; the Actor does not invent salaries or company information.

Fields	Meaning
id, provider, board, sourceJobId	Stable record identity and source board
title, company, location, departments	Source-supplied job details
description	Job description converted to plain text
url, source	Original posting and public source API
sourcePublishedAt, sourceUpdatedAt	Available source timestamps
language, requisitionId	Available source metadata
observedAt	Time this run observed the posting
fingerprint	SHA-256 fingerprint of the normalized content
change	new, changed, or unchanged relative to your snapshot

Start with a company board

Supply the board token from a public Greenhouse board, such as stripe.

{
  "boards": ["stripe"],
  "maxResults": 1000,
  "maxRequests": 1,
  "maxSeconds": 90,
  "changesOnly": false
}

The default dataset contains job records. The default key-value store contains REPORT with completeness, limits and errors, and SNAPSHOT with fingerprints for your next comparison. Read REPORT before treating a run as a full inventory.

Return only changed jobs

Pass the prior run's SNAPSHOT JSON as previousSnapshot and enable changesOnly. The Actor suppresses unchanged records. Without a baseline, returned jobs are new to this run. Observation time and source update time alone do not trigger a content change.

Snapshots are caller-managed; this Actor does not retrieve them from earlier runs automatically. There is no shared customer snapshot. Jobs absent from a later response are retained in the snapshot and are never declared closed. A partial run updates fingerprints only for delivered records, so comparisons do not imply a complete publishing history.

Input and run limits

• boards: 1–20 Greenhouse tokens, containing letters, numbers, underscores or hyphens.
• maxResults: 1–10,000 delivered records; default 1,000.
• maxRequests: 1–20 source requests; default 20. One request per board, without automatic retries.
• maxSeconds: 1–120 seconds of processing; default 90. A pending socket read can take up to 12 additional seconds.
• previousSnapshot: up to 20,000 fingerprint entries; optional.
• changesOnly: false by default.

Cloud defaults are 512 MB and a 180-second timeout. Response and transfer limits are 16 MB per response and 64 MB per run. Invalid, duplicate or inconsistent feeds fail that board before its records are delivered. Limits can produce partial output; REPORT explains the stop reason. Forced restarts are not guaranteed to deliver records exactly once.

Pricing

$2 per 1,000 delivered job records, plus $0.00005 per Actor start at the supported memory allocation. Platform usage is included in this event pricing. A 1,000-record run costs $2.00005 at these prices.

Unchanged jobs suppressed by changesOnly and source errors have no record charge. The start event still applies when a run returns no records. Each observation delivered on a later run is a new billable result, including repeated jobs when changesOnly is off.

Set Maximum cost per run to control your budget. The minimum selectable budget is $0.003; the configured default is $2.01. The Actor limits delivered records to the available event budget. Check the Pricing tab for the active rates before running.

Scope

Greenhouse public boards only. The Actor does not submit applications, collect applicant records, enrich personal contact details, infer job closures, or bypass blocked pages. Use source data in accordance with applicable terms and your rights to use it. No affiliation with Greenhouse or listed employers is claimed.