# ATS Job Scraper — Greenhouse, Lever, Ashby, Workday (`atsdata/ats-job-scraper`) Actor

Give it company domains. It finds their ATS automatically and returns every open job in one normalized schema, with parsed salary. No cookies, no proxies, no board tokens to hunt down.

- **URL**: https://apify.com/atsdata/ats-job-scraper.md
- **Developed by:** [ATS Data](https://apify.com/atsdata) (community)
- **Categories:** Jobs, Lead generation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.00005 / actor start

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?

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 Job Scraper — Greenhouse, Lever, Ashby & Workday

Give it a **company domain**. Get back **every open job**, in one clean schema, with **parsed salary**.

No board tokens to hunt down. No cookies. No proxies. No login.

```
Input:   ["stripe.com", "ramp.com", "palantir.com"]
Output:  1,022 jobs — normalized, deduplicated, salary parsed
```

***

### What you actually get

Real rows from a single run across **four different ATS platforms** — one schema, no per-platform handling on your side:

| Job title | Company | Location | Level | Salary | ATS |
|---|---|---|---|---|---|
| Security Engineer, Cloud | ramp | New York, NY (HQ) *+3* | mid | $211,400–290,600/yr | `ashby` |
| Backend Software Engineer - Application Development | palantir | Palo Alto, CA | mid | $135,000–200,000/yr | `lever` |
| Account Executive, AI Startups (Hunter) | stripe | San Francisco *+1* | mid | `null` | `greenhouse` |
| Software Engineer, Linux Graphics | nvidia | US, CA, Santa Clara | mid | `null` | `workday` |

Salary reads `null` when the company doesn't publish one — it is never guessed or filled in.

#### Straight to a spreadsheet

Export as CSV and nested fields flatten with `/` — no post-processing:

```csv
title,companySlug,department,locations/0,workplaceType,seniority,salary/min,salary/max,salary/currency,postedAt,source
"Security Engineer, Cloud",ramp,Engineering,"New York, NY (HQ)",hybrid,mid,211400,290600,USD,2026-04-07,ashby
Backend Software Engineer - Application Development,palantir,Dev,"Palo Alto, CA",hybrid,mid,135000,200000,USD,2026-06-18,lever
"Account Executive, AI Startups (Hunter)",stripe,Startups - Account Executives (NA),San Francisco,,mid,,,,2026-08-19,greenhouse
"Software Engineer, Linux Graphics",nvidia,,"US, CA, Santa Clara",,mid,,,,2026-08-25,workday
```

Full records also carry `jobId`, `employmentType`, `applyUrl`, `descriptionText`, `descriptionHtml`,
`contentHash` and `scrapedAt`. Turn off `includeDescription` for a smaller, faster payload.

***

### Why this one

Most ATS scrapers make **you** do the hard part: find the company's board slug, figure out which ATS they use, then run a different scraper for each one and reconcile four different output shapes.

This Actor does all of that for you.

| | Typical ATS scraper | This Actor |
|---|---|---|
| Input | Board slug you must find yourself | **Company domain** |
| ATS coverage | One per Actor | **Greenhouse + Lever + Ashby + Workday** |
| Output shape | Different per ATS | **One schema for all** |
| Salary | Raw text, if any | **Parsed** `{min, max, currency, period}` |
| Change tracking | — | **Built in** (new / updated / closed) |
| Proxies | Often required | **None** |

***

### Change tracking — turn it into a hiring monitor

Set **`onlyNewJobs: true`**, schedule the Actor daily, and each run returns **only what changed**:

- `added` — jobs posted since the last run
- `updated` — title, salary, location or description changed
- `removed` — job closed or pulled (a signal in itself)

The first run stores a baseline. Every run after that is a diff.

**Use it for:**

- **Sales intelligence** — a company opening 12 engineering roles is a buying signal
- **Recruiting** — know about a role the hour it goes live
- **Market research** — track hiring velocity and comp by company, team and level
- **Job boards** — keep a live index without re-ingesting everything

***

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `companies` | array | — | Domains (`stripe.com`) or board URLs (`jobs.lever.co/palantir`) |
| `onlyNewJobs` | boolean | `false` | Return only added/changed jobs vs. the previous run |
| `trackingKey` | string | `default` | Track multiple company lists independently |
| `includeRemovedJobs` | boolean | `false` | Also emit jobs that disappeared |
| `includeDescription` | boolean | `true` | Include full description text and HTML |
| `maxJobsPerCompany` | integer | `0` | Cap per company (`0` = no limit) |
| `workdayFetchDetails` | boolean | `true` | Workday needs one extra request per job for descriptions |

Board URLs are accepted directly, so you can skip resolution when you already know the board:

```json
{
  "companies": [
    "stripe.com",
    "jobs.lever.co/palantir",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ]
}
```

***

### Output

Every record has the same shape regardless of which ATS it came from:

```json
{
  "jobId": "ashby:ramp:34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "source": "ashby",
  "companySlug": "ramp",
  "companyDomain": "ramp.com",
  "title": "Security Engineer, Cloud",
  "department": "Engineering",
  "team": "Backend",
  "locations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "workplaceType": "hybrid",
  "employmentType": "FullTime",
  "seniority": "mid",
  "salary": { "min": 211400, "max": 290600, "currency": "USD", "period": "year" },
  "descriptionText": "ABOUT RAMP\n\nRamp is building the smart infrastructure for finance teams…",
  "descriptionHtml": "…",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-…/application",
  "postedAt": "2026-04-07T17:12:35.753Z",
  "scrapedAt": "2026-08-24T18:03:28.104Z",
  "contentHash": "593a0ec77ef05d3c",
  "changeType": "added"
}
```

`contentHash` changes only when the job's meaningful content changes — use it for your own diffing.

`seniority` is derived from the title: `intern`, `junior`, `mid`, `senior`, `principal`, `manager`, `director`, `executive`.

***

### Salary parsing

Ashby exposes structured compensation, so those values are exact. For Greenhouse, Lever and Workday the range is parsed out of the posting text, handling the formats companies actually use:

```
$173,000.00 - $259,600.00/yr     →  173000–259600 USD/year
€55k–€70k per year               →  55000–70000 EUR/year
USD 90000 to 120000 annually     →  90000–120000 USD/year
The salary range is $10,000/month →  10000 USD/month
```

Version numbers, headcounts and date ranges are **not** mistaken for salary.

Coverage measured against live boards:

| Board | Jobs | Postings stating salary | Parsed |
|---|---|---|---|
| Ashby / ramp | 137 | 137 | **137 (100%)** |
| Lever / palantir | 308 | 234 | **234 (100%)** |
| Greenhouse / databricks | 824 | 450 | **444 (99%)** |

Companies that don't publish salary return `salary: null`. Nothing is invented.

***

### Speed

No browser, no proxies — just the public JSON endpoints each ATS already serves.

| Board | Jobs | Time |
|---|---|---|
| Greenhouse / databricks | 824 | 0.5 s |
| Greenhouse / stripe | 577 | 0.7 s |
| Lever / palantir | 308 | 1.4 s |
| Ashby / ramp | 137 | 0.3 s |

Workday is slower by design: its list endpoint returns no descriptions, so each job needs one extra request.

Set `workdayFetchDetails: false` to skip that — much faster and cheaper, but descriptions come back empty and jobs open in several offices read `"2 Locations"` instead of naming them. With the default (`true`) you get the full description and the real location.

***

### Supported ATS

| ATS | Input accepted |
|---|---|
| **Greenhouse** | domain, `boards.greenhouse.io/<slug>`, `job-boards.greenhouse.io/<slug>` |
| **Lever** | domain, `jobs.lever.co/<slug>` |
| **Ashby** | domain, `jobs.ashbyhq.com/<slug>` |
| **Workday** | domain, `<tenant>.wd*.myworkdayjobs.com/<site>` |

More ATS platforms are being added. Need one in particular? Open an issue on the Actor and it gets prioritized.

***

### Notes

- Only **public** job board data is collected — the same pages any visitor can open. No accounts, no logins, no personal candidate data.
- If a company's careers page can't be matched to a supported ATS, that company is skipped with a warning and the rest of the run continues.
- A company can have more than one board. The one with the most open jobs is used as primary; the others are still reported.

# Actor input Schema

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

Company domains (stripe.com) or direct board URLs (jobs.lever.co/palantir, https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite). Domains are resolved to the right ATS automatically.

## `onlyNewJobs` (type: `boolean`):

Compare against the previous run and return only jobs that were added or changed. Turn this on and schedule the Actor daily to track hiring in near real time. The first run returns everything.

## `trackingKey` (type: `string`):

Name of the state used for change tracking. Use different keys to track different company lists independently.

## `includeRemovedJobs` (type: `boolean`):

Also emit records for jobs that disappeared since the previous run (a job being filled or pulled is itself a signal).

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

Include the full job description text and HTML. Turn off for smaller, faster output.

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

Safety cap per company. 0 means no limit.

## `workdayFetchDetails` (type: `boolean`):

Workday's list endpoint has no descriptions, so each job needs one extra request. Turn off to get titles and locations only, much faster.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "jobs.lever.co/palantir"
  ],
  "onlyNewJobs": false,
  "trackingKey": "default",
  "includeRemovedJobs": false,
  "includeDescription": true,
  "maxJobsPerCompany": 0,
  "workdayFetchDetails": true
}
```

# Actor output Schema

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

All job records from this run, one item per job.

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

Counts for this run — total found, written, and the added/updated/removed breakdown when change tracking is on.

# 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",
        "palantir.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("atsdata/ats-job-scraper").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",
        "palantir.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("atsdata/ats-job-scraper").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",
    "palantir.com"
  ]
}' |
apify call atsdata/ats-job-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/nQzJcWNAuKUef0NpM/builds/Ene0UpxjSPBlhMq05/openapi.json