# ATS Jobs Scraper - Workday, Greenhouse, Lever & Ashby API (`appdata-labs/ats-jobs`) Actor

Get every open job from any company careers page running on Workday, Greenhouse, Lever or Ashby. Pass a company name or domain and the Actor works out which applicant tracking system they use, then returns all four vendors in one identical schema with remote, department and date filters.

- **URL**: https://apify.com/appdata-labs/ats-jobs.md
- **Developed by:** [Kobkoon Janngam](https://apify.com/appdata-labs) (community)
- **Categories:** Agents, MCP servers, Jobs
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 job scrapeds

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 Jobs Scraper — Greenhouse, Lever & Ashby from a domain alone

**Give it `stripe.com` and get every open job.** This Actor works out which applicant tracking system a company runs — Greenhouse, Lever or Ashby — and returns their whole careers page in one schema, whichever vendor it came from.

**Quick start:** press **Start** with no configuration at all. It ships with three companies, one on each provider, and returns their open roles immediately. Then paste in the companies you care about.

### Sample output

| company | title | location | department | employmentType | isRemote | publishedAt | provider |
|---|---|---|---|---|---|---|---|
| Stripe | Account Executive, AI Sales | San Francisco, CA | Enterprise Sales | | | 2026-02-03 | greenhouse |
| Spotify | Android Engineer – Experience | London | Engineering | Permanent | false | 2026-06-23 | lever |
| Ramp | Security Engineer, Cloud | New York, NY | Engineering | FullTime | true | 2026-04-07 | ashby |

Every row also carries `jobId`, `url`, `applyUrl`, `boardSlug`, `team`, `workplaceType`, `additionalLocations`, `compensation`, `updatedAt`, `descriptionPreview`, `descriptionTruncated` and `descriptionChars`.

### Why this one

**You do not need the board slug.** Every other ATS scraper wants `boards-api.greenhouse.io/v1/boards/**stripe**` — a token you have to go and find. Buyers do not have that. They have a company domain or a careers link. This Actor takes either, derives the slug, and asks each provider in turn until one recognises the company. Three cheap JSON requests, and an answer rather than a guess.

**One schema across three vendors.** The providers disagree about almost everything: a job's title is `title` on two and `text` on the third; a posting date is an ISO string here and epoch milliseconds there; a location is a nested object, a category, or a bare string. Remote is a boolean on Ashby, a workplace type on Lever, and nothing at all on Greenhouse. All of it is normalised, every field is always present, and `jobId` is a string everywhere so joins do not break.

**Descriptions you can actually read.** Greenhouse returns HTML wrapped in escaped entities. It arrives here as plain text, cut to an 800-character preview with the true length reported in `descriptionChars`, so a row stays small enough for an AI agent to reason over. Set `includeFullDescription` when you want the whole posting.

### What you can do with it

- **Track a competitor's hiring.** Schedule it with `postedAfter` set to yesterday and you get only the new openings — the cleanest public signal of where a company is investing.
- **Build a job board.** Point it at a list of portfolio or partner companies and you have a live, structured feed with direct apply links.
- **Source candidates by market.** `remoteOnly` plus `locationContains` narrows hundreds of roles to the ones in your patch.
- **Feed an AI agent.** Rows are under 2 KB, identically shaped across providers, and every one carries a direct apply URL.

### Input

| Field | Default | Notes |
|---|---|---|
| `companies` | 3 sample companies | A domain (`stripe.com`), a bare slug (`stripe`), or a board URL for any supported provider. Mix freely. |
| `providers` | all three | The order to try when an entry does not name a provider. Narrow it when you already know the ATS — it removes the failed lookups. |
| `titleContains` | empty | Case-insensitive partial match on the job title. |
| `locationContains` | empty | Matches secondary locations too. |
| `department` | empty | Matches department or team. |
| `remoteOnly` | `false` | Checks all three providers' different remote signals. |
| `postedAfter` | empty | `YYYY-MM-DD`. The most useful filter for a scheduled run. |
| `includeFullDescription` | `false` | Full posting text instead of a preview. Rows get much larger. |
| `maxJobsPerCompany` | `100` | Applied after filtering. Boards can be large — Stripe had 592 open roles. |

### How it works, and why it keeps working

This Actor reads the **official, public, keyless job-board APIs** that these companies' own careers pages are built on. No HTML parsing, no login, no proxy. A company can redesign its careers page and this Actor keeps returning the same fields.

### Limits worth knowing before you buy

It covers **Greenhouse, Lever and Ashby**. A company on Workday, SuccessFactors, Taleo or its own bespoke system cannot be read here, and the run tells you plainly which entries did not resolve rather than returning a quiet empty result.

The slug is derived from the domain, which is right far more often than not but not always — a company whose board is named differently from its domain needs its board URL or exact slug. `SUMMARY` records what each entry resolved to, so the first run tells you the right identifier for every later one.

### Pricing

Pay per job delivered, after filtering. A company with no matching openings charges you nothing.

### Disclaimer

This is an **unofficial** tool. It is not affiliated with, authorised by, endorsed by, or in
any way officially connected to Greenhouse Software, Lever, Ashby, or any company whose job
board it reads. "Greenhouse", "Lever" and "Ashby" are trademarks of their respective owners.

It reads only **public, unauthenticated** job-board API endpoints — the same ones these
companies' own careers pages call to render publicly advertised vacancies. It signs into
nothing, stores no credentials, and returns nothing behind a login or a paywall. No
candidate or applicant data is accessed; job postings are, by definition, published to be
read.

Providers can change or withdraw these endpoints at any time. When a board cannot be read,
this Actor says which company and why rather than handing you an empty result that looks
like an answer.

# Actor input Schema

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

Companies to read. Each entry can be a company domain (stripe.com), a bare slug (stripe), or a job-board URL for any supported provider. When the entry does not name a provider, each ATS is asked in turn until one recognises the company — three cheap requests, and an answer rather than a guess.

## `providers` (type: `array`):

The providers to check, in order, when a company entry does not name one. Workday is asked last because it is the only one with no single endpoint to try. Narrow this when you already know the ATS: it removes the failed lookups and makes the run faster.

## `titleContains` (type: `string`):

Keep only jobs whose title contains this text, case-insensitive. Leave empty for every open role. Example: "engineer" matches "Senior Engineer" and "Engineering Manager".

## `locationContains` (type: `string`):

Keep only jobs whose location contains this text, case-insensitive. Secondary locations count too, so "London" still matches a role listed in both Stockholm and London.

## `department` (type: `string`):

Keep only jobs in a matching department or team, case-insensitive and partial. Departments are the company’s own labels, so "engineering" is a safer filter than an exact team name.

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

Keep only remote roles. The three providers express this differently — Ashby has a flag, Lever has a workplace type, Greenhouse has only the location text — so all three signals are checked.

## `postedAfter` (type: `string`):

Keep only jobs published on or after this date, as YYYY-MM-DD. The single most useful filter for a scheduled run: set it to yesterday and you get just the new openings.

## `includeFullDescription` (type: `boolean`):

Off by default. Descriptions run to several thousand characters, which makes a row too big for an AI agent to read comfortably. Off, you get an 800-character preview plus the true length; on, you get the whole thing.

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

How many jobs to return for each company, after filtering. Boards can be large — Stripe had 592 open roles when this Actor was written — so this keeps a default run fast and cheap.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "https://jobs.lever.co/spotify",
    "ramp"
  ],
  "providers": [
    "greenhouse",
    "workday"
  ],
  "titleContains": "engineer",
  "locationContains": "London",
  "department": "engineering",
  "remoteOnly": false,
  "postedAfter": "2026-08-01",
  "includeFullDescription": false,
  "maxJobsPerCompany": 100
}
```

# Actor output Schema

## `rows` (type: `string`):

One row per open job in a single shape, whichever ATS it came from: title, company, location, department, employment type, remote flag, posting date, apply link and description.

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

Which companies resolved to which ATS, how many jobs each returned, and what the filters removed.

# 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",
        "spotify.com",
        "ramp.com"
    ],
    "providers": [
        "greenhouse",
        "lever",
        "ashby",
        "workday"
    ],
    "titleContains": "",
    "locationContains": "",
    "department": "",
    "remoteOnly": false,
    "postedAfter": "",
    "includeFullDescription": false,
    "maxJobsPerCompany": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("appdata-labs/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 = {
    "companies": [
        "stripe.com",
        "spotify.com",
        "ramp.com",
    ],
    "providers": [
        "greenhouse",
        "lever",
        "ashby",
        "workday",
    ],
    "titleContains": "",
    "locationContains": "",
    "department": "",
    "remoteOnly": False,
    "postedAfter": "",
    "includeFullDescription": False,
    "maxJobsPerCompany": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("appdata-labs/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 '{
  "companies": [
    "stripe.com",
    "spotify.com",
    "ramp.com"
  ],
  "providers": [
    "greenhouse",
    "lever",
    "ashby",
    "workday"
  ],
  "titleContains": "",
  "locationContains": "",
  "department": "",
  "remoteOnly": false,
  "postedAfter": "",
  "includeFullDescription": false,
  "maxJobsPerCompany": 50
}' |
apify call appdata-labs/ats-jobs --silent --output-dataset

```

## MCP server setup

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