# Greenhouse, Lever & Ashby Jobs Scraper (`neatfeeds/ats-jobs-greenhouse-lever-ashby`) Actor

Get every open job from company career boards on Greenhouse, Lever and Ashby in one normalized format: title, location, remote, salary, dates, apply link and description.

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

## Pricing

from $1.20 / 1,000 job postings

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

## Greenhouse, Lever & Ashby Jobs Scraper

Get **every open job** from company career pages hosted on **Greenhouse**, **Lever** and **Ashby**, in **one normalized format**. Give it company names or board URLs; get back title, location, remote/hybrid/onsite, salary range, posting date, apply link and the full description as plain text.

**Price: $1.20 per 1,000 jobs** ($0.0012 per job) + $0.00005 per run. 50 jobs cost about $0.06.

### Why this actor

- **Three platforms, one schema.** Greenhouse, Lever and Ashby jobs come out with the same fields, so you can mix companies from all three in one run and one table.
- **Salaries as numbers.** When the employer publishes pay, you get `salaryMin`, `salaryMax`, `salaryCurrency` and (where available) `salaryInterval` as separate fields, not just a text blurb.
- **Official APIs only.** It reads the public job-board APIs these platforms provide for career pages. No browser, no proxies, no login: fast, cheap and stable.
- **Minimal input.** A bare company slug like `ramp` is tried on all three platforms; you don't need to know which one a company uses.
- **Filters before billing.** Title keywords, locations, remote-only and posting age are applied before results are saved, so you only pay for jobs you keep.

### What you can use it for

- Track hiring at competitors, customers or prospects (sales triggers, market research).
- Build job boards and newsletters for a niche (e.g. remote engineering jobs at AI startups).
- Feed AI agents and recruiting tools with fresh, structured job data.
- Salary benchmarking: Ashby and many Greenhouse boards publish pay ranges.

### Input

Only `companies` is required.

| Field | What it does |
|---|---|
| `companies` (required) | Board URLs (`https://boards.greenhouse.io/airbnb`, `https://jobs.lever.co/palantir`, `https://jobs.ashbyhq.com/ramp`, EU Lever boards too), prefixed slugs (`greenhouse:airbnb`, `lever:palantir`, `ashby:ramp`) or a bare slug (`airbnb`), which is tried on all three platforms. |
| `titleKeywords` | Keep jobs whose title contains any of these words. |
| `locations` | Keep jobs whose location contains any of these strings (`London`, `Remote`, `Germany`). |
| `remoteOnly` | Keep only remote jobs. |
| `postedWithinDays` | Keep only jobs published in the last N days. |
| `includeDescription` | Add the full description as plain text (default on). |
| `maxResultsPerCompany` / `maxResults` | Limits per company and in total (default: no per-company limit, 1,000 in total). |

Example:

```json
{
  "companies": ["greenhouse:airbnb", "https://jobs.lever.co/palantir", "ramp"],
  "titleKeywords": ["engineer"],
  "locations": ["remote", "london"],
  "maxResultsPerCompany": 50
}
```

### Output (one item per job)

```json
{
  "platform": "ashby",
  "company": "ramp",
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Security Engineer, Cloud",
  "department": "Engineering",
  "team": "Backend",
  "location": "New York, NY (HQ)",
  "allLocations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "workplaceType": "hybrid",
  "isRemote": true,
  "employmentType": "FullTime",
  "postedAt": "2026-04-07T17:12:35.753Z",
  "url": "https://jobs.ashbyhq.com/ramp/34413f8d-…",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-…/application",
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryInterval": "1 YEAR",
  "salaryText": "$211.4K - $290.6K",
  "description": "ABOUT RAMP …",
  "scrapedAt": "2026-10-19T19:40:48.919Z"
}
```

