# Greenhouse, Lever & Ashby Jobs Scraper API (`fleet261114/ats-job-feed`) Actor

Get every open job from the Greenhouse, Lever and Ashby career boards you name in one JSON/CSV schema: title, team, locations, remote flag, salary range where published, apply link, description. $1 per 1,000 jobs. New-jobs-only mode for daily monitoring. No login, no proxy.

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

## Pricing

from $0.70 / 1,000 job returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 API: salary ranges, new jobs only

Name the companies; get **every open job** on their Greenhouse, Lever and Ashby career boards as uniform records (JSON, CSV or Excel from the dataset).

**You get, per job:** title, department and team, locations, remote flag, employment type, **salary range where the board publishes one** (Lever and Ashby by default; Greenhouse with the "Greenhouse: fetch published pay ranges" option), publish date, job and apply links, full description (text and/or HTML).
**For daily monitoring:** switch on "only jobs not returned before" and schedule the Actor: each run returns just the jobs that are new since the last one.
**Price:** $0.001 per job returned ($1 per 1,000; less on Apify's Bronze, Silver and Gold plans) plus Apify's small run-start fee. Boards that cannot be read are not charged.

It reads the boards' own **public job-board APIs** (the same feeds the companies' career pages are built from). No browser, no proxy, no login, so runs are fast (a few seconds for a few hundred jobs) and cheap. A real sample record is under "Output" below.

*Greenhouse, Lever, Ashby, SmartRecruiters, Workable and Workday are trademarks of their owners. This Actor is independent: it is not made, sponsored or endorsed by them. The names are used only to say which public job boards it reads (Greenhouse, Lever and Ashby) or does not read; company names in examples only show which public boards were read.*

### What you can use it for

- **Hiring-signal and sales-trigger lists**: which of your target accounts are hiring for which roles, every day.
- **Job boards and newsletters**: a niche board fed from a curated list of companies.
- **Job search**: watch 50 companies and get only the jobs that are new since yesterday.
- **Compensation research**: salary ranges from boards that publish them (common for US roles because of pay-transparency laws).

### Input

| Field | What it does |
|---|---|
| **Companies** (required) | One entry per company. Paste the careers-page URL, e.g. `https://job-boards.greenhouse.io/gitlab`, `https://jobs.lever.co/palantir`, `https://jobs.ashbyhq.com/ramp`, or write `greenhouse:gitlab`, `lever:palantir`, `lever-eu:<name>`, `ashby:ramp`. A bare name like `gitlab` also works: Greenhouse, Lever and Ashby are tried in that order. |
| Job title contains | Keep jobs whose title contains any of these words. |
| Location contains | Keep jobs where any location or the country contains any of these (e.g. `London`, `Germany`, `Remote`). |
| Department or team contains | Keep jobs whose department or team matches. |
| Remote jobs only | Keep only jobs marked remote. |
| Posted within the last N days | Date filter on the publish date. |
| Only jobs not returned before | For scheduled runs: return only jobs you have not received in earlier runs (per state key). |
| State key | Separate memory for separate watch lists. |
| Max jobs per company | Cap after filters. The prefilled form uses 10 so that a first test costs cents; set 0 for no cap. |
| Job description format | `text` (default), `html`, `both` or `none` (smallest output). |
| Greenhouse: fetch published pay ranges | Greenhouse shows pay only on each job's own page, so this makes one extra request per Greenhouse job returned. |

Example:

```json
{
  "companies": ["https://job-boards.greenhouse.io/gitlab", "lever:palantir", "ashby:ramp"],
  "titleKeywords": ["engineer"],
  "onlyNewJobs": true
}
```

### Output

One dataset item per job:

```json
{
  "source": "ashby",
  "companySlug": "ramp",
  "companyName": null,
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Software Engineer, Security, Cloud",
  "department": "Engineering",
  "team": "Backend",
  "location": "New York, NY (HQ)",
  "allLocations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "country": "USA",
  "isRemote": true,
  "workplaceType": "Hybrid",
  "employmentType": "FullTime",
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryInterval": "year",
  "salaryText": "$211.4K - $290.6K",
  "publishedAt": "2026-04-07T17:12:35.753Z",
  "updatedAt": null,
  "jobUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245/application",
  "descriptionText": "ABOUT RAMP\n\nRamp is building ...",
  "descriptionHtml": null,
  "scrapedAt": "2026-11-15T04:14:46.921Z"
}
```

Export as JSON, CSV, Excel or via the API like any Apify dataset. A `RUN_SUMMARY` record in the run's key-value store lists, per company, how many jobs were listed, matched your filters and were returned, plus any entries that failed and why.

Fields are `null` when the board does not provide them. What each ATS provides differs:

| Field | Greenhouse | Lever | Ashby |
|---|---|---|---|
| companyName | yes | no | no |
| department / team | department | team (department when set) | both |
| employmentType, workplaceType | no | yes | yes |
| country | no | yes | usually |
| salary | only with the pay-range option, and only if published | if published | if published |
| publishedAt | yes | yes | yes |
| updatedAt | yes | no | no |

### Pricing

Pay per result: **$0.001 per job returned** ($1.00 per 1,000 jobs), plus Apify's small run-start fee. Jobs filtered out, and jobs skipped by "only new jobs", are not charged. You can set a maximum cost per run; the Actor stops cleanly when it is reached.

### Limits and honest notes

