# Job Postings Aggregator (`zinin/job-postings-aggregator`) Actor

Pull every open role from a company's public applicant-tracking system (Greenhouse, Lever, Ashby) and normalize it into one row per posting: title, location, department, URL, posted date. No login, no scraping, no proxies.

- **URL**: https://apify.com/zinin/job-postings-aggregator.md
- **Developed by:** [Tim Zinin](https://apify.com/zinin) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 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

## Job Postings Aggregator — Greenhouse, Lever & Ashby

Greenhouse, Lever and Ashby are the three most widely used applicant-tracking systems, and each one already publishes a public JSON feed of a company's open roles. This Actor pulls every role from any of the three and normalizes it into one row per posting: title, location, department, posting date and a direct apply link — no browser, no proxies, no login.

### What you get

- **Three ATS in one Actor.** Greenhouse, Lever and Ashby — the same `provider:company` syntax across all three, so a mixed-vendor portfolio is a single run.
- **Every open role, normalized.** Title, location, department, posting date and direct apply URL, in the same shape regardless of which ATS the company uses.
- **No login, no proxies, no browser.** Each is a public keyless JSON API — the same feed that powers the company's own careers-page widget.
- **Built for lists.** Concurrency up to 20, up to 100 companies per run, so tracking a whole sector's hiring is a single run.
- Runs on Apify: schedule it, monitor it, call it from the API or the MCP server, export to JSON, CSV or Excel, or push results straight into your own pipeline.

### How to run it

1. Click **Try for free** — no card needed on the free plan.
2. Paste `provider:company` tokens into **Companies (ATS tokens)**, one per line — e.g. `greenhouse:stripe`, `lever:spotify`, `ashby:ramp`. `company` is the board's own slug, the part in the careers URL.
3. Press **Start**. Results appear in the dataset — read them in the UI, pull them from the API, or have a webhook push them onward.

### Pricing

Pay-per-event: **$0.005 per run start + $0.002 per role found**. No monthly seat, no minimum. 100 roles cost about **$0.21**; 1,000 roles about **$2.01**.

A company with no public board on the given provider is still logged with `found: false` and the reason — and it is **not** charged for. You pay for roles actually delivered, not for attempts.

### Input

| Field | Required | What it does |
|---|---|---|
| `items` | yes | One entry per company, format `provider:company`. Provider is `greenhouse`, `lever` or `ashby`; company is the board's own slug (the part in the careers URL, e.g. `jobs.lever.co/spotify` → `spotify`). Up to 100 per run. |
| `maxConcurrency` | no | How many companies to check in parallel, 1–20 (default 5). |

```json
{
    "items": [
        "greenhouse:stripe",
        "lever:spotify",
        "ashby:ramp"
    ]
}
```

### Output

One dataset row per open role found. This is a real row from a real run:

```json
{
    "input": "greenhouse:stripe",
    "found": true,
    "provider": "greenhouse",
    "company": "stripe",
    "jobId": "7954688",
    "title": "Account Executive, AI Sales (Grower)",
    "location": "San Francisco, CA",
    "department": null,
    "url": "https://stripe.com/jobs/search?gh_jid=7954688",
    "postedAt": "2026-06-02T12:58:57.000Z",
    "scrapedAt": "2026-07-26T13:19:32.859Z"
}
```

| Field | What it means |
|---|---|
| `input` | The `provider:company` token you passed |
| `found` | Whether the board returned at least one open role |
| `provider` | `greenhouse`, `lever` or `ashby` |
| `company` | The board's company slug |
| `jobId` | The ATS's internal job ID |
| `title` | Role title |
| `location` | Office/remote location as listed |
| `department` | Team/department as listed, when the board publishes one |
| `url` | Direct apply/posting URL |
| `postedAt` | ISO timestamp of when the role was first published |
| `scrapedAt` | When this Actor fetched the row |

#### Need the rest of the picture?

These run on the same account, take the same shape of input and bill the same way, so they slot into an existing pipeline without new plumbing.

| Actor | What it does |
|---|---|
| [Company Hiring Radar](https://apify.com/zinin/company-hiring-radar) | Pull every open role a company is hiring for from its public job board (Greenhouse, Lever, Ashby) and turn… |
| [Computrabajo LatAm Jobs Scraper](https://apify.com/zinin/computrabajo-jobs) | Search Computrabajo (Mexico, Colombia, Chile, Argentina, Peru) by keyword and get public job listings:… |
| [Layoff Tracker](https://apify.com/zinin/layoff-tracker) | Track recent tech layoffs by company name or sector (e.g |
| [AI Answer Change Alert](https://apify.com/zinin/ai-answer-change-alert) | Track whether an AI assistant's answer to a query you care about changed since last time — new sources… |
| [AI Crawler Access Checker](https://apify.com/zinin/ai-crawler-access-checker) | Check which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended & more) can access your website |

### FAQ

**Does it need an API key / login?** No — Greenhouse, Lever and Ashby all publish their job boards as public keyless JSON.

**How fresh is the data?** Live at request time — the same feed that powers the company's own careers-page widget.

**What if a company has no public board on a given provider?** The row says so (`found: false`) instead of failing the whole run, and it's never billed.

**Can I call it from an AI agent?** Yes — standard Apify Actor, callable from the Apify API, the SDK, or the Apify MCP server.

**What this is NOT.** It does not cover ATS platforms beyond Greenhouse, Lever and Ashby (Workday, SmartRecruiters and others aren't supported), and it does not read the full job description text.

Found a wrong result, or need a check we don't run? Open an issue on this Actor's page.

***

Built by [zinin](https://apify.com/zinin). Questions? Telegram [@timzinin](https://t.me/timzinin).

# Actor input Schema

## `items` (type: `array`):

One entry per company, format `provider:company`. Provider is `greenhouse`, `lever` or `ashby`; company is the board's own slug (the part in the careers URL, e.g. `jobs.lever.co/spotify` -> `spotify`). Examples: `greenhouse:stripe`, `lever:spotify`, `ashby:ramp`.

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

How many companies to check in parallel.

## Actor input object example

```json
{
  "items": [
    "greenhouse:stripe",
    "lever:spotify",
    "ashby:ramp"
  ],
  "maxConcurrency": 5
}
```

# 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 = {
    "items": [
        "greenhouse:stripe",
        "lever:spotify",
        "ashby:ramp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinin/job-postings-aggregator").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 = { "items": [
        "greenhouse:stripe",
        "lever:spotify",
        "ashby:ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("zinin/job-postings-aggregator").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "items": [
    "greenhouse:stripe",
    "lever:spotify",
    "ashby:ramp"
  ]
}' |
apify call zinin/job-postings-aggregator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=zinin/job-postings-aggregator",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/ATELanjFiayoHJkUw/builds/arJZHr0uKyMVF7xQ4/openapi.json