# Company Career Site Jobs — Greenhouse, Lever, Ashby, Workday (`modomodo/ats-jobs-scraper`) Actor

Collect job postings straight from company career sites through the public APIs of four applicant tracking systems, normalized into one schema.

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

## Pricing

$1.00 / 1,000 job postings

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

## Company Career Site Jobs — Greenhouse, Lever, Ashby, Workday

Collect job postings straight from company career sites. This Actor talks to the
public APIs of four applicant tracking systems and returns every posting in one
shape, so a list of companies on different systems still comes back as a single
clean dataset.

### What it does

- **Four systems, one schema.** Greenhouse, Lever, Ashby and Workday postings
  arrive with the same field names, so nothing downstream has to branch.
- **Paste a careers URL.** The system is detected from the link. You can also
  write it out as `greenhouse:airbnb`, `lever:gopuff` or `ashby:openai`.
- **Descriptions included.** Full text and original HTML for every posting,
  with HTML entities already decoded.
- **Every run is checked.** A quality report is written to the key-value store
  under `RUN_SUMMARY`: how many postings each company returned, how often each
  field was actually filled, duplicates, detail requests that were refused, and
  which companies failed and why. Gaps are reported rather than hidden — if a
  source stops returning descriptions partway through, the run says so instead
  of quietly handing you empty columns.
- **One bad company does not sink the run.** Failures are recorded per company
  and the rest still finish.
- **An empty result is an answer, not an error.** A company with no current
  openings, or filters that match nothing, finish successfully with a warning
  in `RUN_SUMMARY`. The run is only marked failed when every company failed or
  the output itself is malformed.

### Input

| Field | Type | Notes |
|---|---|---|
| `companies` | array of strings | One per line. A careers URL, or `system:company`. Workday needs `workday:tenant/dataCenter/site`, which a Workday careers URL already contains. |
| `includeDescription` | boolean | Default `true`. Turning it off makes Workday runs much faster, since that system needs one extra request per posting, and drops the description fields from every source. |
| `maxJobsPerCompany` | integer | `0` means no limit. |
| `titleKeywords` | array of strings | Keep only postings whose title contains one of these. |
| `locationKeywords` | array of strings | Keep only postings matching a location. |
| `remoteOnly` | boolean | Keep only postings marked remote. |

#### Example

```json
{
  "companies": [
    "greenhouse:airbnb",
    "lever:gopuff",
    "ashby:openai",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "includeDescription": true,
  "titleKeywords": ["engineer", "data"]
}
```

### Output

Every record has these fields. A value that the source does not provide is
`null` — never an empty string, so a gap is always visible.

| Field | Description |
|---|---|
| `source` | `greenhouse`, `lever`, `ashby` or `workday` |
| `companyId`, `companyName` | Board identifier and company name |
| `jobId` | Identifier within that system |
| `title` | Job title |
| `locationRaw`, `locations` | Location as written, and the split list |
| `remote` | `true`, `false`, or `null` when the source says nothing |
| `employmentType` | Full time, part time, contract, as the source words it |
| `department`, `team` | Where the source separates them |
| `compensation` | Where the source publishes it |
| `postedAt`, `updatedAt` | ISO 8601 |
| `url`, `applyUrl` | Posting page and application page |
| `descriptionText`, `descriptionHtml` | Full description |
| `scrapedAt` | ISO 8601 |

#### Sample record

```json
{
  "source": "ashby",
  "companyId": "linear",
  "companyName": "linear",
  "jobId": "d3bc1ced-3ce4-4086-a050-555055dbb1ff",
  "title": "Senior / Staff Fullstack Engineer",
  "locationRaw": "Europe",
  "locations": ["Europe"],
  "remote": true,
  "employmentType": "FullTime",
  "department": "Product",
  "team": "Engineering",
  "compensation": null,
  "postedAt": "2021-04-27T20:13:45.158Z",
  "updatedAt": null,
  "url": "https://jobs.ashbyhq.com/linear/d3bc1ced-3ce4-4086-a050-555055dbb1ff",
  "applyUrl": "https://jobs.ashbyhq.com/linear/d3bc1ced-3ce4-4086-a050-555055dbb1ff/application",
  "descriptionText": "At Linear, we're building the product development system...",
  "descriptionHtml": "<p>At Linear, we're building...</p>",
  "scrapedAt": "2026-09-22T09:14:02.511Z"
}
```

