# ATS Hiring Signals — Jobs & Change Tracker (`huggable_chipmunk/ats-hiring-signals`) Actor

Extract public jobs from Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, Workable and Personio. Track new, changed, reopened and closed postings.

- **URL**: https://apify.com/huggable_chipmunk/ats-hiring-signals.md
- **Developed by:** [Marco Schwartz](https://apify.com/huggable_chipmunk) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## ATS Hiring Signals

Extract public job postings from **Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, Workable, and Personio**. Use one consistent dataset for recruitment research, sales intelligence, and scheduled hiring monitoring.

### Quick start

1. Paste company **ATS career-board URLs** into **Career board URLs**.
2. Optionally add title/department keywords, such as sales or marketing.
3. Run the Actor and export results to JSON, CSV, or Excel from the Dataset tab.
4. Save an Apify Task and schedule it daily to monitor changes. Enable **Only changes** to skip unchanged jobs.

Example input:

```json
{
  "careerUrls": ["https://jobs.lever.co/spotify", "https://jobs.ashbyhq.com/notion"],
  "keywords": ["sales", "marketing"],
  "includeDescription": false,
  "maxJobsPerBoard": 5000,
  "changesOnly": false,
  "monitorId": "sales-hiring-watch"
}
```

Advanced input accepts board identifiers instead of URLs:

```json
{
  "boards": [
    {"ats":"greenhouse","board":"stripe"},
    {"ats":"smartrecruiters","board":"BoschGroup"},
    {"ats":"recruitee","board":"bunq"},
    {"ats":"workable","board":"deeporigin"},
    {"ats":"personio","board":"personio"}
  ]
}
```

### Output

Each job record contains ATS, board, region, jobId, title, company, location, department, employmentType, workplaceType, publishedAt, jobUrl, applyUrl, description, changeType, and checkedAt. Fields not published by a provider are null. Descriptions are optional and may be unavailable from listing endpoints. Salary fields are not inferred.

Example:

```json
{
  "ats": "lever",
  "board": "spotify",
  "region": "global",
  "jobId": "example-id",
  "title": "Marketing Manager",
  "company": "spotify",
  "location": "London",
  "department": "Marketing",
  "employmentType": "Full-time",
  "workplaceType": "hybrid",
  "publishedAt": null,
  "jobUrl": "https://jobs.lever.co/spotify/example-id",
  "applyUrl": "https://jobs.lever.co/spotify/example-id/apply",
  "description": null,
  "changeType": "baseline",
  "checkedAt": "2026-10-05T08:00:00.000Z"
}
```

This example is illustrative. The Output tab offers Jobs and hiring changes, with overview and full-detail table views, plus a Run summary link. RUN_SUMMARY in the run's key-value store provides counts, errors, truncated boards, and spending-limit status. Output and dataset schemas are included in the Actor source for API and MCP consumers.

### Monitoring behavior

| changeType | Meaning |
| --- | --- |
| baseline | First observation; not a claim that the job was just posted |
| new | Newly observed since the previous successful check |
| changed | Published job fields changed |
| unchanged | Same published fields as before |
| possibly_closed | Missing from one complete, successful check |
| closed | Missing from two consecutive complete, successful checks |
| reopened | Previously closed posting reappeared |
| board_error | Feed could not be checked; diagnostic record, not a job |

Snapshots are isolated by the running user's account and monitor name. When no name is given, the Apify Task ID or board list supplies the identity. Keep one schedule per monitor; concurrent runs can race. A detected snapshot conflict skips the state update and is reported in RUN_SUMMARY. Reuse the same monitor name to retain history. State depends on Apify's retention policy; if it expires, the next run starts a new baseline.

Failures preserve prior snapshots. Truncated scans cannot close unseen jobs. If a spending limit prevents full output, that board's snapshot is not advanced. Switching the description output option does not alter comparison fingerprints. Keywords match titles and departments, case-insensitively; any keyword may match.

### Coverage and limitations

- Public feeds only: no accounts, cookies, proxies, or login required.
- Greenhouse and Lever support global and EU career-board URLs.
- SmartRecruiters pagination is followed until the requested cap.
- Company-owned career domains are not automatically resolved to an ATS. Paste the actual provider board URL or supply ats + board.
- Workday is not supported in this release.
- Workable uses its public widget feed; coverage is limited to jobs exposed there. Regional content and upstream access restrictions may differ.
- A confirmed disappearance is a feed observation, not an independent employer confirmation that a vacancy is filled.
- Upstream feeds can change. Unknown response schemas produce errors rather than silently empty boards.
- Limits: 50 boards per run, up to 10,000 jobs per board. A truncated scan is identified in RUN_SUMMARY.

### Pricing

Pay per emitted job record, including baseline, unchanged, new, changed, reopened, and closure observations. Filtering and Only changes reduce the number of chargeable records. Board-error diagnostics and RUN_SUMMARY have no Actor event charge.

| Apify plan | Per 1,000 job records |
| --- | ---: |
| Free | $3.00 |
| Bronze | $2.50 |
| Silver | $2.00 |
| Gold, Platinum, Diamond | $1.50 |

The Store pricing panel is authoritative. Ordinary Apify platform usage charges may also apply according to your plan. Configure Maximum total charge before running. The Actor stops job output at its event budget rather than continuing to generate unbilled records.

### Privacy and support

The Actor reads public employer job information. It stores job datasets and monitoring snapshots in Apify storage associated with the running user; it does not send them to an external analytics or AI service. It does not collect applicant data, submit applications, or contact employers.

Use the Actor's **Issues** tab for support. Include the provider, public board URL, and run ID; do not include account tokens or applicant information. Public Store publication is not proof of customer validation. This is an initial release tested on public boards, not a claim of production adoption.

### Local development

Use Node.js 22 or newer. Run npm ci, npm test, then npm start with input in Apify local storage. The Docker image installs pinned dependencies from package-lock.json. No Apify token is embedded in source files.

# Actor input Schema

## `careerUrls` (type: `array`):

Paste public Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, Workable, or Personio board URLs. Custom company career websites and Workday are not supported.

## `boards` (type: `array`):

Optional JSON objects with ats and board. Seven providers supported; this is an alternative to pasting URLs.

## `keywords` (type: `array`):

Leave empty to return every job. Matching is case-insensitive.

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

Include the full public job description in each output record.

## `maxJobsPerBoard` (type: `integer`):

Safety limit for records read from each board.

## `changesOnly` (type: `boolean`):

Hide unchanged jobs on subsequent runs. The first run still returns a baseline.

## `monitorId` (type: `string`):

Independent monitors use separate snapshots. By default tasks or board lists determine the name. Do not run the same monitor concurrently.

## Actor input object example

```json
{
  "careerUrls": [
    "https://jobs.lever.co/spotify"
  ],
  "boards": [],
  "keywords": [],
  "includeDescription": false,
  "maxJobsPerBoard": 5000,
  "changesOnly": false,
  "monitorId": ""
}
```

# Actor output Schema

## `jobs` (type: `string`):

Default dataset containing normalized job observations. changeType distinguishes baseline, new, changed, unchanged, possibly_closed, closed, reopened, and board_error diagnostics.

## `summary` (type: `string`):

JSON report with fetched and emitted counts, board errors, truncated scans, change counts, spending-limit status, and any detected snapshot conflict.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("huggable_chipmunk/ats-hiring-signals").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("huggable_chipmunk/ats-hiring-signals").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 '{}' |
apify call huggable_chipmunk/ats-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,huggable_chipmunk/ats-hiring-signals"
        }
    }
}
```

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/mReVhWJsKjSxImWyJ/builds/Nz5ARQDbf9G5K4jA3/openapi.json