# ATS Hiring Signals: Greenhouse, Lever, Ashby Jobs (`dataforge_api/ats-hiring-signals-ppe`) Actor

Find companies hiring right now from public Greenhouse, Lever, Ashby and SmartRecruiters job boards: open roles by department and seniority, hiring velocity, new jobs since last run.

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

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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: Greenhouse, Lever, Ashby Jobs

Find out which companies are hiring right now and what they hire for. The Actor reads the public job-board APIs of **Greenhouse, Lever, Ashby and SmartRecruiters** (the same feeds that power the careers pages of those companies), normalises the roles into one schema and adds a per-company hiring summary. No login, no API key.

### Who it is for

1. **B2B sales teams**: a company opening many sales or engineering roles is a buying signal. Get the list and the apply links.
2. **Recruiting agencies**: see which employers have many open roles in a department or country.
3. **Market analysts**: track hiring velocity and seniority mix across a set of companies.
4. **Monitoring**: switch on `deltaMode` and run it on a schedule to receive only roles that appeared since the last run.

### Input

| Field | Meaning |
|---|---|
| `companies` | Board names or career-page URLs, e.g. `gitlab`, `lever:spotify`, `ashby:ramp`, `smartrecruiters:Freshworks`. A bare name is tried on all four systems. |
| `outputType` | `signals`, `jobs` or `signals_and_jobs`. |
| `deltaMode` | Return only roles not seen in a previous run. The first run per company saves a baseline and returns its summary only. |
| `titleKeywords`, `departments`, `locations`, `seniority`, `remoteOnly` | Filters. |
| `includeDescription`, `maxJobsPerCompany`, `maxResults` | Output size controls. |

### Output

Job record: `company_slug`, `ats`, `job_id`, `title`, `department`, `location`, `remote`, `employment_type`, `posted_at`, `apply_url`, `seniority` (guessed from the title), optional `description_text`.

Company signal: `open_roles`, `roles_posted_last_14_days`, `hiring_velocity_flag` (low, steady, surging), `remote_roles`, `roles_by_department`, `roles_by_country_or_region`, `roles_by_seniority`, `new_roles_since_last_run`, `careers_url`.

### Limits

- You supply the companies. The Actor does not discover which company uses which ATS (a bare name is probed on all four).
- SmartRecruiters lists no department, so department filters and the department breakdown do not apply to it.
- `remote` is what the job board says; a role can be remote-eligible and still show an office location.
- Only public job postings are read. No applicant data and no recruiter contact details are collected.

### Pricing

Pay per event: `ats-hiring-signals-job` $0.003 per job record and `ats-hiring-signals-company-signal` $0.02 per company summary. Boards that do not exist or have no open roles are not charged. In delta mode a repeated run without new roles returns no job records, so no job events are charged; the per-company summary is still returned and charged on every run. To pay only for new jobs, set `outputType` to `jobs`.

### Use cases

- **Sales timing:** companies that suddenly post many roles are growing; the velocity flag shows it.
- **Recruiting research:** open roles by department, seniority and location, with apply links.
- **Competitor watch:** switch on delta mode to see only new roles since the last run.

Published task examples on this Actor's page show ready-made inputs for each case.

### Related Actors

- [Company Contact Finder](https://apify.com/dataforge_api/company-contact-finder-ppe): public emails and phones from a website
- [Website Tech Stack Detector](https://apify.com/dataforge_api/website-tech-stack-ppe): what a company website runs on
- [New Company Registrations Feed](https://apify.com/dataforge_api/new-business-registrations-ppe): newly registered companies

# Actor input Schema

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

Job board names or career-page URLs. Examples: gitlab, greenhouse:gitlab, lever:spotify, ashby:ramp, smartrecruiters:Freshworks, https://job-boards.greenhouse.io/gitlab. A bare name is tried on all four systems.

## `outputType` (type: `string`):

signals gives one summary record per company, jobs gives one record per open role, signals_and_jobs gives both.

## `deltaMode` (type: `boolean`):

Remember job IDs between runs (in a named storage) and return only roles that were not seen before. The first run for a company saves a baseline and returns only its summary; jobs appear from the second run.

## `titleKeywords` (type: `array`):

Optional. Keep roles whose title contains one of these words, e.g. sales, engineer, data.

## `departments` (type: `array`):

Optional. Keep roles whose department contains one of these words, e.g. engineering, sales.

## `locations` (type: `array`):

Optional. Keep roles whose location contains one of these words, e.g. london, germany, remote.

## `seniority` (type: `array`):

Optional. intern, junior, mid, senior, lead, principal, manager, director or executive. Level is guessed from the job title.

## `remoteOnly` (type: `boolean`):

Keep only roles marked remote by the job board.

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

Add the first 4000 characters of the job description as plain text (not available for SmartRecruiters).

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

Maximum number of job records returned for each company.

## `maxResults` (type: `integer`):

Maximum number of records (summaries plus jobs) saved in the whole run.

## Actor input object example

```json
{
  "companies": [
    "gitlab",
    "lever:spotify",
    "ashby:ramp"
  ],
  "outputType": "signals_and_jobs",
  "deltaMode": false,
  "titleKeywords": [],
  "departments": [],
  "locations": [],
  "seniority": [],
  "remoteOnly": false,
  "includeDescription": false,
  "maxJobsPerCompany": 200,
  "maxResults": 500
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("dataforge_api/ats-hiring-signals-ppe").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("dataforge_api/ats-hiring-signals-ppe").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 dataforge_api/ats-hiring-signals-ppe --silent --output-dataset

```

## MCP server setup

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

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/py3nf0N0yfGSSEYlT/builds/7dlRBbwanRhqi9mSY/openapi.json
