# Company Jobs from Greenhouse, Lever & Ashby — Structured Salary (`forgekit-labs/ats-jobs`) Actor

Give a list of company domains or names; get their open jobs straight from their public Greenhouse, Lever or Ashby job boards, normalized to one schema with structured salary where the employer publishes it. No job descriptions, no guessing.

- **URL**: https://apify.com/forgekit-labs/ats-jobs.md
- **Developed by:** [Zeb Jungeberg](https://apify.com/forgekit-labs) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Company Jobs from Greenhouse, Lever & Ashby — Structured Salary

Give a list of companies. Get their open jobs straight from their own public job boards on **Greenhouse**, **Lever**, or **Ashby**, normalized into one clean schema, with **structured salary ranges wherever the employer publishes them**.

The data is read directly from the board each employer maintains at the time of your run — not from an aggregator.

### What you provide

A list of up to 50 companies per run. Each entry can be:

- a job-board URL — **the most reliable input**: `https://boards.greenhouse.io/airbnb`, `https://jobs.lever.co/palantir`, `https://jobs.ashbyhq.com/openai`
- a domain: `stripe.com`
- a company name: `Ramp`

For domains and names, the Actor tries the exact company name as a board ID on each platform and stops at the first board that exists. Every row tells you how the match was made (see `match` below) so you can check it. Greenhouse boards report their own company name, and a guessed Greenhouse board is only accepted when that name matches yours.

Optional filters: remote only, published-salary only, location contains.

### What this returns

One row per open job:

| Field | Notes |
|---|---|
| `company` | As you entered it |
| `title` | As written by the employer |
| `location` | As written on the board |
| `remote` | `true` / `false` only when the board says so. For Greenhouse, `true` only when the location text explicitly says remote. `null` means unknown — never guessed. |
| `salary_min`, `salary_max`, `salary_currency` | Only from the platform's **structured** salary fields — never extracted from description text. `null` when the employer published none, or published several ranges (e.g. per country) with no single answer. |
| `salary_interval` | `year` / `month` / `hour` etc. when the platform supplies it. Greenhouse does not, so it is always `null` there. |
| `posted_at` | Greenhouse/Ashby: first-published time. Lever: the posting's creation time. |
| `apply_url` | The job's application page on the employer's job board |
| `source_ats` | `greenhouse`, `lever`, or `ashby` |
| `board` | The exact board read, e.g. `greenhouse:stripe` |
| `match` | `board_url` (you gave the board URL), `name_verified` (guessed and confirmed by the board's own company name), or `slug_guess` (guessed from your input; Lever and Ashby don't report a company name, so check `board`) |
| `retrieved_at` | When this run read the board |

#### Companies that don't produce jobs

Each gets one row explaining why, and **none of these rows is charged**:

| `record_type` | Meaning |
|---|---|
| `board_not_found` | No board found on any of the three platforms; `sources_checked` lists what was tried |
| `board_empty` | The board exists but has no open jobs right now |
| `name_mismatch` | A board with that ID exists but belongs to a different company (`board_company`) — supply the board URL instead |
| `no_matching_jobs` | Jobs exist, but none pass your filters (`jobs_before_filters`) |
| `duplicate_board` | Another entry in your list already resolved to the same board, so its jobs aren't returned (or charged) twice |
| `source_error` | The job board could not be reached reliably; this is never reported as "no jobs" |
| `unsupported_input` | e.g. EU-hosted boards (`jobs.eu.lever.co`, `boards.eu.greenhouse.io`), not supported yet |

### What this deliberately does not return

- **No job descriptions.** Description text belongs to the employer; follow `apply_url` to read it.
- **No recruiter or hiring-manager fields.** (Job titles are passed through exactly as the employer wrote them.)
- **No unlisted postings.** Ashby jobs an employer has marked unlisted are skipped.
- **No other job platforms.** Workday, iCIMS, LinkedIn, Indeed, etc. are not covered.

### Pricing

Pay per result: a small fee per job row returned, plus Apify's standard per-run start fee. Rows explaining why a company produced no jobs are not charged.

### Source and affiliation

This Actor reads the public, unauthenticated job-board endpoints that Greenhouse, Lever and Ashby provide for employers' careers pages. It is not affiliated with, endorsed by, or sponsored by Greenhouse, Lever, Ashby, or any employer listed. Job data is provided as published by each employer; verify details on the application page before acting on them.

Employers or platforms with questions or removal requests: zeb@forgekits.build.

Built and operated by ForgeKit.

# Actor input Schema

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

Up to 50 companies per run. Each entry can be a domain (stripe.com), a company name (Ramp), or a job-board URL (https://jobs.lever.co/palantir, https://boards.greenhouse.io/airbnb, https://jobs.ashbyhq.com/openai). A board URL is the most reliable input.

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

Only return jobs the board explicitly marks as remote. Jobs with unknown remote status are excluded.

## `hasSalaryOnly` (type: `boolean`):

Only return jobs where the employer published a structured salary range.

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

Case-insensitive text the job location must contain, e.g. "New York" or "Remote".

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.lever.co/palantir"
  ],
  "remoteOnly": false,
  "hasSalaryOnly": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

One row per open job. Companies that produced no jobs appear as rows with record_type board_not_found, board_empty, name_mismatch, no_matching_jobs, duplicate_board, source_error, or unsupported_input (never charged).

## `runSummary` (type: `string`):

Counts per outcome and jobs returned for this run.

# 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": [
        "stripe.com",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.lever.co/palantir"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("forgekit-labs/ats-jobs").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": [
        "stripe.com",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.lever.co/palantir",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("forgekit-labs/ats-jobs").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 '{
  "companies": [
    "stripe.com",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.lever.co/palantir"
  ]
}' |
apify call forgekit-labs/ats-jobs --silent --output-dataset

```

## MCP server setup

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

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/iSFsKAUkNDUCjcHWE/builds/gSkItXpEoFO6g0a9h/openapi.json