# Multi-ATS Job Postings & Hiring-Signal Scraper (`ax_dev/multi-ats-hiring-signals`) Actor

Scrape jobs from Greenhouse, Lever, Ashby & SmartRecruiters in one unified schema, plus per-company hiring signals (departments, locations, remote %, hiring velocity). Built for sales intelligence, recruiting, market research & AI agents. No API key, near-zero maintenance.

- **URL**: https://apify.com/ax\_dev/multi-ats-hiring-signals.md
- **Developed by:** [Alexandr Maier](https://apify.com/ax_dev) (community)
- **Categories:** Jobs, Lead generation, AI
- **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 and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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-ATS Job Postings & Hiring-Signal Scraper

Pull job postings from **Greenhouse, Lever, Ashby, and SmartRecruiters** into **one unified schema**, and get **hiring signals** per company: department breakdown, locations, remote %, and how fast they're hiring.

Most job scrapers cover a single ATS and just dump raw postings. This one **normalizes four ATS platforms into one format** and adds the analytics layer that sales-intelligence, recruiting, and market-research teams actually pay for.

Data comes from each vendor's **official public JSON API** — no API key, no login, no proxy, no anti-bot. That makes it fast and **near-zero maintenance**: these endpoints rarely change.

### What you get

**Per job** (unified across all four ATS):

```json
{
  "ats": "ashby",
  "company": "ramp",
  "id": "03e2d4e1-...",
  "title": "Technical Consultant, Mid-Market",
  "department": "Sales",
  "team": "Solutions Consulting",
  "location": "Remote (US)",
  "remote": true,
  "employmentType": "FullTime",
  "publishedAt": "2026-07-07T20:47:09.753Z",
  "url": "https://jobs.ashbyhq.com/ramp/03e2d4e1-..."
}
```

**Per company** (hiring signal summary):

```json
{
  "type": "company_signal",
  "company": "spotify",
  "ats": "lever",
  "totalOpenRoles": 110,
  "remoteRoles": 30,
  "remoteShare": 27,
  "rolesPostedLast30Days": 32,
  "newestPostingAt": "2026-07-09T...",
  "topDepartments": [{ "name": "Engineering", "count": 39 }, ...],
  "topLocations": [{ "name": "London", "count": 14 }, ...]
}
```

### How to find a company's token

The token is the identifier in a company's careers URL:

| ATS | Careers URL example | Token | Input |
|---|---|---|---|
| Greenhouse | `boards.greenhouse.io/stripe` | `stripe` | `greenhouse:stripe` |
| Lever | `jobs.lever.co/spotify` | `spotify` | `lever:spotify` |
| Ashby | `jobs.ashbyhq.com/ramp` | `ramp` | `ashby:ramp` |
| SmartRecruiters | `jobs.smartrecruiters.com/Visa` | `Visa` | `smartrecruiters:Visa` |

### Input

| Field | Type | Description |
|---|---|---|
| `companies` | array **(required)** | `"<ats>:<company>"` entries, e.g. `"greenhouse:stripe"` |
| `keywords` | array | Keep roles whose title (or body, if included) matches |
| `locations` | array | Keep roles whose location contains a substring |
| `departments` | array | Keep roles in matching departments |
| `remoteOnly` | boolean | Remote-flagged roles only |
| `postedWithinDays` | integer | Only roles posted in the last N days (hiring-velocity monitoring) |
| `includeDescription` | boolean | Include full role text (bigger output) |
| `signalsOnly` | boolean | Output only the per-company summary, no individual rows |

#### Example: monitor competitors' engineering hiring, last 30 days

```json
{
  "companies": ["greenhouse:stripe", "lever:spotify", "ashby:ramp"],
  "departments": ["Engineering"],
  "postedWithinDays": 30
}
```

### Use cases

- **Sales intelligence** — a company hiring 40 salespeople signals budget and expansion. Feed signals into your CRM.
- **Competitive intel** — track which departments and locations competitors are growing.
- **Recruiting / talent** — a fresh, deduplicated feed of open roles across your target companies.
- **AI agents (MCP)** — "What is company X hiring for right now?" is one clean tool call with flat JSON back.
- **Market research** — hiring velocity as a leading indicator across a sector.

### Pricing (pay-per-event)

| Event | Price |
|---|---|
| Actor start | $0.005 |
| Company processed (with signals) | $0.01 |
| Job row saved | $0.00015 |

Scanning 10 companies with ~2,000 total roles ≈ $0.005 + $0.10 + $0.30 = **~$0.40**. Use `signalsOnly` to pay only per company when you just need the aggregates.

### Honest notes

- Covers companies hosted on these four ATS platforms. It does not scrape LinkedIn, Indeed, or company career pages built on other systems.
- Uses official public endpoints only. No login, no personal data, no anti-bot evasion.
- `includeDescription` isn't available for SmartRecruiters in this version (would need a per-role call).
- All source-specific logic lives in `src/ats.js` — the only file to touch if an ATS ever changes its format. Adding a new ATS = one function.

# Actor input Schema

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

List of companies in the form "<ats>:<company>". Supported ATS: greenhouse, lever, ashby, smartrecruiters. The <company> is the token in the careers-page URL (e.g. boards.greenhouse.io/stripe -> stripe).

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

Keep only roles whose title (or description, if included) contains a keyword. Case-insensitive. Empty = all roles.

## `locations` (type: `array`):

Keep only roles whose location contains one of these substrings (e.g. "London", "US", "Berlin").

## `departments` (type: `array`):

Keep only roles in matching departments (e.g. "Engineering", "Sales").

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

Keep only roles flagged remote.

## `postedWithinDays` (type: `integer`):

Keep only roles published within the last N days (great for hiring-velocity monitoring). Empty = no cutoff.

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

Include each role's full text (larger output, enables keyword search inside the body). Not available for SmartRecruiters in this version.

## `signalsOnly` (type: `boolean`):

Output only the per-company hiring-signal summary (departments, locations, remote %, velocity), not individual job rows.

## `useProxy` (type: `boolean`):

Route requests through Apify Proxy. Rarely needed — these are official APIs.

## `proxyConfiguration` (type: `object`):

Advanced proxy settings (overrides 'Use Apify Proxy'). Rarely needed — these are official APIs.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:gitlab",
    "lever:spotify"
  ],
  "keywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "includeDescription": false,
  "signalsOnly": false,
  "useProxy": false
}
```

# 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": [
        "greenhouse:stripe",
        "lever:spotify",
        "ashby:ramp",
        "smartrecruiters:Visa"
    ],
    "keywords": [],
    "locations": [],
    "departments": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("ax_dev/multi-ats-hiring-signals").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": [
        "greenhouse:stripe",
        "lever:spotify",
        "ashby:ramp",
        "smartrecruiters:Visa",
    ],
    "keywords": [],
    "locations": [],
    "departments": [],
}

# Run the Actor and wait for it to finish
run = client.actor("ax_dev/multi-ats-hiring-signals").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 '{
  "companies": [
    "greenhouse:stripe",
    "lever:spotify",
    "ashby:ramp",
    "smartrecruiters:Visa"
  ],
  "keywords": [],
  "locations": [],
  "departments": []
}' |
apify call ax_dev/multi-ats-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ax_dev/multi-ats-hiring-signals",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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