# ATS Jobs Scraper (Greenhouse, Lever, Ashby, Workday) (`datahamster/ats-jobs`) Actor

Jobs from company career boards on Greenhouse, Lever, Ashby and Workday in one schema. Keyword/location filters, monitor mode for new or changed postings. Official public APIs, no login, pay per job.

- **URL**: https://apify.com/datahamster/ats-jobs.md
- **Developed by:** [Viktor Dubnytskiy](https://apify.com/datahamster) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 result items

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

## ATS Jobs Scraper — Greenhouse, Lever, Ashby, Workday

Pull every open job from the career boards of the companies you care about, across four applicant-tracking systems, into one flat schema. Built for recruiters, sales teams tracking hiring signals, job-board aggregators and researchers.

### What you get

One row per job: `sourceAts`, `company`, `id`, `title`, `locations[]`, `remote`, `department`, `employmentType`, `postedAt`, `updatedAt`, `description` (plain text), `applyUrl`, `url`, `scrapedAt`. The schema is identical for all four ATS, so datasets from different companies concatenate without remapping.

### Input

- `boards`: career-board URLs or `ats:slug` pairs. Examples: `https://boards.greenhouse.io/stripe`, `lever:zoox`, `https://jobs.ashbyhq.com/notion`, `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`.
- `keyword` (optional): substring match on title, department or description.
- `location` (optional): substring match on any listed location.
- `maxItems`: stop after this many jobs. You are charged only for jobs actually pushed.
- `mode`: `scrape` (default) or `monitor` — on a saved Task run on a schedule, monitor returns only jobs that are new or changed since the previous run (`changeType`, `changedFields`, `previous`), and can POST a summary to `webhookUrl` or a Telegram chat.

### Pricing

| Event | Price |
|---|---|
| result | $0.0005 per job ($0.50 per 1,000) |
| monitor-check | $0.0015 per monitor run |
| change | $0.0005 per new or changed job |

Charged only for validated, deduplicated rows. A run that finds nothing costs nothing beyond platform usage, and the run's `RUN_SUMMARY` record says why (`no_matches`, `blocked`, `rate_limited`, `invalid_input`, `upstream_error`).

### Limits

- Workday boards need one extra request per job for the description; expect ~2–4 jobs/second per board.
- Lever and Greenhouse return the full board in one or a few requests; Ashby returns everything in one request.
- Boards that are private, require login, or use an unsupported ATS are skipped and counted in the run summary.
- Salary is returned only where the ATS exposes it in the public feed (Ashby `compensation`, Lever `salaryRange` are included under `raw` when present).

### Changelog

- 0.1: initial release — Greenhouse, Lever, Ashby, Workday; keyword/location filters; monitor mode.

# Actor input Schema

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

Career board URLs or ats:slug (greenhouse:stripe, lever:zoox, ashby:notion, https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite)

## `keyword` (type: `string`):

Substring match on title, department, description

## `location` (type: `string`):

Substring match on any listed location

## `maxItems` (type: `integer`):

Stop after this many results (you are charged only for pushed items)

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

Mode

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

Optional state key when not running as a saved task

## `webhookUrl` (type: `string`):

POST a change summary here in monitor mode

## `telegramBotToken` (type: `string`):

Telegram bot token

## `telegramChatId` (type: `string`):

Telegram chat id

## Actor input object example

```json
{
  "boards": [
    "greenhouse:stripe",
    "ashby:notion"
  ],
  "maxItems": 100,
  "mode": "scrape"
}
```

# Actor output Schema

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

All pushed rows (dataset, JSON)

## `resultsTable` (type: `string`):

Dataset in the Console viewer

## `runSummary` (type: `string`):

RUN\_SUMMARY record (pushed, skipped, emptyReason)

# 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 = {
    "boards": [
        "greenhouse:stripe",
        "ashby:notion"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datahamster/ats-jobs").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 = { "boards": [
        "greenhouse:stripe",
        "ashby:notion",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("datahamster/ats-jobs").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 '{
  "boards": [
    "greenhouse:stripe",
    "ashby:notion"
  ]
}' |
apify call datahamster/ats-jobs --silent --output-dataset

```

## MCP server setup

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

```

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/n7APHbOEiEDgpUftW/builds/EPmkXcVVRx6OzH4Wd/openapi.json