- **Only Greenhouse, Lever and Ashby.** Companies on Workday, SmartRecruiters, iCIMS, Workable, Taleo or their own systems are not covered; such entries are reported as failed in `RUN_SUMMARY` and cost nothing.
- **You supply the companies.** This is not a search over all jobs on the internet. To find a company's board, open its careers page; the URL or the "Apply" links usually show `greenhouse.io`, `lever.co` or `ashbyhq.com`.
- Data is exactly what the company publishes on its board, at the time of the run. Some companies post one job per location, so the same role can appear several times.
- Lever asks clients to wait 1 second between requests, which this Actor respects; a company with 1,000 Lever jobs takes about 10 seconds.
- The Actor does not collect personal data: it outputs job postings only, not recruiter or hiring-manager names or contacts.
- "Only new jobs" memory lives in a key-value store named `ats-job-feed-state` in **your** Apify account. Delete it, or change the state key, to start over.

### Use it from the API, a schedule or an AI agent

**API.** Start a run and get the results in one call (replace `YOUR_APIFY_TOKEN`):

```bash
curl -X POST "https://api.apify.com/v2/actors/fleet261114~ats-job-feed/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companies": ["https://job-boards.greenhouse.io/gitlab", "lever:palantir"], "titleKeywords": ["engineer"]}'
```

This waits up to 5 minutes. For bigger jobs, start a run with `POST /v2/acts/fleet261114~ats-job-feed/runs` and read its dataset when it finishes. Apify's JavaScript and Python clients wrap the same calls.

**Schedules and integrations.** Create a task with your input and attach an Apify schedule (for example daily). Use Apify's integrations (webhooks, Make, Zapier, n8n, Google Sheets and others) to send the results onward.

**AI agents (MCP).** Add this Actor as a tool in any MCP client (Claude, Cursor and others) through Apify's hosted MCP server:

```
https://mcp.apify.com?tools=fleet261114/ats-job-feed
```

The agent sees the input schema and the field descriptions above and can call the Actor directly. Set a maximum cost per run in the call options to cap spending.

### FAQ

**Is this scraping?** No web pages are scraped. Greenhouse, Lever and Ashby publish each company's open jobs through public job-board APIs meant for building career pages; this Actor reads those.

**How do I find a company's board?** Open its careers page and look at the URL or the Apply links for `greenhouse.io`, `lever.co` or `ashbyhq.com`, then paste that URL.

**Why is the salary empty?** Companies publish salary on only some jobs. For Greenhouse, also switch on the pay-range option.

**Can I get only new jobs every day?** Yes: switch on "Only jobs not returned before" and schedule the Actor. You pay only for jobs returned.

**What does a typical run cost?** At $0.001 per job: a company with 300 open jobs costs about $0.30; a daily run in "only new" mode returns only the jobs posted since the previous run, so you pay for those alone.

### Questions and problems

Open an issue on the Actor's **Issues** tab with the run link. Reports are answered within the time Apify's Store rules require.

# Actor input Schema

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

One entry per company. Paste the careers-page URL (e.g. https://job-boards.greenhouse.io/gitlab, https://jobs.lever.co/palantir, https://jobs.ashbyhq.com/ramp), or write "greenhouse:gitlab", "lever:palantir", "lever-eu:<name>", "ashby:ramp". A bare name like "gitlab" is also accepted: then Greenhouse, Lever and Ashby are tried in that order.

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

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

## `locationKeywords` (type: `array`):

Keep only jobs where any listed location or country contains one of these (case-insensitive), e.g. "London", "Germany", "Remote".

## `departmentKeywords` (type: `array`):

Keep only jobs whose department or team contains one of these (case-insensitive).

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

Keep only jobs marked remote by the board, or with "remote" in a location.

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

Keep only jobs first published (Greenhouse, Lever, Ashby) within this many days. Empty = no date filter.

## `onlyNewJobs` (type: `boolean`):

For scheduled monitoring: return only jobs this Actor has not returned to you in earlier runs with the same state key. The first run returns everything that matches. State is kept in a named key-value store "ats-job-feed-state" in your own account.

## `stateKey` (type: `string`):

Use a different key for each independent watch list. Letters, digits, - and \_ only.

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

Cap on jobs returned per company after filters. 0 = no cap.

## `descriptionFormat` (type: `string`):

Plain text, the board's original HTML, both, or none (smallest output).

## `includeGreenhouseSalary` (type: `boolean`):

Greenhouse lists pay ranges only on each job's own page, so this makes one extra request per Greenhouse job. Lever and Ashby salaries are always included when the company publishes them.

## Actor input object example

```json
{
  "companies": [
    "https://job-boards.greenhouse.io/gitlab",
    "lever:palantir",
    "ashby:ramp"
  ],
  "titleKeywords": [],
  "locationKeywords": [],
  "departmentKeywords": [],
  "remoteOnly": false,
  "onlyNewJobs": false,
  "stateKey": "default",
  "maxJobsPerCompany": 10,
  "descriptionFormat": "text",
  "includeGreenhouseSalary": false
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "companies": [
        "https://job-boards.greenhouse.io/gitlab",
        "lever:palantir",
        "ashby:ramp"
    ],
    "maxJobsPerCompany": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("fleet261114/ats-job-feed").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": [
        "https://job-boards.greenhouse.io/gitlab",
        "lever:palantir",
        "ashby:ramp",
    ],
    "maxJobsPerCompany": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("fleet261114/ats-job-feed").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": [
    "https://job-boards.greenhouse.io/gitlab",
    "lever:palantir",
    "ashby:ramp"
  ],
  "maxJobsPerCompany": 10
}' |
apify call fleet261114/ats-job-feed --silent --output-dataset

```

## MCP server setup

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

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/II36hOjB4WmH8F5zE/builds/6X4BX3gDOfSaIYqYf/openapi.json
