# ATS Jobs Aggregator: Greenhouse, Lever, Ashby + 3 more (`cheering_unicorn/ats-jobs-aggregator`) Actor

Returns every open job from company career pages hosted on Greenhouse, Lever, Ashby, Recruitee, Personio or Workable as one clean, normalized dataset. Give it career-page URLs, get title, location, department, salary, dates and description per job. No browser, no login.

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

## Pricing

from $2.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

## ATS Jobs Aggregator

Pull every open job from company career pages hosted on **Greenhouse, Lever, Ashby, Recruitee, Personio or Workable** into one normalized dataset. Paste the career-page URLs, run, and get a clean table of jobs with title, location, department, employment type, salary (when the ATS exposes it), publish date and the full description.

It talks only to the public job-board APIs those ATS vendors publish for embedding career pages, so it is fast, cheap and does not break when a company restyles its careers site. No browser, no proxies, no login.

### What you get

One dataset row per job:

```json
{
  "ats": "greenhouse",
  "board": "stripe",
  "companyName": "Stripe",
  "jobId": "8172487",
  "title": "Abuse Investigator",
  "url": "https://stripe.com/jobs/search?gh_jid=8172487",
  "applyUrl": "https://stripe.com/jobs/search?gh_jid=8172487",
  "location": "Dublin",
  "locations": ["Dublin"],
  "remote": null,
  "workplaceType": null,
  "department": "8611 Security Analytics",
  "team": null,
  "employmentType": null,
  "publishedAt": "2026-09-03T13:30:34-04:00",
  "updatedAt": "2026-10-22T09:16:14-04:00",
  "salary": null,
  "descriptionText": "Who we are ...",
  "descriptionHtml": "<div>...</div>",
  "scrapedAt": "2026-10-22T19:04:11.512345+00:00"
}
```

Fields that an ATS does not expose are `null` rather than missing, so the columns are the same for every board.

### Input

| Field | Type | Notes |
|---|---|---|
| `boards` | array of strings | Career-page URLs or `ats:slug`. Recognised: `boards.greenhouse.io/<slug>`, `job-boards.greenhouse.io/<slug>`, `jobs.lever.co/<slug>`, `jobs.ashbyhq.com/<slug>`, `<slug>.recruitee.com`, `<slug>.jobs.personio.de`, `apply.workable.com/<slug>`. A bare slug such as `stripe` is probed against every ATS. |
| `keywords` | array of strings | Keep jobs whose title contains any keyword (case-insensitive). |
| `locationFilter` | string | Keep jobs whose location contains this text. |
| `remoteOnly` | boolean | Keep remote jobs only. |
| `postedAfter` | `YYYY-MM-DD` | Drop jobs published before this date. |
| `includeDescription` | boolean | Include HTML and plain-text description (default on). |
| `maxJobsPerBoard` | integer | Cap per board after filters (default 500, 0 = unlimited). |
| `maxJobs` | integer | Cap for the whole run (0 = unlimited). |

Example:

```json
{
  "boards": ["https://boards.greenhouse.io/stripe", "https://jobs.lever.co/palantir", "ashby:openai"],
  "keywords": ["engineer", "developer"],
  "remoteOnly": true,
  "maxJobs": 200
}
```

Boards that cannot be read (wrong slug, board switched off) are listed in the `ERRORS` record of the run's key-value store and the run continues with the other boards. The run fails only if every board failed.

### Pricing

Pay per event: **$0.002 per job** saved to the dataset ($2 per 1,000 jobs), plus Apify's standard Actor start fee. You pay only for jobs that match your filters and were written to the dataset. Boards that fail cost nothing. Set *Maximum total charge* on the run to cap spend; the Actor stops cleanly when it is reached.

Rough examples: three mid-size boards (~300 jobs) ≈ $0.60. A watch-list of 50 company boards checked daily with `postedAfter` set to yesterday usually costs a few cents per run.

### Use cases

