# ATS Job Boards API (`timbered_oak/ats-job-boards-api`) Actor

Job listings from Greenhouse, Lever, Ashby, and Workable public board APIs.

- **URL**: https://apify.com/timbered\_oak/ats-job-boards-api.md
- **Developed by:** [Mark](https://apify.com/timbered_oak) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.40 / 1,000 job posting scrapeds

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?

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

## ATS Job Boards API

Job listings pulled straight from the four ATS vendors' own public,
unauthenticated board APIs: Greenhouse, Lever, Ashby, Workable. No login, no
proxy, no scraping of rendered pages — these are the same JSON endpoints the
vendors' own embeddable widgets call.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `source` | enum: `greenhouse`, `lever`, `ashby`, `workable`, `auto` | yes | Which ATS to hit. `auto` detects from a board URL, or tries each API in turn for a bare slug. |
| `slugs` | array of strings | yes | Company board slugs (`"gitlab"`) or full board URLs (`https://boards.greenhouse.io/gitlab`, `https://jobs.lever.co/spotify`, `https://jobs.ashbyhq.com/ramp`, `https://apply.workable.com/huggingface`). |
| `maxJobs` | integer | no | Cap on rows pushed per slug. Leave empty for no cap. |

**v1 limit:** no bundled seed list of company slugs. You supply the
slugs/URLs; the actor does not discover or guess them. A curated seed list is
future work, not v1.

### Output example

One row per job in the default dataset (real row from a live smoke run,
description truncated here):

```json
{
    "source": "greenhouse",
    "companySlug": "gitlab",
    "title": "Account Executive - Italy",
    "location": "Remote, Italy",
    "department": "EMEA - Commercial",
    "remote": true,
    "employmentType": null,
    "postedAt": "2026-04-17T05:58:03-04:00",
    "updatedAt": "2026-08-31T17:56:36-04:00",
    "applyUrl": "https://job-boards.greenhouse.io/gitlab/jobs/8503792002",
    "description": "<div class=\"content-intro\"><p>GitLab is the intelligent orchestration platform for DevSecOps...</p></div>"
}
```

No recruiter names, emails, or other personal data — those fields are
dropped, not just left null.

### Pricing

Pay-per-event. One `job-scraped` event is charged per job row pushed
(`Actor.charge({ eventName: 'job-scraped' })`), never charged for an empty
result. **$0.0034 per event** ($3.40 per 1,000 jobs) — configured in the
Apify Console pricing step, not in this repo.

### Limits / known gaps

- No seed list — see v1 limit above.
- `employmentType` is `null` on Greenhouse; that ATS doesn't expose it in the
  public jobs feed.
- Ashby boards can run into the tens of MB (openai's is ~12 MB). This actor
  caps each job's description to 20,000 characters rather than streaming the
  response — fine for reading, not for re-hosting the full HTML verbatim.
- `auto` mode with a bare slug (no URL) tries Greenhouse → Lever → Ashby →
  Workable in order and returns the first board that resolves; a slug that
  happens to exist on two boards silently returns only the first match.
- A slug/board with zero open jobs returns zero rows for that slug (a
  warning is logged) rather than failing the whole run.

# Actor input Schema

## `source` (type: `string`):

Which applicant-tracking-system API to hit. Use "auto" to detect from a board URL, or try each API in turn for a bare slug.

## `slugs` (type: `array`):

Company board slugs (e.g. "gitlab") or full board URLs (e.g. https://boards.greenhouse.io/gitlab, https://jobs.lever.co/spotify, https://jobs.ashbyhq.com/ramp, https://apply.workable.com/huggingface). No seed list is bundled — v1 only scrapes slugs you supply.

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

Cap on rows pushed per company (per source, in auto mode). Leave empty for no cap.

## Actor input object example

```json
{
  "source": "auto",
  "slugs": [
    "gitlab"
  ]
}
```

# Actor output Schema

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

All scraped rows as JSON

# 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 = {
    "slugs": [
        "gitlab"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("timbered_oak/ats-job-boards-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 = { "slugs": ["gitlab"] }

# Run the Actor and wait for it to finish
run = client.actor("timbered_oak/ats-job-boards-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 '{
  "slugs": [
    "gitlab"
  ]
}' |
apify call timbered_oak/ats-job-boards-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,timbered_oak/ats-job-boards-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/1zcle1vacw5RegK7p/builds/fUU5JRmKHzERZz7sb/openapi.json