| Field | Meaning |
|---|---|
| `platform`, `company`, `jobId` | Source platform (`greenhouse`, `lever`, `ashby`), board slug and the platform's job ID. |
| `title`, `department`, `team` | Job title and the employer's own grouping. |
| `location`, `allLocations` | Main location and every listed location. |
| `workplaceType`, `isRemote` | `remote`, `hybrid` or `onsite` when the board says so; `isRemote` is true for remote jobs. |
| `employmentType` | E.g. `FullTime` on Ashby, the commitment on Lever (not published by Greenhouse). |
| `postedAt` | First publication date, ISO 8601. |
| `url`, `applyUrl` | Job page and application form. |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval`, `salaryText` | Pay range as numbers plus the original text, when the employer publishes it. |
| `description` | Full description as plain text (only with `includeDescription`). |
| `scrapedAt` | When the job was collected. |

### Pricing

Pay per event, no subscription:

| Event | Price |
|---|---|
| Job returned | $0.0012 ($1.20 per 1,000) |
| Run start | $0.00005 |

Examples:

- 50 jobs from three companies: 50 × $0.0012 + $0.00005 ≈ **$0.06**
- One large board with 600 open jobs: **$0.72**
- 20 companies checked daily with `postedWithinDays: 1`, about 40 matching jobs per day: about **$1.44 per month**

### FAQ

**How do I cap what a run costs?**
Set a maximum cost per run in the run options (or with `maxTotalChargeUsd` via the API). The actor stops cleanly when the limit is reached and keeps every result collected so far. `maxResults` caps the number of jobs as well.

**Why are some fields `null`?**
Each platform publishes different data. Fields a platform does not provide are `null`: Greenhouse has no employment type, Lever rarely publishes salaries, and only some employers publish pay at all. A company that does not use Greenhouse, Lever or Ashby is reported in the log and skipped; the run continues with the others.

**Can I call it from code, an AI agent or an automation tool?**
Yes. Run it through the [Apify API](https://docs.apify.com/api/v2) and get the dataset in the same call:

```bash
curl -X POST "https://api.apify.com/v2/acts/Neatfeeds~ats-jobs-greenhouse-lever-ashby/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["ashby:ramp"], "titleKeywords": ["engineer"], "maxResults": 20}'
```

It also works with Apify schedules, webhooks and integrations such as Make, Zapier and n8n, and with AI agents through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp).

### Notes

- Data comes from public career-page APIs published by the employers themselves.

# Actor input Schema

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

One entry per company. Accepted: a board URL (https://boards.greenhouse.io/airbnb, https://jobs.lever.co/palantir, https://jobs.ashbyhq.com/ramp), a prefixed slug (greenhouse:airbnb, lever:palantir, ashby:ramp) or a bare slug (airbnb), which is tried on all three platforms.

## `titleKeywords` (type: `array`):

Keep only jobs whose title contains at least one of these words (case-insensitive). Empty = all jobs.

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

Keep only jobs whose location contains one of these strings, e.g. "London", "Remote", "Germany". Empty = all locations.

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

Keep only jobs marked as remote.

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

Keep only jobs published in the last N days. 0 = no limit.

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

Add the full job description as plain text. Turn off for smaller, faster results.

## `maxResultsPerCompany` (type: `integer`):

Keep at most this many jobs from each company (after filters). 0 = no per-company limit.

## `maxResults` (type: `integer`):

Stop after this many jobs in total (each job is one billed result).

## Actor input object example

```json
{
  "companies": [
    "greenhouse:airbnb",
    "lever:palantir",
    "ashby:ramp"
  ],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescription": true,
  "maxResultsPerCompany": 20,
  "maxResults": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset items in the "Jobs" view: company, title, location, workplaceType, salaryText, postedAt, platform, url.

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

Every dataset item with all fields.

# 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:airbnb",
        "lever:palantir",
        "ashby:ramp"
    ],
    "maxResultsPerCompany": 20,
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("neatfeeds/ats-jobs-greenhouse-lever-ashby").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:airbnb",
        "lever:palantir",
        "ashby:ramp",
    ],
    "maxResultsPerCompany": 20,
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("neatfeeds/ats-jobs-greenhouse-lever-ashby").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": [
    "greenhouse:airbnb",
    "lever:palantir",
    "ashby:ramp"
  ],
  "maxResultsPerCompany": 20,
  "maxResults": 50
}' |
apify call neatfeeds/ats-jobs-greenhouse-lever-ashby --silent --output-dataset

```

## MCP server setup

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

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/YHH3orC3EDVNOXqAS/builds/QCjjpeG9ykZrn75t1/openapi.json