# ATS Jobs Feed: Greenhouse, Lever, Ashby, Recruitee, Personio (`longlever/ats-jobs-feed`) Actor

Live job postings straight from company career boards on Greenhouse, Lever, Ashby, Recruitee and Personio, in one normalized schema, with a changes-since-last-run mode for scheduled monitoring.

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

## Pricing

from $0.60 / 1,000 job returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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, Recruitee and Personio jobs in one schema

Give it a list of companies and get every open job straight from their own career boards, live, in one clean schema. Schedule it in **changes mode** and each run returns only the jobs that are **new, updated or removed** since the last run.

- **Live, not a stale database.** Every run reads the company's board at that moment.
- **One schema across five ATS.** Title, department, locations, remote type, employment type, seniority, salary (where published), dates, apply link and the full description.
- **Change detection built in.** Get daily new and closed roles for a company list without diffing anything yourself.
- **Hiring signals per company.** One row per company with new and closed roles and a hiring velocity, priced per company, for GTM teams and Clay tables.
- **Bring domains, not just board URLs.** Auto-discover finds which ATS a company uses from its website.
- **Cheap and predictable.** You pay per job returned, from $1.00 per 1,000 jobs.

### Who uses it

- **Recruiters and staffing firms** tracking hiring at target accounts
- **Niche job boards** backfilling and refreshing listings from employer boards
- **Sales and GTM teams** using new roles as buying signals
- **Researchers** tracking hiring by company, function and location
- **AI agents** that need fresh, structured job data (see "For AI agents" below)

### Supported ATS and input formats

| ATS | Board URL example | Shorthand |
|---|---|---|
| Greenhouse | `https://boards.greenhouse.io/airbnb` or `https://job-boards.greenhouse.io/airbnb` | `greenhouse:airbnb` |
| Lever | `https://jobs.lever.co/palantir` (EU boards: `jobs.eu.lever.co`) | `lever:palantir` |
| Ashby | `https://jobs.ashbyhq.com/ramp` | `ashby:ramp` |
| Recruitee | `https://bunq.recruitee.com` | `recruitee:bunq` |
| Personio | `https://personio.jobs.personio.de` (or `.com`) | `personio:personio` |

You can also enter a **company domain** (`stripe.com`), a **careers page URL**, or a **company name** (`Palantir`). With auto-discover on, the Actor checks the website for a board link. If that finds nothing, it tries the domain or name as a board token on each ATS and checks that the board's company name matches.

Workday, SmartRecruiters and other ATS are not supported yet. Open an issue if you need one.

### Quick start

1. Paste your companies into **Companies**, one per line.
2. Leave **Mode** on **Full snapshot** for a one-off pull.
3. Click **Start**. Results appear in the **Jobs** table and can be exported as JSON, CSV or Excel.

#### Monitor companies on a schedule (recommended)

1. Set **Mode** to **Changes since last run**.
2. Create a schedule (daily is typical) under **Schedules** in Apify Console.
3. Connect the run to Google Sheets, Slack, Airtable, a webhook, Make or n8n with Apify integrations.

The first run returns every current job as `new` and saves a baseline. After that you get only:

- `new`: posted since the last run
- `updated`: title, location, department, salary, description or apply link changed
- `removed`: no longer on the board, usually filled or closed (removed rows carry the job ID, title, locations and URL from the last time it was seen)

The baseline is keyed to your companies and filters, so changing either starts a fresh baseline. Set **State key** to give it a fixed name.

### Hiring signals mode (for GTM teams and Clay)

Set **Mode** to **Hiring signals** and give it a list of company domains. You get **one row per company** instead of one row per job:

- `open_roles`: open roles right now (after your filters)
- `new_roles_count` and `closed_roles_count`: roles opened and closed since the last run, plus `net_change`
- `hiring_velocity_30d` and `posted_last_7d`: open roles first posted in the last 30 and 7 days
- `top_departments`: where the new roles are (or the open roles on a first run)
- `new_roles` and `closed_roles`: the roles themselves, with title, department, locations and link (up to **Roles listed per company**, 25 by default)

The first run for a company is a baseline (`is_baseline: true`): it shows open roles and velocity, and the new and closed counts start from the second run. Schedule it weekly or daily. Every company you add gets its own baseline, so growing your list does not reset the others.

