# ATS Jobs API — Greenhouse, Lever & Ashby Career Site Jobs (`lifezero/ats-jobs-api`) Actor

A job scraper for careers page jobs on Greenhouse, Lever and Ashby: all open job listings in one dataset with title, location, remote flag, department, posted date, apply URL, salary and full description. Official public job-board APIs, no login or proxies.

- **URL**: https://apify.com/lifezero/ats-jobs-api.md
- **Developed by:** [Rashed Alsuwaidi](https://apify.com/lifezero) (community)
- **Categories:** Jobs, Lead generation, Developer tools
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 job results

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 API — Greenhouse, Lever & Ashby career site jobs

Get **every open job** from company career sites hosted on **Greenhouse, Lever and Ashby** in one clean, unified dataset: a job scraper for careers page jobs that returns ready-to-use job listings. No login, no proxies, no browser: the Actor reads the official public job-board APIs these ATS vendors publish for embedding career pages, so runs take seconds and cost little.

### What you get

One row per open job, with the same fields whatever the ATS:

| Field | Example |
|---|---|
| `company` | Stripe |
| `title` | Backend Engineer, Payments |
| `location` | Dublin, Ireland; Remote |
| `remote` / `workplaceType` | true / Remote |
| `department` / `team` | Engineering |
| `employmentType` | FullTime |
| `postedAt` | 2026-09-28T14:02:11Z |
| `applyUrl` / `jobUrl` | direct apply link |
| `description` | full plain-text description (HTML optional) |
| `compensation` | salary range when the company publishes it |
| `ats`, `companySlug`, `jobId`, `scrapedAt` | for joins and de-duplication |

#### Example output item

```json
{
  "ats": "greenhouse",
  "company": "Stripe",
  "title": "Backend Engineer, Payments",
  "location": "Dublin, Ireland",
  "remote": false,
  "department": "Engineering",
  "postedAt": "2026-09-28T14:02:11Z",
  "applyUrl": "https://stripe.com/jobs/listing/.../apply",
  "description": "Who we are ...",
  "jobId": "6123456",
  "scrapedAt": "2026-10-02T15:50:00Z"
}
```

### How to use

1. Add companies, one per line:
   - `greenhouse:stripe`, `lever:palantir`, `ashby:openai`
   - or paste the board URL: `https://boards.greenhouse.io/stripe`, `https://jobs.lever.co/palantir`, `https://jobs.ashbyhq.com/openai`
   - or just a slug, and the Actor auto-detects the ATS.
2. Optional filters: title keywords, exclude keywords, locations, remote only, departments, posted within N days, per-company and total limits.
3. Run, then download JSON, CSV or Excel, or call it from the API, a schedule, Make, Zapier, n8n or an AI agent (MCP).

The default input (5 well-known companies) works out of the box and finishes in under a minute.

### Works with these companies

Verified on 2026-10-02 with one request to each company's public job board (open jobs at check time):

| Company | Input | Open jobs |
|---|---|---|
| OpenAI | `ashby:openai` | 831 |
| Stripe | `greenhouse:stripe` | 710 |
| Palantir | `lever:palantir` | 319 |
| Airbnb | `greenhouse:airbnb` | 149 |
| Notion | `ashby:notion` | 134 |

Any other company on Greenhouse, Lever or Ashby works too: use the slug from its careers page URL.

#### Common setups (copy into the JSON input)

**Remote engineering jobs at target companies**

```json
{ "companies": ["greenhouse:stripe", "ashby:openai", "lever:palantir"], "keywords": ["engineer"], "remoteOnly": true }
```

**New jobs since yesterday (run on a daily schedule)**

```json
{ "companies": ["greenhouse:airbnb", "ashby:notion"], "postedWithinDays": 1 }
```

**Hiring signals for sales (cheap, fast run)**

```json
{ "companies": ["greenhouse:stripe", "greenhouse:airbnb", "ashby:openai", "ashby:notion", "lever:palantir"], "maxJobsPerCompany": 20, "includeDescription": false }
```

### Call it from the API, a schedule or an AI agent

Run it synchronously and get the jobs back in one HTTP call (replace `<YOUR_TOKEN>`):

```bash
curl -X POST "https://api.apify.com/v2/acts/lifezero~ats-jobs-api/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["greenhouse:stripe", "lever:palantir", "ashby:openai"], "keywords": ["engineer"], "postedWithinDays": 7}'
```

- **Daily feed of new jobs:** save the input as a task, set `postedWithinDays` to 1 and add a daily schedule.
- **AI agents and MCP clients:** every input field has a plain description, so an agent can pass a company slug and filters and read back structured jobs.

### Use cases

- Job boards and aggregators: keep listings fresh from hundreds of career sites.
- Recruiters and sales teams: spot companies hiring for a role (hiring signals, lead generation).
- Market research: track hiring by department and location over time.
- Job seekers: monitor target companies daily with a schedule and filters.
- AI agents: a clear input schema so agents and MCP clients can fetch live jobs for a company.

### FAQ

**Is this a Greenhouse jobs API, a Lever jobs API and an Ashby jobs API in one?**
Yes. Mix companies from all three in one run; every job comes back with the same fields, and the `ats` field tells you where it came from.

**How do I find a company's slug?**
Open its careers page. `boards.greenhouse.io/stripe` → `greenhouse:stripe`; `jobs.lever.co/palantir` → `lever:palantir`; `jobs.ashbyhq.com/openai` → `ashby:openai`. You can also paste the full URL.

**What happens if a company does not use one of these ATS?**
The board is reported as not found in the `SUMMARY` record and skipped; the rest of the run continues and you are not charged for it.

**How fresh is the data?**
Live: each run reads the career site's job board at run time, so closed jobs disappear and new jobs appear on the next run.

**How much does a run cost?**
$1.20 per 1,000 jobs saved, plus a tiny start fee. A run over the 5 default companies (about 2,000 jobs) costs about $2.40; with `maxJobsPerCompany` 50 it costs about $0.30.

**Do I need proxies or a login?**
No. The Actor reads the public job-board endpoints the ATS vendors publish for embedding career pages.

### Pricing

You pay $1.20 per 1,000 jobs: one 'Job result' event per job saved, plus a tiny start fee. The 'Default dataset item' event in the price table is never charged by this Actor. Jobs removed by your filters are not charged.

### Notes

- Data comes only from the public posting APIs the ATS vendors provide for career-site embedding. Unlisted or internal jobs are not included.
- A board that does not exist is reported in the `SUMMARY` record and skipped; the run continues.
- Tip: find a company's slug in its careers page URL (for example `boards.greenhouse.io/<slug>`).

# Actor input Schema

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

One per line. Use ats:slug (greenhouse:stripe, lever:palantir, ashby:openai), a board URL (https://boards.greenhouse.io/stripe, https://jobs.lever.co/palantir, https://jobs.ashbyhq.com/openai), or just a slug to auto-detect the ATS.

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

Keep jobs whose title contains any of these (case-insensitive). Empty = all jobs.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these.

## `locations` (type: `array`):

Keep jobs whose location contains any of these, e.g. London, United States, Remote.

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

Keep only remote jobs.

## `departments` (type: `array`):

Keep jobs whose department or team contains any of these, e.g. Engineering.

## `postedWithinDays` (type: `integer`):

0 = any date.

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

Adds the full job description as text.

## `includeDescriptionHtml` (type: `boolean`):

Adds the original HTML description.

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

0 = no limit.

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

0 = no limit.

## Actor input object example

```json
{
  "companies": [
    "ashby:openai",
    "greenhouse:stripe",
    "lever:palantir",
    "greenhouse:airbnb",
    "ashby:notion"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "remoteOnly": false,
  "departments": [],
  "postedWithinDays": 0,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "maxJobsPerCompany": 50,
  "maxJobs": 0
}
```

# Actor output Schema

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

One item per open job, same fields for every ATS.

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

Jobs found and matched per company board, plus boards that were not found.

# 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": [
        "ashby:openai",
        "greenhouse:stripe",
        "lever:palantir",
        "greenhouse:airbnb",
        "ashby:notion"
    ],
    "maxJobsPerCompany": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("lifezero/ats-jobs-api").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": [
        "ashby:openai",
        "greenhouse:stripe",
        "lever:palantir",
        "greenhouse:airbnb",
        "ashby:notion",
    ],
    "maxJobsPerCompany": 50,
}

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

```

## MCP server setup

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

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/tvz1W1I058TLPQ1rg/builds/BntHEk69FDJRG0glD/openapi.json