# Company Hiring Signals — Greenhouse & Lever (`exceptional_nugget/company-hiring-signal-tracker`) Actor

Track public Greenhouse and Lever job boards. Filter roles and locations, deduplicate postings, and compare new, changed and missing jobs across complete checks.

- **URL**: https://apify.com/exceptional\_nugget/company-hiring-signal-tracker.md
- **Developed by:** [LibriHouse](https://apify.com/exceptional_nugget) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 source checks

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Company Hiring Signals — Greenhouse & Lever

For recruiting and sales teams watching hiring activity at selected companies.

Track public Greenhouse and Lever job boards. Filter roles and locations, deduplicate postings, and compare new, changed and missing jobs across complete checks.

### What it does

Reads public Greenhouse job boards and paginated Lever postings. Records job ID, title, location and URL. Complete boards support added, updated and missing-job comparisons.

### Quick start

Paste the example below into Input, run the Actor, then open **REPORT** for a readable HTML report or **SUMMARY** for run coverage and history status. Dataset output has one row per supplied companies entry, with nested records and changes. Export JSON for full nested detail; CSV is best for summary fields.

```json
{
  "companies": [
    {
      "id": "greenhouse",
      "provider": "greenhouse",
      "board": "greenhouse",
      "name": "Greenhouse"
    }
  ]
}
```

### Inputs

Each companies object requires provider (greenhouse or lever) and board token. Optional id, name and region (us or eu; Lever only). roleKeywords and locationKeywords are optional case-insensitive literal OR filters; both groups must match. maxPages defaults to 3 (1–10); maxJobs to 500 (1–1000).

Supply 1–10 source objects. URLs must be public HTTP(S) on standard ports without credentials. `timeoutSecs` is 2–30 per request (default 15), `maxRedirects` 0–5 (default 3), and `delayMillis` 100–5000 between requests (default 250). Redirect destinations and DNS answers are validated; private and reserved network addresses are blocked. Response bodies are capped at 4 MB.

### Results and interpretation

`status` is observed, baseline, unchanged, changed or unknown. `sourceComplete` distinguishes complete coverage from partial/failed evidence. `records` contains observations; `facts` provides summary metrics; `issues` and the report explain limitations. `changeCounts` gives full counts; `changes` includes at most 100 detailed changes per input, with `changesTruncated` when capped. The HTML report previews 20 changes and 10 records. `SUMMARY.complete` means all inputs were attempted, while `coverageComplete` means all sources were reliable.

### Repeat runs and history

`monitor` defaults to true. Run the same watchlist with the same `monitorKey` to compare against the last reliable observation. The first run establishes a baseline and reports no invented changes. Change the key to start a new baseline. Changing source definitions or filter settings creates a separate scope. Keep stable IDs and source order.

History is stored in an Actor-owned named key-value store in your account, under limited permissions. Complete funded runs persist immutable snapshots; failed sources retain their prior records. Overlapping runs use start-ordered snapshots so a late older run cannot roll history back. Each run pins its baseline across restarts. Prefer schedules that do not overlap to avoid duplicate alerts from concurrent comparisons.

The most recent 20 snapshots are retained, with at most 2000 historical record IDs per source for rolling feeds and a 7 MB snapshot cap. Older retained IDs can appear new after eviction. `SUMMARY.history` says whether history was saved; split large watchlists if it reports a size limit. Partial budget runs do not advance history. `monitor: false` performs an observation without history.

### Pricing

**$30 per 1000 completed source checks** ($0.03 per `board-checked` event), plus Apify platform usage and the listed Actor-start event. A completed check can return unknown or problem evidence; it still incurs the custom check event. Transport/security exceptions with an `error` have no custom check charge. The Actor-start event is $0.00005 per GB of allocated memory, minimum one event. Use the run spending limit to bound charges; the report identifies partial budget runs. The Apify pricing tab is authoritative.

### Coverage limits

Public postings only, no applicant data or applications. Greenhouse total must match the returned array. Lever needs a short final page to prove exhaustion. Reaching a page or job cap suppresses comparison. Missing means absent from the configured board, not proof a hire occurred.

HTTP requests only. No CAPTCHA bypass, credentials, proxy subscription, external AI key, notifications or outbound messages are included. Use Apify schedules and your own integrations to consume changes. Reports show source evidence, not guaranteed business outcomes.

### Troubleshooting and support

For unknown results, inspect `issues` and the source response before changing your workflow. Increase pagination limits only when needed. Retry rate limits later with a longer delay. Use a new monitor key when intentionally redefining a watchlist. Open an issue from this Actor's Issues tab with the run ID, expected behavior and a public reproducible input; omit tokens and personal data.

### Local development

Node.js 22+. Run `npm ci`, `npm test`, `npm run check`, then `npm start` with an Apify INPUT record. Tests cover source fixtures, incomplete coverage, history, HTTP safety, report escaping and charging boundaries. Cloud release evidence is recorded separately in RELEASE.md in the local project.

# Actor input Schema

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

Each companies object requires provider (greenhouse or lever) and board token. Optional id, name and region (us or eu; Lever only). roleKeywords and locationKeywords are optional case-insensitive literal OR filters; both groups must match. maxPages defaults to 3 (1–10); maxJobs to 500 (1–1000).

## `monitor` (type: `boolean`):

Create/read an Actor-owned named history store. Disable for a stateless observation.

## `monitorKey` (type: `string`):

Use a distinct label for independent monitoring histories. Changes to source identities or extraction filters create a separate history.

## `timeoutSecs` (type: `integer`):

Deadline including DNS, in seconds.

## `maxRedirects` (type: `integer`):

Maximum redirects followed per request.

## `delayMillis` (type: `integer`):

Minimum delay between consecutive requests in the run.

## `roleKeywords` (type: `array`):

OR match job titles, case-insensitive.

## `locationKeywords` (type: `array`):

OR match locations, case-insensitive.

## `maxPages` (type: `integer`):

100 jobs per Lever page; cap means incomplete coverage.

## `maxJobs` (type: `integer`):

Source record cap; exceeding it suppresses change comparison.

## Actor input object example

```json
{
  "companies": [
    {
      "id": "greenhouse",
      "provider": "greenhouse",
      "board": "greenhouse",
      "name": "Greenhouse"
    }
  ],
  "monitor": true,
  "monitorKey": "default",
  "timeoutSecs": 15,
  "maxRedirects": 3,
  "delayMillis": 250,
  "roleKeywords": [],
  "locationKeywords": [],
  "maxPages": 3,
  "maxJobs": 500
}
```

# Actor output Schema

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

No description

## `report` (type: `string`):

No description

## `summary` (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": [
        {
            "id": "greenhouse",
            "provider": "greenhouse",
            "board": "greenhouse",
            "name": "Greenhouse"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("exceptional_nugget/company-hiring-signal-tracker").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": [{
            "id": "greenhouse",
            "provider": "greenhouse",
            "board": "greenhouse",
            "name": "Greenhouse",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("exceptional_nugget/company-hiring-signal-tracker").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": [
    {
      "id": "greenhouse",
      "provider": "greenhouse",
      "board": "greenhouse",
      "name": "Greenhouse"
    }
  ]
}' |
apify call exceptional_nugget/company-hiring-signal-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,exceptional_nugget/company-hiring-signal-tracker"
        }
    }
}
```

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/EPXqSzvTxrZbSEkZs/builds/90hZ02kDtjJcjMRcM/openapi.json