### Finding a company

- **Greenhouse** — `boards.greenhouse.io/<company>` or `job-boards.greenhouse.io/<company>`
- **Lever** — `jobs.lever.co/<company>`
- **Ashby** — `jobs.ashbyhq.com/<company>`
- **Workday** — `<tenant>.wd<n>.myworkdayjobs.com/<site>`

Paste any of those links and the Actor works out the rest. A company whose
careers page is not one of these four systems is reported in `RUN_SUMMARY`
rather than failing the run.

### Reading the quality report

`RUN_SUMMARY` in the key-value store holds the numbers behind the run:

| Field | Meaning |
|---|---|
| `jobsCollected` / `rawCollected` | Rows returned, and rows found before filters |
| `bySource` | How many rows each system contributed |
| `fillRate` / `fillRateBySource` | How often each field was actually filled, overall and per system |
| `detailFailures` | Detail requests a system refused, counted rather than guessed |
| `detailStopped` | Set when a system refused so persistently that the Actor stopped asking |
| `warnings` | Empty results, description gaps, refused detail requests |
| `errors` | Companies that failed, with the reason |
| `verdict` | `ok: false` only when every company failed or the output is malformed |

Workday publishes descriptions through a separate request per posting and
rate-limits them. The Actor retries and slows down, and if the system keeps
refusing it stops asking rather than billing you for empty columns — that shows
up in `detailStopped`.

### Notes

- Only postings a company publishes on its own careers page are collected.
  Ashby postings marked unlisted are skipped.
- No personal data is collected: these are job advertisements written by
  employers.
- These are public endpoints and normally need no proxy.

# Actor input Schema

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

One company per line. Paste a careers URL (the system is detected automatically), or write it explicitly as greenhouse:airbnb, lever:gopuff, ashby:openai, workday:nvidia/wd5/NVIDIAExternalCareerSite

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

Fetch the description text for every posting. Greenhouse, Lever and Ashby include it at no extra cost. Workday needs one extra request per posting, so turn this off for large Workday runs.

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

0 means no limit. Workday needs one extra request per posting, so a company with thousands of openings can take minutes and cost accordingly — keep a limit while testing.

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

Keep only postings whose title contains one of these (case-insensitive). Leave empty to keep all.

## `locationKeywords` (type: `array`):

Keep only postings whose location contains one of these (case-insensitive). Leave empty to keep all.

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

Keep only postings marked remote.

## `proxyConfiguration` (type: `object`):

Optional. These are public APIs and normally work without a proxy.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:airbnb",
    "lever:gopuff",
    "ashby:openai",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "includeDescription": true,
  "maxJobsPerCompany": 25,
  "remoteOnly": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One item per posting, in the same shape for all four systems.

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

How many postings each company returned, how often each field was actually filled per source, detail requests that were refused, warnings, and the pass or fail verdict for the run.

# 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": [
        "greenhouse:airbnb",
        "lever:gopuff",
        "ashby:openai",
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
    ],
    "maxJobsPerCompany": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("modomodo/ats-jobs-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": [
        "greenhouse:airbnb",
        "lever:gopuff",
        "ashby:openai",
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
    ],
    "maxJobsPerCompany": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("modomodo/ats-jobs-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": [
    "greenhouse:airbnb",
    "lever:gopuff",
    "ashby:openai",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "maxJobsPerCompany": 25
}' |
apify call modomodo/ats-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,modomodo/ats-jobs-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/KNq3xtGiJYpN9GOh5/builds/HzobDLDEeaP7gw1lm/openapi.json