# Greenhouse, Lever & Ashby Jobs + Hiring Signals | $1/1K (`hiringsignals/ats-hiring-signal-monitor`) Actor

Get every open job from the Greenhouse, Lever, Ashby, Workable and Recruitee career pages of your company list, or only the jobs that are new or closed since your last run. Paste domains, get clean job rows with pay ranges. Built for sales prospecting and competitor tracking. No login.

- **URL**: https://apify.com/hiringsignals/ats-hiring-signal-monitor.md
- **Developed by:** [Hiring Signals](https://apify.com/hiringsignals) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 86.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 job returneds

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

## Greenhouse, Lever & Ashby Jobs + Hiring Signals

Paste a list of companies (domains are fine). Get every open job from their career pages on Greenhouse, Lever, Ashby, Workable and Recruitee, or only the jobs that are new or closed since your last run.

I built it for sales teams who treat hiring as a buying signal. Recruiters and investors use it the same way. It costs $1 per 1,000 jobs, with no login and no LinkedIn.

### What you get

One row per job. This is a real row from a run on `ramp.com`:

```json
{
  "company": "Ramp",
  "title": "Security Engineer, Cloud",
  "changeType": "new",
  "function": "engineering",
  "seniority": "mid",
  "department": "Engineering",
  "team": "Backend",
  "locations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "workplaceType": "hybrid",
  "employmentType": "Full-time",
  "compensation": { "min": 211400, "max": 290600, "currency": "USD", "interval": "year" },
  "postedAt": "2026-04-07T17:12:35.753Z",
  "firstSeenAt": "2026-10-03T17:28:25.361Z",
  "lastSeenAt": "2026-10-03T17:28:25.361Z",
  "url": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "ats": "ashby",
  "boardSlug": "ramp",
  "companyInput": "ramp.com"
}
```

`changeType` is `open`, `new` or `closed`. A closed row is a job that was on the board last run and is gone now. In snapshot mode every row is `open`; use "new" or "changes" mode to track what changed.

Each run also saves a `SUMMARY` record in the key-value store. For every company it lists open jobs, new jobs, closed jobs and a count by function. It also lists any company I couldn't find a board for, and says why.

### What people use it for

**Sales prospecting.** A company that just opened three sales roles has budget and a plan. Load your target accounts, set the mode to "New jobs since last run", filter to the functions you sell into, and schedule it weekly. You get a short list of accounts that are moving.

**Watching competitors.** New roles tell you where a competitor is going before the press release does. A wave of jobs in one city, or a first "Head of Partnerships", is hard to hide.

**Tracking a portfolio.** VCs and investors can watch hiring across every portfolio company in one run. Closed roles matter as much as new ones. A board that empties out is worth a phone call.

**Recruiting.** See which companies are hiring for the roles you place, and catch reqs the day they post.

### How to use it

1. Paste your companies, one per line. Any of these work:
   - a domain: `stripe.com`
   - a careers page or board URL: `https://jobs.lever.co/spotify`
   - an exact board: `greenhouse:stripe`, `lever:spotify`, `lever-eu:acme`, `ashby:ramp`, `workable:huggingface`, `recruitee:bunq`
2. Pick what to return:
   - **Snapshot**: every open job.
   - **New jobs since last run**: only jobs that weren't there before.
   - **New and closed jobs since last run**: both.
3. Add filters if you want them: job function, words in the title, department, location, remote only, posted in the last N days.
4. Schedule it. Daily or weekly is typical.

The first run of a watchlist in "new" or "changes" mode returns every open job, so you have a starting point. After that you only get the changes.

#### Tips

- **Name your watchlist.** If you set "Watchlist name", you can add or remove companies later without resetting what counts as new. Without a name, the company list itself is the watchlist, so editing the list starts fresh.
- **Exact boards are best.** For a domain, I read the company's careers page to find the board, and if that fails I guess the board name on each job board. Guesses are usually right but can be wrong for common names. If you know the board, `greenhouse:acme` never guesses. `SUMMARY` shows how each company was found (`input`, `careers-page` or `slug-guess`).
- **Filters don't change what counts as new.** The monitor remembers every job on the board, not just the ones that passed your filters. You can change filters between runs and you won't get fake "new" rows.
- **Max cost is respected.** If a run hits your max cost, it stops cleanly. Changes it couldn't return show up again on the next run instead of being lost.

### Input

| Field | What it does | Default |
|---|---|---|
| `companies` | Domains, careers or board URLs, or `ats:slug` entries | 3 example companies |
| `mode` | `snapshot`, `new` or `changes` | `snapshot` |
| `watchlistName` | Keeps run-to-run memory when the list changes | empty |
| `functions` | sales, marketing, support, data, design, product, engineering, finance, people, legal, ops, other | all |
| `titleInclude` / `titleExclude` | Words the title must or must not contain | none |
| `departments` | Words in the department or team name | none |
| `locations` | Words in any of the job's locations | none |
| `remoteOnly` | Only remote jobs | off |
| `postedWithinDays` | Only jobs posted in the last N days (0 = off) | 0 |
| `includeDescription` | Add the full description as plain text | off |
| `includeCompensation` | Add the pay range when one is listed | on |
| `maxJobsPerCompany` | Cap on rows per company per run | 500 |

### Pricing

You pay per event:

| Event | Price |
|---|---|
| Run start | $0.002 |
| Company checked (a board was found and read) | $0.002 |
| Job returned in snapshot mode, or on a first run | $0.001 |
| New or closed job returned in "new" or "changes" mode | $0.003 |

Jobs that didn't change cost nothing in "new" and "changes" mode, and companies with no board found cost nothing.

Example: 500 target accounts checked weekly, with about 200 changes a week, comes to about $1.60 a week, or around $7 a month.

### Where the data comes from

Every request goes to a job board's public API, the same feed a company's careers page reads from. Greenhouse, Lever and Ashby document these APIs for anyone building job listings. I follow each host's robots.txt, keep requests polite (no more than 5 at once per host, with backoff when a host asks me to slow down), and read nothing behind a login.

The output is job postings only. I leave out recruiter and hiring-manager names, even when a board includes them.

### Function and seniority tags

`function` and `seniority` come from simple rules on the job title, with the department as a fallback. They are right most of the time and wrong some of the time. If a tag looks off, the title and department are right there in the row.

### Not supported yet

- **Workday** and **iCIMS** boards. Workday is next.
- **SmartRecruiters.** Its API host's robots.txt blocks every crawler except LinkedIn's, so I leave it alone.
- Companies that host jobs on their own site with no ATS behind it.

### Questions and problems

Open an issue on the Issues tab. I read every one and usually answer within two days. If a company you care about isn't found, include it and I'll take a look.

# Actor input Schema

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

One per line. A domain (stripe.com), a careers or job board URL (https://jobs.lever.co/acme), or an exact board as ats:slug (greenhouse:stripe, lever:acme, lever-eu:acme, ashby:ramp, workable:acme, recruitee:acme). Exact boards are fastest and never guess wrong.

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

snapshot: every open job. new: only jobs that weren't there last run. changes: new jobs plus jobs that closed since last run. The first run of a watchlist in new or changes mode returns every open job as the starting point.

## `watchlistName` (type: `string`):

Optional. Runs with the same name share memory, so you can add or remove companies without resetting what counts as new. Leave empty and the company list itself is the watchlist.

## `functions` (type: `array`):

Only return jobs tagged with these functions. Leave empty for all.

## `titleInclude` (type: `array`):

Keep a job if its title contains any of these words (not case sensitive). Example: account executive, RevOps.

## `titleExclude` (type: `array`):

Drop a job if its title contains any of these words. Example: intern.

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

Keep a job if its department or team contains any of these words, as the company names them.

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

Keep a job if any of its locations contains one of these words. Example: London, Germany, Remote.

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

Only jobs marked remote, or with Remote in the location.

## `postedWithinDays` (type: `integer`):

Only jobs posted in the last N days. 0 turns this off. Closed jobs are always returned in changes mode.

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

Add the full description as plain text. Makes the output much bigger.

## `includeCompensation` (type: `boolean`):

Add the pay range when the job board lists one or the description states one.

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

Cap on rows returned per company in one run, to keep costs predictable.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "ramp.com",
    "huggingface.co"
  ],
  "mode": "snapshot",
  "functions": [],
  "titleInclude": [],
  "titleExclude": [],
  "departments": [],
  "locations": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescription": false,
  "includeCompensation": true,
  "maxJobsPerCompany": 500
}
```

# Actor output Schema

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

Open, new or closed jobs, one row each.

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

Open, new and closed counts per company, and any company whose job board wasn't found.

# 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": [
        "stripe.com",
        "ramp.com",
        "huggingface.co"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hiringsignals/ats-hiring-signal-monitor").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": [
        "stripe.com",
        "ramp.com",
        "huggingface.co",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("hiringsignals/ats-hiring-signal-monitor").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": [
    "stripe.com",
    "ramp.com",
    "huggingface.co"
  ]
}' |
apify call hiringsignals/ats-hiring-signal-monitor --silent --output-dataset

```

## MCP server setup

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

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/S9PyWh8YeHBnjSCiH/builds/X248vyHkqewTdLi7e/openapi.json