# Multi-Board Job Deduplicator & Hiring Intelligence (`seemuapps/multi-board-job-intelligence`) Actor

Collect, normalize and deduplicate Greenhouse, Lever and Ashby jobs and calculate employer hiring intent.

- **URL**: https://apify.com/seemuapps/multi-board-job-intelligence.md
- **Developed by:** [Andrew](https://apify.com/seemuapps) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 unique jobs

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/platform/actors/running/actors-in-store#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

## Multi-Board Job Deduplicator & Hiring Intelligence

Collect job postings from public Greenhouse, Lever, and Ashby career boards, normalize them into one clean schema, strip out cross-posted duplicates, and get an employer-level hiring score for every company you track. One row per real job — not per listing.

### What you get

One dataset record per unique job posting:

- **Job**: title, department, location, direct apply URL, publish date, and the board's own job ID
- **Company and source**: which employer posted it and which board it came from (`greenhouse`, `lever`, `ashby`)
- **Remote flag**: postings detected as remote, so you can filter to remote-only in one click
- **Deduplicated**: the same role cross-posted to two boards, or listed twice under different IDs, collapses to a single record
- **Employer hiring summary** (in the key-value store): open roles, remote roles, departments hiring, and a 0–100 hiring intent score per company, ranked
- Export to JSON, CSV, Excel, or Google Sheets directly from the Apify console

### Use cases

- Hiring intent and lead generation — companies staffing up are companies buying; rank your target list by hiring score
- Job board aggregation — power a niche job site or newsletter from dozens of company boards without duplicate listings
- Competitor and market intelligence — see which departments a competitor is scaling and where
- Recruiting and talent mapping — track open roles across a whole portfolio or industry in one dataset
- Remote job feeds — filter every board down to remote-only roles matching your keywords

### How to use

1. Add your **Career boards** — one entry per company with `company`, `source` (`greenhouse`, `lever`, or `ashby`), and the `board` slug from its careers URL
2. Optionally add **Title keywords** to keep only matching roles (case-insensitive, matched anywhere in the title)
3. Optionally toggle **Remote only**
4. Run the actor — unique jobs land in the **Dataset** tab, and the employer summary in the **Key-value store** tab under `SUMMARY`

```json
{
  "boards": [
    { "company": "Example", "source": "greenhouse", "board": "example" },
    { "company": "Acme", "source": "lever", "board": "acme" }
  ],
  "keywords": ["engineer", "designer"],
  "remoteOnly": false
}
```

The board slug is the last part of the public careers URL — `boards.greenhouse.io/example`, `jobs.lever.co/acme`, or `jobs.ashbyhq.com/acme` all give you `example` / `acme`.

### Output format

Dataset — one record per unique job:

```json
{
  "company": "Example",
  "source": "greenhouse",
  "jobId": "4012345",
  "title": "Senior Software Engineer",
  "location": "Remote",
  "url": "https://boards.greenhouse.io/example/jobs/4012345",
  "publishedAt": "2026-08-01T00:00:00Z",
  "department": "Engineering",
  "isRemote": true
}
```

`SUMMARY` key-value store record — one entry per employer, ranked by hiring intent:

```json
[
  {
    "company": "Example",
    "openRoles": 24,
    "remoteRoles": 11,
    "departments": ["Engineering", "Sales", "Design"],
    "hiringIntentScore": 100
  }
]
```

### FAQ

**How are duplicates detected?** Jobs are matched on company, title, and location after normalization, so the same role posted to two boards or re-listed under a new ID appears once.

**Do I need a login or API key for the boards?** No. Only public career boards are read.

**What if one board fails?** That board is skipped with a warning and the run continues — a single broken slug never costs you the rest of the results.

**Where is the employer summary?** In the **Key-value store** tab of the run, under the `SUMMARY` record. The dataset stays one-row-per-job so CSV and Sheets exports stay clean.

**Can I run it on a schedule?** Yes — run it daily to track how many roles each employer has open over time.

# Actor input Schema

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

Public ATS boards to collect, each with company, source (greenhouse, lever, or ashby), and board slug.

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

Optional case-insensitive job-title keywords. Leave empty to include every role.

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

Only return job postings detected as remote.

## `fixtureMode` (type: `boolean`):

Use deterministic sample records without calling live ATS APIs.

## Actor input object example

```json
{
  "boards": [
    {
      "company": "Example",
      "source": "greenhouse",
      "board": "example"
    }
  ],
  "keywords": [],
  "remoteOnly": false,
  "fixtureMode": false
}
```

# Actor output Schema

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

No description

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

No description

# 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": [
        {
            "company": "Example",
            "source": "greenhouse",
            "board": "example"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seemuapps/multi-board-job-intelligence").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": [{
            "company": "Example",
            "source": "greenhouse",
            "board": "example",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("seemuapps/multi-board-job-intelligence").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": [
    {
      "company": "Example",
      "source": "greenhouse",
      "board": "example"
    }
  ]
}' |
apify call seemuapps/multi-board-job-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seemuapps/multi-board-job-intelligence"
        }
    }
}

```

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/uXDFOMjEgKffHIpwU/builds/byA3SVK8eLVeJwUwp/openapi.json