# Greenhouse, Lever & Ashby Jobs Scraper + Monitor (`mayevil/greenhouse-lever-jobs-scraper`) Actor

Scrape open jobs from company career sites on Greenhouse, Lever, Ashby, Workable and Recruitee via their official public APIs. Track a watchlist of companies and get only new or closed jobs on each run (hiring signals). Salary, remote and job type normalized. No proxies.

- **URL**: https://apify.com/mayevil/greenhouse-lever-jobs-scraper.md
- **Developed by:** [David Tu](https://apify.com/mayevil) (community)
- **Categories:** Jobs, Lead generation, Automation
- **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. 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

Scrape **every open job from a company's own career site** and see **which roles are new since your last run**. Paste a list of companies or careers-page URLs and get clean, normalized job data in one dataset, whichever applicant tracking system (ATS) each company uses. Each job comes with **salary ranges, remote/hybrid flags, departments and employment type**.

Works with **Greenhouse, Lever, Ashby, Workable and Recruitee**. It uses their **official public job-board APIs**, the same feeds that power companies' careers pages. That makes it fast and cheap, and it needs **no proxies, no browser and no login**.

### What does this jobs scraper do?

- 🔎 **One run, five ATS platforms.** Greenhouse, Lever (global and EU), Ashby, Workable and Recruitee, all in one output format.
- 🧭 **Automatic ATS detection.** Just type `ramp` or `huggingface` and the Actor finds the board. Careers-page URLs and `ats:slug` shorthand work too.
- 🆕 **Hiring-signal monitor.** Remembers what it has seen and outputs only **new jobs** (and optionally **closed jobs**) since the previous run. Schedule it daily and pay only for changes.
- 💰 **Salary data** (min / max / currency / interval) whenever the employer publishes it: Ashby compensation, Lever salary ranges, Recruitee salary, and Greenhouse pay-transparency ranges.
- 🧹 **Normalized fields.** `workplaceType` (remote / hybrid / onsite), `employmentType` (FULL_TIME, CONTRACT, INTERN…), ISO dates, and plain-text or HTML descriptions (ready for LLMs).
- 🎯 **Filters.** Title keywords (include and exclude), location keywords, remote only, posted within N days, max jobs per company and in total.
- 🏋️ **Handles big boards.** Tested on boards with 2,500+ open jobs (e.g. SpaceX, Anduril) at 256 MB memory.
- 🛡️ **Polite and robust.** Per-host rate limiting (Lever at most 1 request/second, as its robots.txt asks), retries with backoff on 429/5xx, and a per-company `RUN_SUMMARY` (ok / not_found / error / skipped).

### Who uses it?

#### Recruiters and staffing agencies

Track the career pages of your target clients and get a daily list of **new openings** in your niche (e.g. "Data Engineer", "Account Executive") before they reach the job boards.

#### Sales intelligence and hiring signals

A company that suddenly posts 10 security roles is shopping for security tools. Feed **new-job events** from hundreds of target accounts into your CRM, Clay, or outreach sequences, and time your pitch to their hiring.

#### Job boards and aggregators

Pull **fresh, structured jobs straight from employers' career sites**, with apply links, salaries and remote flags, to power a niche job board or newsletter.

#### Market research, investors and HR analytics

Measure **hiring velocity** by department and location across competitors or a portfolio, follow new office openings, and benchmark **published pay ranges**.

### How to scrape jobs from Greenhouse, Lever and Ashby

1. Add companies under **Companies**, one per line, in any of these formats:

| Format | Example |
|---|---|
| Greenhouse board URL | `https://boards.greenhouse.io/airbnb`, `https://job-boards.greenhouse.io/twilio` |
| Lever board URL | `https://jobs.lever.co/palantir`, `https://jobs.eu.lever.co/<company>` |
| Ashby board URL | `https://jobs.ashbyhq.com/ramp` |
| Workable board URL | `https://apply.workable.com/huggingface` |
| Recruitee board URL | `https://<company>.recruitee.com` |
| Shorthand | `greenhouse:airbnb`, `lever:palantir`, `lever-eu:<slug>`, `ashby:ramp`, `workable:huggingface`, `recruitee:<slug>` |
| Bare slug (auto-detect) | `ramp` |

2. Optionally set filters, or turn on **Monitor mode**.
3. Click **Start**, then download the results as JSON, CSV, Excel or HTML, or fetch them via the Apify API, webhooks or integrations (Make, Zapier, n8n, Google Sheets…).

> **Finding a company's slug:** open its careers page and click any job. The URL shows the ATS and slug, e.g. `jobs.lever.co/<slug>/...` or `boards.greenhouse.io/<slug>/jobs/...`.

### Input examples

**Full export of a few companies:**

```json
{
  "companies": ["https://jobs.ashbyhq.com/ramp", "greenhouse:airbnb", "lever:palantir", "huggingface"],
  "includeDescription": true
}
```

**Daily hiring-signal monitor** (only new engineering jobs in London or remote, plus closed ones):

```json
{
  "companies": ["stripe", "figma", "notion", "openai", "lever:spotify"],
  "titleKeywords": ["engineer", "developer"],
  "locationKeywords": ["London", "Remote"],
  "monitorMode": true,
  "monitorStateKey": "eng-watchlist",
  "outputClosedJobs": true,
  "includeDescription": false
}
```

**Cheap sample: max 20 jobs per company, salaries included:**

```json
{
  "companies": ["greenhouse:airbnb", "greenhouse:reddit", "ashby:perplexity"],
  "maxJobsPerCompany": 20,
  "includeGreenhouseSalary": true
}
```

### Output example

Each dataset item is one job. A real example (description shortened):

```json
{
  "jobKey": "ashby:ramp:34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "status": "active",
  "ats": "ashby",
  "companySlug": "ramp",
  "companyName": null,
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Security Engineer, Cloud",
  "department": "Engineering",
  "team": "Backend",
  "location": "New York, NY (HQ)",
  "locations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "country": "USA",
  "workplaceType": "hybrid",
  "isRemote": true,
  "employmentType": "FULL_TIME",
  "employmentTypeRaw": "FullTime",
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryInterval": "YEAR",
  "salaryText": "$211.4K - $290.6K",
  "postedAt": "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",
  "description": "ABOUT RAMP\n\nRamp is building the smart infrastructure for finance teams...",
  "sourceApiUrl": "https://api.ashbyhq.com/posting-api/job-board/ramp?includeCompensation=true",
  "scrapedAt": "2026-10-07T07:57:42.997Z"
}
```

| Field | Notes |
|---|---|
| `status` | `active` in normal runs. In monitor mode: `new` (first seen in this run) or `closed` (removed since the last run). |
| `workplaceType` / `isRemote` | From the ATS. Greenhouse has no structured flag, so it is inferred from the location text. |
| `salary*` | Only when the employer publishes pay. Greenhouse ranges are added automatically for small outputs, or for every job with **Fetch Greenhouse pay ranges**. |
| `companyName` | Exposed by Greenhouse, Workable and Recruitee. For Lever and Ashby use `companySlug`. |

A **`RUN_SUMMARY`** record in the run's key-value store lists every company with its detected ATS, status (`ok`, `not_found`, `error`, `skipped`), jobs on the board, jobs matching your filters and jobs output.

### Monitor mode (hiring signals)

- State lives in a named key-value store (`ats-jobs-monitor-state`) under your **Monitor state key**. Use one key per watchlist or schedule.
- **First run:** all matching jobs are output as `new`, or none if **Skip existing jobs on the first monitored run** is on (baseline only).
- **Next runs:** only jobs that appeared since the last run are output, plus `closed` ones if enabled.
- All jobs on a board are remembered regardless of your filters, so changing filters later does not flood you with old jobs.
- **Nothing is lost.** If a run stops early (max jobs or your spending limit), new jobs that were not output are not marked as seen, and the next run delivers them.

### Pricing

**$1.50 per 1,000 jobs**, pay per result (pay-per-event). You pay only for jobs saved to your dataset, plus a tiny Apify start fee per run ($0.00005). There is no monthly rental, and **in monitor mode you pay only for new or closed jobs.**

| Apify plan discount | Price per 1,000 jobs |
|---|---|
| Free / Starter | $1.50 |
| Bronze | $1.40 |
| Silver | $1.25 |
| Gold and above | $1.00 |

Examples at $1.50 / 1,000:

- Full export of 50 companies × 60 jobs ≈ 3,000 jobs ≈ **$4.50**.
- A daily monitor of 200 companies that finds ~40 new jobs/day ≈ 1,200 jobs/month ≈ **$1.80/month**.

Set **Max jobs in total** or the run's **maximum cost** to cap spending. The run stops gracefully when either limit is reached.

### FAQ

#### Is it legal to scrape these job boards?

This Actor only reads **public job postings** that employers publish on purpose. It uses the **official public job-board APIs** that Greenhouse, Lever, Ashby, Workable and Recruitee provide for career sites. These APIs need no login or authentication, and the Actor does not bypass any protection. It does **not** collect applicant data or candidate profiles, and it deliberately drops recruiter contact fields (e.g. Recruitee's mailbox e-mail). SmartRecruiters is not supported because its robots.txt disallows automated access. You are responsible for using the data lawfully and in line with each employer's terms. If unsure, ask a lawyer.

#### Do I need proxies?

No. These are public APIs built for career sites. The Actor never uses Apify Proxy, so you pay no proxy costs.

#### How many companies can I track?

Hundreds or thousands per run. Companies are processed in parallel while each ATS host is rate-limited politely. Big boards (2,000+ jobs) work at the default 256 MB. If you export many of them in full, with descriptions, 1 GB memory makes the run faster.

#### A company shows `not_found`. Why?

The slug is wrong, or the company uses a different ATS (e.g. Workday). Open their careers page, copy a job URL, and paste that instead.

#### How fresh is the data?

It is live. Every run reads the employer's board at that moment.

#### Can I get the data into Google Sheets, Slack or my CRM?

Yes. Use Apify integrations or webhooks. A common setup is a daily schedule in monitor mode, followed by a Slack or Sheets integration that receives only the new jobs.

#### Which ATS platforms are not supported?

iCIMS, Taleo, SuccessFactors and SmartRecruiters are not supported (yet). **Workday** (`*.myworkdayjobs.com`) is covered by the sibling [Workday Jobs Scraper + Monitor](https://apify.com/mayevil/workday-jobs-monitor). Tell us in the Issues tab which other ATS you need.

### Limitations

- Only the five ATS platforms above.
- Lever and Ashby do not expose the company name (`companyName` is `null`).
- Greenhouse has no structured remote flag or country. These are inferred from the location text, and the pay-range interval is inferred from the range title.
- Some employers post the same role in several locations as separate postings. Each posting is kept as published (Workable's duplicated multi-location entries are merged).
- Auto-detection can, rarely, pick another company that uses the same slug on a different ATS. Use a URL or `ats:slug` to be explicit.

### Related

| Actor | Use for |
|---|---|
| [Workday Jobs Scraper + Monitor](https://apify.com/mayevil/workday-jobs-monitor) | Workday `*.myworkdayjobs.com` CXS career boards + hiring signals |
| [Shopify Products.json Scraper — Price & Stock Monitor](https://apify.com/mayevil/shopify-catalog-monitor) | Public Shopify `/products.json` catalogs, price & stock changes |

# Actor input Schema

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

One company per line. Accepted: https://boards.greenhouse.io/airbnb, https://job-boards.greenhouse.io/x, https://jobs.lever.co/palantir, https://jobs.eu.lever.co/x, https://jobs.ashbyhq.com/ramp, https://apply.workable.com/huggingface, https://x.recruitee.com, "greenhouse:airbnb", "lever:palantir", "lever-eu:x", "ashby:ramp", "workable:huggingface", "recruitee:x", or a bare slug like "ramp" (the Actor probes each ATS and uses the first board that has jobs).

## `atsToTry` (type: `array`):

Order in which ATS platforms are probed when an entry is a bare slug. Entries given as URLs or with an "ats:" prefix ignore this.

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

Case-insensitive substrings. A job is kept if its title contains at least one. Leave empty to keep all titles.

## `titleExcludeKeywords` (type: `array`):

Case-insensitive substrings. Jobs whose title contains any of these are dropped (e.g. "intern", "senior").

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

Case-insensitive substrings matched against the job location(s) and country, e.g. "London", "Singapore", "Hong Kong", "Remote".

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

Keep only jobs flagged as remote by the ATS (or with "remote" in the location when the ATS has no flag).

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

Keep only jobs published in the last N days. 0 = no date filter. Jobs without a published date are kept.

## `monitorMode` (type: `boolean`):

Remembers which jobs it has already seen (in a named key-value store) and outputs only jobs that are new since the previous run with the same state key. You only pay for new jobs, which makes scheduled hiring-signal monitoring cheap.

## `monitorStateKey` (type: `string`):

Name of the watchlist memory. Use a different key for each independent watchlist/schedule.

## `skipExistingOnFirstRun` (type: `boolean`):

When a company is seen for the first time in monitor mode, just record its current jobs as a baseline instead of outputting them.

## `outputClosedJobs` (type: `boolean`):

In monitor mode, also output a record with status "closed" for each job that disappeared from a board since the last run.

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

Include the full job description. Turn off for smaller, faster datasets.

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

Plain text (clean, LLM-friendly) or the original HTML.

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

Greenhouse publishes pay-transparency ranges only on single-job pages. When 100 or fewer Greenhouse jobs per company are output, they are fetched automatically together with the description. Turn this on to also fetch them for larger outputs (one extra request per job, slower). Ashby, Lever and Recruitee salaries are always included when published.

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

Cap on output jobs per company. 0 = no cap.

## `maxJobsTotal` (type: `integer`):

The run stops gracefully after outputting this many jobs (cost control). 0 = no cap.

## `maxConcurrency` (type: `integer`):

How many companies are processed in parallel. Requests to the same ATS host are additionally throttled (Lever: max 1 request/second as requested in its robots.txt).

## `maxRequestsPerMinute` (type: `integer`):

Upper bound on how many company boards are started per minute.

## Actor input object example

```json
{
  "companies": [
    "https://jobs.ashbyhq.com/ramp",
    "greenhouse:airbnb",
    "lever:palantir",
    "huggingface"
  ],
  "atsToTry": [
    "greenhouse",
    "lever",
    "ashby",
    "workable",
    "recruitee"
  ],
  "titleKeywords": [],
  "titleExcludeKeywords": [],
  "locationKeywords": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "monitorMode": false,
  "monitorStateKey": "default",
  "skipExistingOnFirstRun": false,
  "outputClosedJobs": false,
  "includeDescription": true,
  "descriptionFormat": "text",
  "includeGreenhouseSalary": false,
  "maxJobsPerCompany": 0,
  "maxJobsTotal": 1000,
  "maxConcurrency": 5,
  "maxRequestsPerMinute": 60
}
```

# Actor output Schema

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

No description

## `runSummary` (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://jobs.ashbyhq.com/ramp",
        "greenhouse:airbnb",
        "lever:palantir",
        "huggingface"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mayevil/greenhouse-lever-jobs-scraper").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://jobs.ashbyhq.com/ramp",
        "greenhouse:airbnb",
        "lever:palantir",
        "huggingface",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mayevil/greenhouse-lever-jobs-scraper").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://jobs.ashbyhq.com/ramp",
    "greenhouse:airbnb",
    "lever:palantir",
    "huggingface"
  ]
}' |
apify call mayevil/greenhouse-lever-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

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/0GVmwtklcfpMtEpDq/builds/M5tHXNzDNs1wyahyd/openapi.json