# Greenhouse, Lever & Ashby Jobs Scraper + New Jobs Monitor (`mercury_ops/ats-jobs-monitor`) Actor

Get every open job from any company's Greenhouse, Lever, Ashby, Workable, Recruitee or Personio careers page via their official public job-board APIs, with salary, location, remote and UK flags, or schedule it to report only new, changed and closed jobs. No login.

- **URL**: https://apify.com/mercury_ops/ats-jobs-monitor.md
- **Developed by:** [Mercury](https://apify.com/mercury_ops) (community)
- **Categories:** Jobs, Automation, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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 + New Jobs Monitor

**Pull every open job straight from a company's own applicant-tracking system, with salary, location, remote and UK flags, in one clean schema. Or schedule it and get only the new, changed and closed jobs.** Six ATS platforms, detected automatically. No login, no browser, no API keys.

### Supported platforms

| ATS | Example input |
|---|---|
| Greenhouse | `https://job-boards.greenhouse.io/monzo` or `greenhouse:monzo` |
| Lever (US and EU) | `https://jobs.lever.co/palantir` or `lever:palantir` |
| Ashby | `https://jobs.ashbyhq.com/ramp` |
| Workable | `https://apply.workable.com/huggingface` |
| Recruitee | `https://bunq.recruitee.com` |
| Personio | `https://acme.jobs.personio.de` |

Don't know which ATS a company uses? Give its **website or careers page** (e.g. `monzo.com`) and the Actor finds the job-board link on the page, or give a **bare slug** (e.g. `bunq`) and it tries each platform.

### Two modes

| Mode | What you get | You pay for |
|---|---|---|
| **All jobs** | Every open job that matches your filters. | Each job row |
| **Changes only (monitor)** | Run it daily. Each run outputs only jobs that are **new**, **updated** (title, location or salary changed) or **removed** (closed) since the last run. | A tiny fee per job compared + each change |

### Use cases

- **Hiring signals for sales and recruiting agencies:** know the day a target account opens a new role (e.g. its first Head of Data, or 10 new sales roles).
- **Job alerts and niche job boards:** feed new roles from a list of companies into Slack, email, Google Sheets, Airtable or your own site.
- **Market and salary research:** salary ranges where the ATS publishes them (common on Ashby, Lever and Recruitee), department mix, remote share, UK vs elsewhere.
- **AI agents:** call it through the Apify MCP server to answer "who's hiring X in London?".

### Input

```json
{
  "companies": ["https://job-boards.greenhouse.io/monzo", "lever:palantir", "monzo.com", "bunq"],
  "mode": "all",
  "titleKeywords": ["engineer", "data"],
  "excludeTitleKeywords": ["intern"],
  "locationKeywords": ["London", "Remote"],
  "ukOnly": false,
  "remoteOnly": false,
  "postedWithinDays": 30,
  "includeDescription": false
}
```

Filters are applied **before** billing: you only pay for jobs you keep.

### Output (one row per job)

```json
{
  "company": "Ramp",
  "ats": "ashby",
  "board": "ramp",
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Security Engineer, Cloud",
  "department": "Engineering",
  "team": "Backend",
  "employmentType": "FullTime",
  "location": "New York, NY (HQ)",
  "locations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "countryCode": "US",
  "remote": true,
  "workplaceType": "Hybrid",
  "ukBased": false,
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salaryText": "$211.4K – $290.6K • Offers Equity",
  "url": "https://jobs.ashbyhq.com/ramp/34413f8d-…",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-…/application",
  "postedAt": "2026-04-07T17:12:35+00:00",
  "updatedAt": null,
  "description": null,
  "checkedAt": "2026-10-26T18:32:43+00:00"
}
```

In *Changes only* mode rows also carry `changeType` (`new`, `updated`, `removed`) and, for updates, `changedFields`. A per-company summary (which ATS and board were found, open jobs, matched jobs, changes, errors) is saved as `OUTPUT` in the run's key-value store.

### How it works and what it respects

- Uses only the **official public job-board APIs** each ATS provides so that companies can publish their openings (the same feeds their own careers pages use). No scraping of logged-in pages, no candidate data.
- Job postings are company content. The Actor does not collect recruiter or candidate personal data; it doesn't output contact emails.
- **Obeys robots.txt** on every host and identifies itself honestly. SmartRecruiters is deliberately not supported because its API's robots.txt disallows general crawlers.
- Polite: one request at a time per host with a pause, back-off on rate limits.

### Limits

- Only companies whose careers pages run on the six platforms above. Workday, iCIMS, Taleo and custom career sites aren't supported.
- Salary appears only when the company publishes it in the ATS.
- `ukBased` and `remote` are derived from the ATS's own fields and location text, so a few odd location strings can be misclassified.
- Greenhouse doesn't expose employment type; Personio doesn't expose country codes.
- "Updated" compares title, location and salary only. If you change filters on a monitor, use a new `monitorName`.
- Max 500 companies per run.

### Pricing (pay per event)

- **Job** (All jobs mode): $0.001 per job, i.e. **$1.00 per 1,000 jobs**.
- **Job checked** (Changes only): $0.00005 per job compared, i.e. $0.05 per 1,000.
- **Job change** (Changes only): $0.002 per new, updated or closed job.

Example: monitoring 100 companies averaging 60 open roles, daily, with ~40 new or closed roles a day, costs about $0.38/day ($0.30 compared + $0.08 changes).

# Actor input Schema

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

One per line. Any of: an ATS board URL (job-boards.greenhouse.io/monzo, jobs.lever.co/acme, jobs.ashbyhq.com/ramp, apply.workable.com/acme, acme.recruitee.com, acme.jobs.personio.de), 'greenhouse:slug' style, a company's own careers page or website (the ATS link is found automatically), or a bare slug (tried on each ATS).

## `mode` (type: `string`):

'All jobs' outputs every open job that matches your filters (one billable row per job). 'Changes only' compares with the previous run of the same monitor and outputs only new, updated (title, location or salary changed) and removed (closed) jobs; the first run saves a baseline. Schedule it daily for a hiring-signal or job-alert feed.

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

Optional. Keep jobs whose title contains any of these words, e.g. engineer, data, marketing. Case-insensitive.

## `excludeTitleKeywords` (type: `array`):

Optional. Drop jobs whose title contains any of these, e.g. intern, senior.

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

Optional. Keep jobs whose location text or country code contains any of these, e.g. London, Manchester, GB, Remote.

## `ukOnly` (type: `boolean`):

Keep only jobs located in the UK (country code GB, or UK place names in the location).

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

Keep only jobs marked remote by the ATS or with 'remote' in the location.

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

Optional. Keep only jobs first published in the last N days (where the ATS gives a date).

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

Adds the full job description as plain text (up to 8,000 characters).

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

Safety cap per company board.

## `monitorName` (type: `string`):

Changes only: snapshots are kept per monitor name and board in a key-value store named 'ats-jobs-monitor-state' in your account. Use a new name if you change filters, otherwise jobs that no longer match look 'removed'.

## `proxyConfiguration` (type: `object`):

Not needed: these are public APIs. Only enable if you hit rate limits.

## Actor input object example

```json
{
  "companies": [
    "https://job-boards.greenhouse.io/monzo",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "mode": "all",
  "ukOnly": false,
  "remoteOnly": false,
  "includeDescription": false,
  "maxJobsPerCompany": 2000,
  "monitorName": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

No description

## `changes` (type: `string`):

No description

## `full` (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/monzo",
        "https://jobs.ashbyhq.com/ramp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mercury_ops/ats-jobs-monitor").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/monzo",
        "https://jobs.ashbyhq.com/ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mercury_ops/ats-jobs-monitor").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/monzo",
    "https://jobs.ashbyhq.com/ramp"
  ]
}' |
apify call mercury_ops/ats-jobs-monitor --silent --output-dataset

```

## MCP server setup

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

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/8AJsBt3Ds78GVbdCi/builds/QoWlhCODMHRLTbU3H/openapi.json