SaaS Hiring Signal Monitor

Track public hiring signals from companies using Greenhouse.

Scope

This MVP uses only the public Greenhouse Job Board API. It does not log in, submit applications, use proxies, bypass controls, or accept arbitrary URLs.

Greenhouse documents the source at Job Board API. The documented read endpoint is:

GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true

Greenhouse states that only application submission requires Basic Auth. This Actor uses read-only list requests, so it needs no Greenhouse API key. An Apify account is required for an Apify run. Review Greenhouse's legal documents, employer terms, robots rules, rate limits, and applicable law before redistribution.

Input

{"boardTokens":["acme"],"maxJobs":1000}

boardTokens accepts 1 to 10 public Greenhouse board slugs. The slug is the path value in a public board URL such as boards.greenhouse.io/acme.

Output

The first observation emits new_posting rows. Later runs emit updated_posting rows when updated_at changes. Each row includes:

• source_url, the exact API request URL
• fetched_at, the observation timestamp
• published_at and updated_at, when supplied by Greenhouse
• job_url, title, location, board token, and job ID

The Actor deduplicates repeated job IDs in each response. It stores snapshots in an Apify Key-Value Store. Source failures produce source_error rows with warnings. The Actor caps boards at 10, jobs per board at 1,000, and response bodies at 4 MiB.

Local development

npm install
npm test
apify validate-schema

The test suite uses injected responses. It does not call Greenhouse or start paid jobs.