# Greenhouse, Lever, Ashby, Workable, Recruitee & Personio Jobs (`cleanapi/ats-job-feed`) Actor

One API for Greenhouse, Lever, Ashby, Workable, Recruitee and Personio job boards. Pass a company domain, get every open role in a single schema. Duplicates are removed before billing, empty runs cost nothing, and posting dates come from the platform, never today's date.

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

## Pricing

from $4.00 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Job postings from Greenhouse, Lever, Ashby, Workable, Recruitee & Personio

Give it a company domain or a careers page URL. Get every open role that company
has published, whatever applicant tracking system it runs, in one schema.

### What you are guaranteed

- **No duplicates charged.** Deduplication happens on a stable key, before
  billing. Not after.
- **No empty results charged.** Billing follows delivery, never the other way
  around.
- **Real posting dates.** `postedAt` is never filled with today's date.
  `postedAtSource` always tells you where the date came from: `platform_field`
  for a genuine publication date, `platform_created_at` when the platform only
  exposes a creation date, `unavailable` when it gives nothing. The field is then
  `null` rather than guessed.
- **A country filter that works on all six platforms.** Recruitee and Workable
  supply an ISO code directly. The other four publish only a free-text location,
  so the country is derived from it and flagged as `derived_from_location`, never
  passed off as reported data. A posting whose location cannot be resolved is
  dropped with reason `country_unknown`, never counted as a match. On a real
  sample of 635 postings, 93% resolved; the rest carried labels like "N/A".
- **Never an empty output without a reason.** Every company gets a status in the
  coverage report: `ok`, `no_open_positions`, `platform_not_detected` or
  `fetch_failed`, with the detail.
- **No runaway runs.** `maxResults` and `maxRuntimeSecs` are hard limits.

### Platforms

| Platform | Source |
|---|---|
| Greenhouse | `boards-api.greenhouse.io`, documented public API |
| Lever | `api.lever.co`, documented public API |
| Ashby | `api.ashbyhq.com`, documented public API |
| Recruitee | `{account}.recruitee.com`, documented public API |
| Workable | `apply.workable.com`, undocumented endpoint, monitored daily |
| Personio | `{account}.jobs.personio.de/xml`, public XML feed |

### Known limits, stated upfront

- **Personio has no publication date.** It only exposes a creation date, so
  `postedAtSource` reads `platform_created_at`. A role created in 2017 and still
  open will carry that date.
- **Personio descriptions are often empty.** Around 19% of Personio postings
  carry a description, because many companies leave that block blank in their
  feed. Nothing can be done about it from the outside.
- **Lever descriptions.** About 92% of Lever postings have one. The rest have
  neither a plain-text nor an HTML description on the platform itself.
- **Four platforms expose no country code.** Greenhouse, Lever, Ashby and
  Personio publish a location label only. The country is derived from it, which
  works for about 93% of postings in practice. `countrySource` always tells you
  which postings were derived.
- **Greenhouse does not expose remote or employment type.** When the location
  says "Remote", the `remote` field is set to `true` and `remoteSource` reads
  `derived_from_location`, so you always know it was inferred and not reported.

### Spend limit per run

Apify defaults to a maximum cost of $4.99 per run, which is roughly 415 postings
at $0.012 each. A larger request stops cleanly with `charge_limit_reached`, a
warning in the log, and the detail in the coverage report. Raise
*Maximum cost per run* in the run options to go further.

### Input

```json
{
  "companies": ["stripe.com", "https://jobs.lever.co/spotify"],
  "platforms": ["greenhouse", "lever"],
  "postedAfter": "2026-06-01",
  "country": "NL",
  "excludeCompanies": [],
  "excludeKeywords": ["intern"],
  "maxResults": 1000,
  "maxRuntimeSecs": 900
}
```

A bare domain triggers automatic platform detection. A careers page URL is
faster and always reliable, so prefer it when you have it.

### Output

One posting per dataset item.

```json
{
  "jobId": "greenhouse:stripe:8172508",
  "title": "Abuse Investigator",
  "company": "Stripe",
  "department": "Security Analytics",
  "location": "Dublin",
  "country": "IE",
  "countries": ["IE"],
  "countrySource": "derived_from_location",
  "remote": null,
  "remoteSource": "unavailable",
  "employmentType": null,
  "description": "<h2>Who we are</h2>...",
  "applyUrl": "https://stripe.com/jobs/search?gh_jid=8172508",
  "postedAt": "2026-09-03T17:32:53.000Z",
  "postedAtSource": "platform_field",
  "collectedAt": "2026-09-12T10:46:59.837Z",
  "sourcePlatform": "greenhouse",
  "sourceUrl": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs?content=true",
  "salary": null
}
```

A coverage report is written to the `COVERAGE_REPORT` key of the key-value
store, listing every company, the platform it resolved to, how many postings
were found, how many were delivered, and why any were dropped.

### Keywords

greenhouse api, lever api, ashby api, workable api, recruitee api, personio xml,
ats jobs, job board api, career site jobs, hiring signals, job postings feed,
applicant tracking system, boards-api.greenhouse.io, jobs.lever.co,
api.ashbyhq.com

# Actor input Schema

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

Company domains (stripe.com), careers page URLs, or platform tokens. A careers page URL is faster and always reliable; a bare domain triggers automatic platform detection.

## `platforms` (type: `array`):

Leave empty to query every supported platform.

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

ISO date. Postings whose publication date is unknown are excluded while this filter is active, rather than being passed off as recent.

## `country` (type: `string`):

Filters on country, e.g. FR, GB, US. Recruitee and Workable supply an ISO code directly; on the other four platforms the country is derived from the location label and flagged as derived\_from\_location. Postings whose location cannot be resolved are dropped with reason country\_unknown, never passed off as a match.

## `excludeCompanies` (type: `array`):

Company names to drop from the results. Case-insensitive.

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

Postings whose title contains any of these words are dropped. Case-insensitive.

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

Hard limit. The run stops cleanly once reached.

## `maxRuntimeSecs` (type: `integer`):

Hard limit. No run can go on indefinitely.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "https://jobs.lever.co/spotify"
  ],
  "platforms": [],
  "excludeCompanies": [],
  "excludeKeywords": [],
  "maxResults": 1000,
  "maxRuntimeSecs": 900
}
```

# Actor output Schema

## `postings` (type: `string`):

One item per delivered posting, in a single schema across all six platforms.

## `coverage` (type: `string`):

Per company: the platform it resolved to, postings found, delivered, and dropped with the reason.

# 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": [
        "stripe.com",
        "https://jobs.lever.co/spotify"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("cleanapi/ats-job-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": [
        "stripe.com",
        "https://jobs.lever.co/spotify",
    ] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cleanapi/ats-job-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/9qCNxM4I0mXK6ayeO/builds/6teEoebEKNPxtO46i/openapi.json