- **Recruiting / sourcing**: watch competitors' career pages and get new roles the morning they appear (schedule the Actor, set `postedAfter`).
- **Job boards and aggregators**: feed a niche job board without maintaining six scrapers.
- **Sales intelligence**: hiring is a buying signal; filter titles by `keywords` such as `SDR`, `Salesforce`, `Kubernetes`.
- **Market research**: salary bands (Ashby, Lever, Recruitee publish them), remote-vs-onsite mix, department growth.
- **AI agents**: array input, flat output and PPE pricing make this a drop-in tool via the Apify MCP server.

### How it works

For each board the Actor calls the vendor's public job-board endpoint (`boards-api.greenhouse.io`, `api.lever.co/v0/postings`, `api.ashbyhq.com/posting-api`, `<slug>.recruitee.com/api/offers`, `<slug>.jobs.personio.de/xml`, `www.workable.com/api/accounts`). These are the same endpoints the vendors document for embedding a company's jobs on its own website. Requests are rate-limited to one per second per host with retries and back-off.

Not supported on purpose: SmartRecruiters (its API host disallows crawlers in `robots.txt`), Workday and custom career sites (they require a browser). Jobs are company data, not personal data; no applicant or recruiter information is collected.

### FAQ

**A company's career page is on its own domain, how do I find the slug?** Open a job and look at the apply link: `boards.greenhouse.io/<slug>/jobs/...`, `jobs.lever.co/<slug>/...`, `jobs.ashbyhq.com/<slug>/...`, `<slug>.recruitee.com`, `<slug>.jobs.personio.de`, `apply.workable.com/<slug>/`. Or just pass the bare slug and let the Actor probe.

**Why is `publishedAt` missing for some boards?** Workable and Greenhouse expose it; Personio exposes `createdAt`; Ashby, Lever and Recruitee expose it for most but not all jobs.

**Can I run it on a schedule?** Yes. Combine a daily schedule with `postedAfter` and a webhook or the Apify integrations (Slack, Google Sheets, Make, Zapier, n8n).

**Something looks wrong.** Open an issue on the Actor's Issues tab with the board URL; I usually answer within a day.

# Actor input Schema

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

Career-page URLs or `ats:slug` entries. Recognised hosts: boards.greenhouse.io/<slug>, job-boards.greenhouse.io/<slug>, jobs.lever.co/<slug>, jobs.ashbyhq.com/<slug>, <slug>.recruitee.com, <slug>.jobs.personio.de, apply.workable.com/<slug>. A bare slug (for example `stripe`) is probed against every supported ATS.

## `keywords` (type: `array`):

Keep only jobs whose title contains at least one of these words (case-insensitive). Leave empty to keep all jobs.

## `locationFilter` (type: `string`):

Keep only jobs whose location contains this text, for example `London` or `United States`.

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

Keep only jobs flagged as remote by the ATS or whose location mentions remote.

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

ISO date (for example `2026-10-01`). Jobs published before this date are dropped. Boards that do not expose a publish date are kept.

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

Include the job description as HTML and plain text. Turn off for a lighter dataset.

## `maxJobsPerBoard` (type: `integer`):

Stop after this many jobs from one board (after filters). 0 = no limit.

## `maxJobs` (type: `integer`):

Stop the run after this many jobs in total. 0 = no limit. You pay only for jobs actually saved.

## Actor input object example

```json
{
  "boards": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/openai"
  ],
  "keywords": [],
  "remoteOnly": false,
  "includeDescription": true,
  "maxJobsPerBoard": 50,
  "maxJobs": 0
}
```

# Actor output Schema

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

No description

## `errors` (type: `string`):

No description

# 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": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/openai"
    ],
    "maxJobsPerBoard": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("cheering_unicorn/ats-jobs-aggregator").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": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/openai",
    ],
    "maxJobsPerBoard": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("cheering_unicorn/ats-jobs-aggregator").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": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/openai"
  ],
  "maxJobsPerBoard": 50
}' |
apify call cheering_unicorn/ats-jobs-aggregator --silent --output-dataset

```

## MCP server setup

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

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/GxtbbRfK7vARa53FV/builds/N67vBkz3ExKnfBX4T/openapi.json