# ATS Jobs Feed: Greenhouse, Lever & Ashby Jobs API (`tobbyb/ats-jobs-feed`) Actor

Live job postings from company career boards on Greenhouse, Lever and Ashby via their official public job-board APIs. Paste slugs or careers URLs, ATS auto-detected. Filter by keyword, location, remote; get only new jobs since your last run.

- **URL**: https://apify.com/tobbyb/ats-jobs-feed.md
- **Developed by:** [Tobby Tools](https://apify.com/tobbyb) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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 Feed: Greenhouse, Lever & Ashby Jobs API

Get **live job postings straight from company career boards** hosted on **Greenhouse, Lever and Ashby**, normalized into one clean schema. Paste board slugs or careers URLs; the Actor detects the ATS, reads the board, filters by keyword, location or remote, and can return **only the jobs that are new since your last run**.

Data comes from the **official public job-board APIs** each ATS publishes for careers pages:

| ATS | Endpoint used | Docs |
|---|---|---|
| Greenhouse | `boards-api.greenhouse.io/v1/boards/{slug}/jobs?content=true` | [Job Board API](https://developers.greenhouse.io/job-board.html) |
| Lever | `api.lever.co/v0/postings/{slug}?mode=json` (EU: `api.eu.lever.co`) | [Postings API](https://github.com/lever/postings-api) |
| Ashby | `api.ashbyhq.com/posting-api/job-board/{slug}?includeCompensation=true` | [Job Postings API](https://developers.ashbyhq.com/docs/public-job-posting-api) |

No login, no browser, no proxies, no HTML scraping. Each request returns what the company already publishes for job seekers. The Actor reads boards live at run time; it is not a cached database.

### What you can do with it

- **Job alerts / monitoring**: schedule it daily with *Only new jobs since my last run* and get just the fresh postings from your target companies.
- **Job board backfill**: pull every open role from a list of employers into your site or spreadsheet.
- **Hiring signals for sales and recruiting**: see which companies are hiring for which teams and locations.
- **Market research**: track openings, departments and locations across competitors.

### Input

| Field | What it does |
|---|---|
| `companies` (required) | Board slugs or careers URLs, one per line. See below. |
| `keywords` | Keep jobs whose **title** contains any of these (case-insensitive). |
| `searchDescription` | Also match keywords inside the description. |
| `excludeKeywords` | Drop jobs whose title contains any of these. |
| `locations` | Keep jobs whose location text contains any of these, e.g. `Toronto`, `Canada`, `Remote`. |
| `remoteOnly` | Keep only jobs flagged remote (see *Remote flag* below). |
| `onlyNew` | Output only jobs not seen in your previous run with the same `snapshotName`. |
| `snapshotName` | Name of the saved state, so you can run independent monitors. |
| `includeDescription` | Include description text and HTML (default on). |
| `maxJobsPerCompany`, `maxResults` | Limits. Each output job is one charged result. |

#### Accepted company formats

- `https://boards.greenhouse.io/stripe`, `https://job-boards.greenhouse.io/stripe`
- `https://jobs.lever.co/palantir`, `https://jobs.eu.lever.co/<slug>`
- `https://jobs.ashbyhq.com/ramp`
- Plain slugs: `stripe`. The Actor checks Greenhouse, Lever and Ashby (and Lever EU if none match). If the same slug exists on more than one ATS, it uses the board with the most jobs and notes the others in the run summary.
- Forced platform: `greenhouse:stripe`, `lever:palantir`, `lever-eu:<slug>`, `ashby:ramp`.

Custom-domain careers pages (e.g. `company.com/careers`) are not auto-detected. Open one job on the page and look for the Greenhouse, Lever or Ashby URL or slug.

#### Example input

```json
{
  "companies": ["https://boards.greenhouse.io/stripe", "https://jobs.lever.co/palantir", "ashby:linear"],
  "keywords": ["engineer"],
  "locations": ["London", "Remote"],
  "onlyNew": true,
  "snapshotName": "eng-london"
}
```

### Output

One row per job:

```json
{
  "company": "Stripe",
  "companySlug": "stripe",
  "sourceAts": "greenhouse",
  "jobId": "8172503",
  "title": "Abuse Research Engineer",
  "location": "Remote from the US",
  "allLocations": ["Remote from the US", "US"],
  "remote": true,
  "workplaceType": null,
  "department": "8611 Security Analytics",
  "team": null,
  "employmentType": null,
  "salary": null,
  "postedAt": "2026-09-09T14:52:09.000Z",
  "updatedAt": "2026-10-29T14:42:09.000Z",
  "jobUrl": "https://stripe.com/jobs/search?gh_jid=8172503",
  "applyUrl": "https://stripe.com/jobs/search?gh_jid=8172503",
  "descriptionText": "Who we are\n\nAbout Stripe\n\n...",
  "descriptionHtml": "<h2>Who we are</h2>...",
  "boardUrl": "https://boards.greenhouse.io/stripe",
  "fetchedAt": "2026-11-03T21:11:31.138Z"
}
```

#### How fields map per ATS

Fields are only as complete as each ATS's public API. Missing data is `null`; nothing is guessed.

| Field | Greenhouse | Lever | Ashby |
|---|---|---|---|
| `company` | `company_name` | board slug (the API has no company name) | board slug (the API has no company name) |
| `postedAt` | `first_published` | `createdAt` | `publishedAt` (last published) |
| `updatedAt` | `updated_at` | null | null |
| `department` / `team` | first department / null | `department` / `team` | `department` / `team` |
| `employmentType` | null (not in the API) | `commitment` (e.g. Full-time) | `employmentType` (e.g. FullTime) |
| `workplaceType` | null | `workplaceType` | `workplaceType` |
| `salary` | null | null | compensation summary when the employer publishes it |
| `descriptionHtml` | `content` (HTML-unescaped) | description + lists + additional | `descriptionHtml` |

**Remote flag:** Lever and Ashby use the board's workplace type (`remote: true` only for fully remote; hybrid is `false`). Greenhouse has no remote field, so a Greenhouse job counts as remote when its location or office text says Remote or Anywhere; otherwise `remote` is `null`.

Ashby jobs marked unlisted (`isListed: false`) are skipped.

### Only new jobs since last run

With `onlyNew` on, the Actor saves the job IDs it saw per board in your named key-value store `ats-jobs-feed-state` (key `snapshot-<snapshotName>`). The **first run for each board only saves a baseline and outputs nothing for it** (so it costs only the start event). Later runs output jobs whose ID was not on the board last time. Schedule the Actor (for example daily) to get a new-jobs feed. Note that a job that is taken down and reposted with a new ID by the employer counts as new.

### Reliability

- One bad slug or a temporary error on one board never fails the run. Each company gets a status (`ok`, `not_found`, `error`, `duplicate`) in the run summary (key-value store record `SUMMARY`), with the detected ATS and counts.
- Retries with backoff on rate limits (429) and server errors; Lever pages are read with a 1-second pause, as Lever's robots.txt asks.

### Pricing

Pay per event:

- **$0.001 per job** in the dataset ($1 per 1,000 jobs)
- **$0.00005 per run start**

Boards that are not found, jobs removed by your filters and baseline runs are not charged. Use `maxResults` to cap spend per run.

### Notes and fair use

- This Actor only reads published postings from public, unauthenticated endpoints that the ATS vendors document for careers pages. It does not log in, apply to jobs or collect candidate data.
- Job descriptions belong to the employers. Respect each employer's terms when you republish their postings, and link back via `jobUrl`/`applyUrl`.
- Please don't schedule more often than you need; boards rarely change more than a few times a day.

Questions or a missing ATS? Open an issue on the Actor page.

# Actor input Schema

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

One per line. Careers URLs like https://boards.greenhouse.io/stripe, https://job-boards.greenhouse.io/stripe, https://jobs.lever.co/palantir, https://jobs.eu.lever.co/\<slug> or https://jobs.ashbyhq.com/ramp, or plain slugs like stripe (tried on Greenhouse, then Lever, then Ashby, then Lever EU). Force a platform with a prefix: greenhouse:stripe, lever:palantir, lever-eu:\<slug>, ashby:ramp. Custom-domain careers pages are not detected; use the slug instead.

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

Keep jobs whose title contains any of these words or phrases (not case-sensitive), e.g. engineer, product manager. Empty = all jobs.

## `searchDescription` (type: `boolean`):

Match keywords in the job description as well as the title.

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

Drop jobs whose title contains any of these, e.g. senior, intern.

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

Keep jobs whose location text contains any of these (not case-sensitive), e.g. Toronto, Canada, London, Remote.

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

Keep only jobs flagged remote. Lever and Ashby use the board's workplace type; Greenhouse has no remote field, so a job counts as remote when its location or office text says Remote/Anywhere.

## `onlyNew` (type: `boolean`):

Output only jobs whose ID was not on the board in your previous run with the same snapshot name. The first run for each board saves a baseline and outputs nothing for it. State is kept in your named key-value store 'ats-jobs-feed-state'.

## `snapshotName` (type: `string`):

Use different names to keep independent monitors (letters, digits, - \_ .).

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

Include the job description as plain text and HTML. Turn off for smaller rows.

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

0 = no per-company limit.

## `maxResults` (type: `integer`):

Stop after this many jobs in total (each job is one charged result).

## Actor input object example

```json
{
  "companies": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "searchDescription": false,
  "remoteOnly": false,
  "onlyNew": false,
  "snapshotName": "default",
  "includeDescription": true,
  "maxJobsPerCompany": 0,
  "maxResults": 5000
}
```

# Actor output Schema

## `results` (type: `string`):

Company, title, location, remote flag, department, type, posted date, ATS and apply link.

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

Per-company status and counts.

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

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

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

```

## MCP server setup

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

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/hCnwwkGWThWc7kcLD/builds/3VewI3ikOoNS54dbx/openapi.json