Every input gets a row. If a company isn't on a supported ATS, its row says `status: no_supported_board` and is not charged. Domains are resolved once and remembered for 30 days, so repeat runs don't pay to look them up again.

Use title keywords or departments to track a function, for example `engineer` or `Sales`, so the counts only cover those roles.

### Filters

| Filter | What it does |
|---|---|
| Title keywords (any) | Keep jobs whose title contains any keyword. Optionally also search the description |
| Exclude title keywords | Drop jobs whose title contains any of these |
| Locations (any) | Keep jobs where a location contains any value, for example `London`, `Germany`, `Remote` |
| Remote only | Keep fully remote jobs only |
| Departments or teams (any) | Match on department or team |
| Posted within days | Keep recently posted jobs |
| Max jobs per company | Snapshot mode only, keeps the newest |

### Output

One row per job. Example (description shortened):

```json
{
  "company": "ramp",
  "ats": "ashby",
  "board_token": "ramp",
  "job_id": "0d52b853-4088-45dd-8c4b-0702da1bf5ed",
  "title": "Lead Recruiter | Executive",
  "department": "People & Talent",
  "team": "People & Talent",
  "locations": ["New York, NY (HQ)", "San Francisco, CA", "Remote (US)"],
  "remote_type": "hybrid",
  "employment_type": "full_time",
  "seniority": "lead",
  "posted_at": "2026-10-19T17:06:15.365000Z",
  "updated_at": null,
  "job_url": "https://jobs.ashbyhq.com/ramp/0d52b853-4088-45dd-8c4b-0702da1bf5ed",
  "apply_url": "https://jobs.ashbyhq.com/ramp/0d52b853-4088-45dd-8c4b-0702da1bf5ed/application",
  "salary_min": 180000,
  "salary_max": 250000,
  "salary_currency": "USD",
  "salary_period": "year",
  "description_text": "ABOUT RAMP\n\nRamp is building the smart infrastructure for finance teams...",
  "description_html": null,
  "change_type": null,
  "source_input": "https://jobs.ashbyhq.com/ramp",
  "fetched_at": "2026-10-19T18:28:12Z"
}
```

**Field notes**

- `remote_type`: `remote`, `hybrid`, `onsite` or `unknown`.
- `employment_type`: `full_time`, `part_time`, `contract`, `temporary`, `intern` or `other`.
- `seniority`: `intern`, `entry`, `senior`, `lead`, `manager`, `director` or `executive`. It is derived from the title or the ATS's own level field, and is null when there is no signal.
- **Salary** fields are filled only when the company publishes pay. `salary_period` is null for Greenhouse because Greenhouse does not state one.
- `change_type` is null in snapshot mode.
- `source_input` is the line from your input that produced the row, so you can join results back to your list.
- Each run also writes a `SUMMARY` record to the key-value store. It lists every board with its match count, how each input was resolved (`input`, `page_link` or `slug_guess`), and any inputs that failed or could not be resolved.

### Pricing

Pay per event. You only pay for what the run delivers.

| Event | Price (Free and Starter plans) |
|---|---|
| Job returned (new, updated, removed or snapshot row) | $0.001 ($1.00 per 1,000) |
| Company checked (one per board per run) | $0.0003 |
| Company resolved by auto-discover (first time only, then remembered for 30 days) | $0.002 |
| Hiring signal (one company row in hiring signals mode; no per-job or company-checked charge in that mode) | $0.002 |

Higher Apify plans get lower per-job prices. A daily changes-mode run over 100 companies costs about $0.03 for the checks plus $0.001 per changed job. Set a maximum cost per run in the run options and the Actor stops cleanly at that limit. In changes mode a board cut off by the limit is not marked as seen, so the next run delivers it.

### For AI agents

- **Input:** `companies` (array of board URLs, `ats:token`, domains or names), `mode` (`snapshot`, `changes` or `signals`), and the optional filters above.
- **Output:** one row per job in `snapshot` and `changes`; one row per company in `signals`. The run `SUMMARY` key-value record lists errors and unresolved inputs.
- **Cost:** about $0.001 per job plus $0.0003 per company, or $0.002 per company in `signals`. Use `maxJobsPerCompany` and title or location filters to keep runs small.
- **Hiring signals for a list of domains:** use `mode: signals`. It's the cheapest way to answer "which of these companies are hiring, and for what" on a schedule.

