# ATS Jobs Multi-Board — Greenhouse, Ashby & Lever, Deduped (`alaudinburki/ats-jobs-multiboard`) Actor

Search thousands of company job boards at once and get one deduplicated list, with first_seen so you can tell what is genuinely new.

- **URL**: https://apify.com/alaudinburki/ats-jobs-multiboard.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **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 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 Multi-Board — Greenhouse, Ashby & Lever, Deduped

Search thousands of company job boards at once and get one deduplicated list, with first_seen so you can tell what is genuinely new.

### How to use

1. Open [ats-jobs-multiboard on Apify](https://apify.com/alaudinburki/ats-jobs-multiboard).
2. Enter the required input and adjust any limits in the input form.
3. Run the Actor and download its dataset from Apify.

### Inputs

| Field | Purpose | Default |
|---|---|---|
| `boards` | Which company job boards to read. Use "provider:token" (greenhouse, ashby or lever), or just the company token — that defaults to Greenhouse. Find the token in the board URL, e.g. boards.greenhouse.io/vercel. | — |
| `query` | Only keep jobs whose title, department or location contains these words (all of them). Leave empty for every job. | — |
| `locationContains` | Only keep jobs whose location contains this text, case-insensitive. e.g. "remote", "London", "Germany". | — |
| `remoteOnly` | Keep only postings that look remote, judged from the location, title and the board's own remote flag. | false |
| `onlyNewSinceLastRun` | Return only jobs not seen in any previous run, and set isNew. Requires a saved run history — see snapshotKey. Leave off on the first run. | false |
| `snapshotKey` | Where the seen-jobs baseline is stored. Change it to keep separate histories for separate searches. | "SEEN_JOBS" |
| `includeDescription` | Include up to 2,000 characters of the posting's description, converted to plain text. | true |
| `maxItems` | Stop after this many jobs. Keeps a wide board sweep from running away. | 2000 |

### Output dataset

| Field | Meaning |
|---|---|
| `id` | Stable identifier from the source. Use it to link records across runs. |
| `sourceId` | Identifier of the source this record came from. |
| `provider` | The AI provider this row measured. |
| `board` | The job board the posting came from. |
| `title` | Title as the source writes it. |
| `company` | Company name as the source writes it. |
| `location` | Location as the source writes it. |
| `department` | Government department the contract or grant belongs to. |
| `employmentType` | Employment type as posted. |
| `remote` | Whether the posting is remote. |
| `url` | The URL this row describes. |
| `publishedAt` | ISO 8601 timestamp of publication. |
| `updatedAt` | ISO 8601 timestamp of the most recent upstream update. |
| `description` | Description of this record, as published by the source. |

### Pricing and limits

Check the current pricing panel on this Actor’s Apify page before running it. The input limits control how much data the Actor requests; actual charges follow the pricing model shown by Apify.

Results depend on the source service and the input supplied. Source records may omit fields, and a query with no matches can return an empty dataset.

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- ATS Jobs Multi-Board — Greenhouse, Ashby & Lever, Deduped declares all 14 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of ATS Jobs Multi-Board include id, sourceId, provider, board, title and company.
- ATS Jobs Multi-Board needs no API key, login or account of any kind before its first run.
- ATS Jobs Multi-Board needs 1 required input: `boards`.
- ATS Jobs Multi-Board documents `id` as: Stable identifier from the source. Use it to link records across runs.
- Every number published about ATS Jobs Multi-Board is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- ATS Jobs Multi-Board is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

### Limitations

- ATS Jobs Multi-Board reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
- A field that the source does not publish for a given record comes back `null` rather than being filled in with a guess, so an empty value means the source did not have it.
- Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
- This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

### FAQ

**What does ATS Jobs Multi-Board return?**

It returns 14 documented output fields — `id`, `sourceId`, `provider`, `board`, `title`, `company`, `location` and `department` — each with a declared type and a written description. The full schema is below.

**What does ATS Jobs Multi-Board require to run?**

`boards` is required. Everything else has a default.

**Does ATS Jobs Multi-Board need an API key?**

No. It reads only public data and asks for no account.

**How is ATS Jobs Multi-Board billed?**

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.

# Actor input Schema

## `boards` (type: `array`):

Which company job boards to read. Use "provider:token" (greenhouse, ashby or lever), or just the company token — that defaults to Greenhouse. Find the token in the board URL, e.g. boards.greenhouse.io/vercel.

## `query` (type: `string`):

Only keep jobs whose title, department or location contains these words (all of them). Leave empty for every job.

## `locationContains` (type: `string`):

Only keep jobs whose location contains this text, case-insensitive. e.g. "remote", "London", "Germany".

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

Keep only postings that look remote, judged from the location, title and the board's own remote flag.

## `onlyNewSinceLastRun` (type: `boolean`):

Return only jobs not seen in any previous run, and set isNew. Requires a saved run history — see snapshotKey. Leave off on the first run.

## `snapshotKey` (type: `string`):

Where the seen-jobs baseline is stored. Change it to keep separate histories for separate searches.

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

Include up to 2,000 characters of the posting's description, converted to plain text.

## `maxItems` (type: `integer`):

Stop after this many jobs. Keeps a wide board sweep from running away.

## Actor input object example

```json
{
  "boards": [
    "greenhouse:vercel",
    "ashby:openai",
    "greenhouse:stripe"
  ],
  "query": "engineer",
  "locationContains": "remote",
  "remoteOnly": false,
  "onlyNewSinceLastRun": false,
  "snapshotKey": "SEEN_JOBS",
  "includeDescription": true,
  "maxItems": 2000
}
```

# Actor output Schema

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

One row per item, with the 14 fields listed under Views.

# 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 = {
    "boards": [
        "greenhouse:vercel",
        "ashby:openai",
        "greenhouse:stripe"
    ],
    "query": "engineer",
    "locationContains": "remote"
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/ats-jobs-multiboard").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 = {
    "boards": [
        "greenhouse:vercel",
        "ashby:openai",
        "greenhouse:stripe",
    ],
    "query": "engineer",
    "locationContains": "remote",
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/ats-jobs-multiboard").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 '{
  "boards": [
    "greenhouse:vercel",
    "ashby:openai",
    "greenhouse:stripe"
  ],
  "query": "engineer",
  "locationContains": "remote"
}' |
apify call alaudinburki/ats-jobs-multiboard --silent --output-dataset

```

## MCP server setup

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

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/QlatnNGablvSUQsw9/builds/mecsVtuDz4izZ93IN/openapi.json