# ATS Hiring Signals — cross-ATS jobs + new-role deltas (`tkmvictim/ats-hiring-signals`) Actor

Track hiring across company career sites (Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee). Get normalized job postings, only-new deltas with first-seen dates, and per-company hiring rollups (buying signals). Non-personal data.

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

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

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

## ATS Hiring Signals — cross-ATS jobs + new-role delta & company rollups

Track hiring across company career sites and sell the **derived signal**, not a raw wrapper.

**Why this and not a plain job scraper:** anyone can hit a single ATS's public JSON for free. The product is the layer on top — a normalized cross-ATS schema, **only-new deltas with `firstSeenAt` dates**, and **per-company hiring rollups** ("who just started hiring for what") that buyers (recruiters, B2B sales tracking hiring spikes as buying signals) cannot self-serve.

### Supported ATS (Tier-1, public JSON, no auth, non-personal)

Greenhouse · Lever · Ashby · SmartRecruiters · Recruitee.
(Workday / iCIMS are intentionally **out** — anti-bot heavy, would break the passive/self-healing model. Add as a separate isolated actor later.)

### Input

```json
{
  "companies": [
    { "ats": "greenhouse", "slug": "stripe" },
    { "ats": "ashby", "slug": "ramp" },
    { "ats": "lever", "slug": "matchgroup" }
  ],
  "mode": "full",
  "emitCompanyRollup": true,
  "filters": { "titleKeywords": [], "departments": [], "remoteOnly": false },
  "maxJobsPerCompany": 0
}
```

- **mode `full`** — every active job (+ closed). **mode `delta`** — only newly-opened / newly-closed roles (uses the stored per-company snapshot). Run on a daily **Schedule** in `delta` mode to generate recurring buying-signal consumption.

### Output (dataset)

- Job records: `{ jobId, company, companySlug, ats, title, department, team, location{raw,remote}, employmentType, applyUrl, sourceUrl, postedAt, firstSeenAt, lastSeenAt, status }` — `status` ∈ `new | active | closed`.
- Company rollups (`_type: "company_rollup"`): `{ company, ats, activeJobs, newJobs, closedJobs, newDepartments, newRoles[], isBaseline }`.

### Pricing (pay-per-event — configure in Console)

| Event | Suggested price | Role |
|---|---|---|
| `job-listed` | $0.002 / job | commodity full-mode records (acquisition) |
| `new-job-delta` | $0.01 / new role | the product — pre-computed only-new feed |
| `company-hiring-rollup` | $0.05 / company | highest-margin buying-signal intelligence |

Don't compete on $/1,000 raw jobs (incumbents win on volume). Charge for the signal.

### Legal / ToS

Non-personal job & firmographic data. **Sell derived data** (first-seen, velocity, rollups), not verbatim bulk redistribution — Greenhouse's terms restrict reselling raw bulk. Never extract recruiter names/emails from descriptions (keeps it out of PII/GDPR territory). Public endpoints only; no login/cookies.

### Self-healing notes

Tolerant key-based parsing per ATS; a company that 404s is skipped, not fatal. Baseline runs (no prior snapshot) mark everything `active`, never `new`, to avoid a false "all-new" explosion. State lives in the KV store keyed per company.

# Actor input Schema

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

List of { ats, slug, name? }. ats one of: greenhouse, lever, ashby, smartrecruiters, recruitee. slug = the company handle on that ATS.

## `mode` (type: `string`):

full = every active job (+closed). delta = only newly-opened and newly-closed roles (uses stored snapshot).

## `emitCompanyRollup` (type: `boolean`):

Per-company summary: active/new/closed counts, new departments, new roles.

## `filters` (type: `object`):

{ titleKeywords: \[], departments: \[], remoteOnly: false }

## `maxJobsPerCompany` (type: `integer`):

Cap the number of jobs processed per company. 0 = no cap.

## Actor input object example

```json
{
  "companies": [
    {
      "ats": "greenhouse",
      "slug": "stripe"
    },
    {
      "ats": "ashby",
      "slug": "ramp"
    },
    {
      "ats": "lever",
      "slug": "matchgroup"
    }
  ],
  "mode": "full",
  "emitCompanyRollup": true,
  "filters": {},
  "maxJobsPerCompany": 0
}
```

# 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": [
        {
            "ats": "greenhouse",
            "slug": "stripe"
        },
        {
            "ats": "ashby",
            "slug": "ramp"
        },
        {
            "ats": "lever",
            "slug": "matchgroup"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tkmvictim/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 = { "companies": [
        {
            "ats": "greenhouse",
            "slug": "stripe",
        },
        {
            "ats": "ashby",
            "slug": "ramp",
        },
        {
            "ats": "lever",
            "slug": "matchgroup",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("tkmvictim/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 '{
  "companies": [
    {
      "ats": "greenhouse",
      "slug": "stripe"
    },
    {
      "ats": "ashby",
      "slug": "ramp"
    },
    {
      "ats": "lever",
      "slug": "matchgroup"
    }
  ]
}' |
apify call tkmvictim/ats-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tkmvictim/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/IIfEbwhygcHKtoIiB/builds/IvMX3WX8fqYAvK20y/openapi.json