### Limits and good practice

- The Actor reads public job board endpoints that each ATS provides for publishing jobs. It does not log in, bypass access controls or collect applicant data.
- Requests are rate-limited per host and retried on temporary errors.
- Auto-discover is best effort. Inputs resolved by `slug_guess` are usually right, but check them in `SUMMARY` before relying on them.
- Personio and Recruitee boards are usually smaller European companies. Coverage depends on which ATS your target companies use.

### Support

Open an issue on the Actor page. Issues are answered within one business day. If the Actor saves you time, a rating helps other people find it.

# Actor input Schema

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

One per line. Accepts board URLs (boards.greenhouse.io/airbnb, jobs.lever.co/palantir, jobs.ashbyhq.com/ramp, bunq.recruitee.com, personio.jobs.personio.de), shorthand like greenhouse:airbnb, or company domains and names when auto-discover is on.

## `mode` (type: `string`):

Snapshot returns every matching job. Changes returns only jobs that are new, updated or removed since the last run with the same companies and filters. Hiring signals returns one row per company: new and closed roles since the last run plus a hiring velocity, charged per company instead of per job (schedule it weekly or daily for GTM and Clay workflows).

## `autoDiscover` (type: `boolean`):

For inputs that are not board URLs, look for the company's ATS board on its website. Charged per company resolved.

## `guessSlugs` (type: `boolean`):

If the website check finds nothing, try the domain or name as a board token on each ATS. Rows found this way have resolvedBy = slug_guess in the run SUMMARY; check them before relying on them.

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

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

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

Drop jobs whose title contains any of these.

## `searchInDescription` (type: `boolean`):

Match title keywords against the job description too, not just the title.

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

Keep jobs where any location contains one of these, for example "London", "Germany", "Remote".

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

Keep only jobs the ATS marks as fully remote.

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

Keep jobs whose department or team contains any of these, for example "Engineering" or "Sales".

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

Keep jobs posted (or last updated, where the ATS gives no post date) within this many days.

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

0 means no limit. Newest jobs are kept. Ignored in changes mode so no change is ever skipped.

## `maxRolesListed` (type: `integer`):

In hiring signals mode, how many new and closed roles to list by name in each company row. Counts always cover every role.

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

Include the plain-text job description in each row.

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

Also include the original description HTML. Makes rows larger.

## `stateKey` (type: `string`):

Optional name for the saved state. By default it is derived from your companies and filters, so changing either starts a fresh baseline.

## `maxConcurrency` (type: `integer`):

How many company boards to fetch at once. Requests to each ATS host are also rate-limited.

## Actor input object example

```json
{
  "companies": [
    "https://boards.greenhouse.io/airbnb",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/ramp",
    "https://bunq.recruitee.com",
    "https://personio.jobs.personio.de"
  ],
  "mode": "snapshot",
  "autoDiscover": true,
  "guessSlugs": true,
  "searchInDescription": false,
  "remoteOnly": false,
  "maxJobsPerCompany": 25,
  "maxRolesListed": 25,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "maxConcurrency": 8
}
```

# Actor output Schema

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

One row per job. In changes mode, only new, updated and removed jobs.

## `signals` (type: `string`):

Signals mode: one row per company with new and closed roles since the last run and a hiring velocity.

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

Every board checked with its match count, how each input was resolved, and any errors or unresolved inputs.

# 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/airbnb",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/ramp",
        "https://bunq.recruitee.com",
        "https://personio.jobs.personio.de"
    ],
    "maxJobsPerCompany": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("longlever/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/airbnb",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/ramp",
        "https://bunq.recruitee.com",
        "https://personio.jobs.personio.de",
    ],
    "maxJobsPerCompany": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("longlever/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/airbnb",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/ramp",
    "https://bunq.recruitee.com",
    "https://personio.jobs.personio.de"
  ],
  "maxJobsPerCompany": 25
}' |
apify call longlever/ats-jobs-feed --silent --output-dataset

```

## MCP server setup

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