# Greenhouse, Lever & Ashby Jobs Scraper (`beakdo/ats-career-signal-sniper`) Actor

Scrapes open job postings, salary ranges, remote flags, and tech stack keywords directly from Greenhouse, Lever, and Ashby boards. Accepts mixed company slugs in one run and outputs flat JSON or CSV for Clay and n8n.

- **URL**: https://apify.com/beakdo/ats-career-signal-sniper.md
- **Developed by:** [Kim SungHyun](https://apify.com/beakdo) (community)
- **Categories:** Lead generation, Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.90 / 1,000 greenhouse, lever & ashby jobs scraper records

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

Pulls live job listings straight from public Greenhouse, Lever, and Ashby career boards without spinning up a headless browser. Give it a list of company board slugs (`vercel`, `linear`, `cloudflare`) and it resolves whichever of the three ATS platforms each company uses, normalizes the postings into a single schema, and tags mentioned tools and compensation ranges.

I built this mainly for outbound lists in Clay and n8n where you have a column of SaaS company slugs and want to see who is actively hiring security engineers, data engineers, or enterprise AEs before sending outreach.

### How ATS auto-detection works

When `atsProvider` is set to `"auto"`, each slug is checked against the public JSON endpoints in order:

1. Greenhouse (`boards-api.greenhouse.io/v1/boards/{slug}/jobs?content=true`)
2. Ashby (`api.ashbyhq.com/posting-api/job-board/{slug}?includeCompensation=true`)
3. Lever (`api.lever.co/v0/postings/{slug}?mode=json`)

If you already know every slug in your batch belongs to one provider, set `atsProvider` to `"greenhouse"`, `"ashby"`, or `"lever"` to save the extra lookup requests. Dead slugs or 404 boards return zero rows and cost nothing.

### Input example

```json
{
  "companySlugs": ["vercel", "linear", "cloudflare"],
  "atsProvider": "auto",
  "departmentFilter": "",
  "maxJobsPerCompany": 20
}
```

Set `departmentFilter` to a plain substring like `"security"`, `"data"`, or `"sales"` if you only want roles matching a specific team. Because billing is per extracted row, filtering inside the actor is cheaper than pulling all 300 roles at a big company and filtering downstream.

### Output sample

```json
{
  "company_slug": "vercel",
  "ats_platform": "greenhouse",
  "job_id": "5419284004",
  "job_title": "Staff Security Engineer",
  "department_raw": "Security",
  "department_category": "Security_Compliance",
  "location": "Remote - US",
  "is_remote": true,
  "compensation_summary": "$196,000 - $294,000",
  "tech_stack_signals": ["AWS", "Go", "Kubernetes", "Next.js", "SOC2", "TypeScript"],
  "company_open_roles_total": 48,
  "hiring_intent_score": 0.89,
  "job_url": "https://job-boards.greenhouse.io/vercel/jobs/5419284004",
  "published_at": "2026-11-10T18:22:11-05:00",
  "description_excerpt": "We are looking for a Staff Security Engineer to own cloud infrastructure security..."
}
```

### Pricing and edge cases

Billing uses Pay-Per-Event at `$1.90` per 1,000 extracted job rows (`$0.0019` per `job-signal-extracted` event), with no start fee.

A few practical things worth knowing before running big batches:

- A company's ATS board slug does not always match its domain name (for instance, `getdbt` vs `dbtlabs`). If a slug 404s across all three providers, check the URL of their careers page once.
- Greenhouse embeds raw HTML entities inside its JSON `content` field; the parser strips tags before scanning for the 35+ stack keywords (`Snowflake`, `Databricks`, `dbt`, `Kubernetes`, `Terraform`, `Salesforce`, `HubSpot`, `SOC2`, `HIPAA`, etc.).
- Personal webmail addresses (`gmail.com`, `yahoo.com`, `naver.com`, etc.) and national ID patterns found inside job text are automatically redacted so downstream CRM imports stay clean.

# Actor input Schema

## `companySlugs` (type: `array`):

List of company ATS board slugs (e.g. 'vercel', 'linear', 'cloudflare', 'datadog').

## `atsProvider` (type: `string`):

Choose a specific ATS or 'auto' to automatically probe Greenhouse, Ashby, and Lever.

## `departmentFilter` (type: `string`):

Optional case-insensitive filter for job title or department (e.g. 'Engineering', 'Sales', 'Security', 'Data').

## `maxJobsPerCompany` (type: `integer`):

Maximum job signal records to emit per company board.

## Actor input object example

```json
{
  "companySlugs": [
    "vercel",
    "linear"
  ],
  "atsProvider": "auto",
  "departmentFilter": "",
  "maxJobsPerCompany": 15
}
```

# Actor output Schema

## `signals` (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 = {
    "companySlugs": [
        "vercel",
        "linear"
    ],
    "atsProvider": "auto",
    "maxJobsPerCompany": 15
};

// Run the Actor and wait for it to finish
const run = await client.actor("beakdo/ats-career-signal-sniper").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 = {
    "companySlugs": [
        "vercel",
        "linear",
    ],
    "atsProvider": "auto",
    "maxJobsPerCompany": 15,
}

# Run the Actor and wait for it to finish
run = client.actor("beakdo/ats-career-signal-sniper").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 '{
  "companySlugs": [
    "vercel",
    "linear"
  ],
  "atsProvider": "auto",
  "maxJobsPerCompany": 15
}' |
apify call beakdo/ats-career-signal-sniper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,beakdo/ats-career-signal-sniper"
        }
    }
}
```

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/I0avrVKxJ9cabSZYb/builds/TXtzLAXHvWlnwiVGm/openapi.json
