# ATS Job Scraper - Greenhouse, Lever, Ashby, Workday & More (`fuyuki0/ats-jobs-scraper`) Actor

Scrape jobs straight from company career boards across 8 applicant tracking systems: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Rippling, Breezy and Workday. Paste a board URL and the system is detected for you. Filter by title or location, and get only postings new since your last run.

- **URL**: https://apify.com/fuyuki0/ats-jobs-scraper.md
- **Developed by:** [Phupatchara Treenuson](https://apify.com/fuyuki0) (community)
- **Categories:** Jobs, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ATS Job Scraper — Greenhouse, Lever, Ashby, Workday & more

Scrape job postings **straight from company career boards** instead of from a job
aggregator. Paste the board URL of any company you want watched and this Actor
detects which applicant tracking system they run, fetches the postings, and
returns them all in one shape.

Eight systems are supported:

| Applicant tracking system | Typical board URL |
|---|---|
| Greenhouse | `https://boards.greenhouse.io/stripe` |
| Lever | `https://jobs.lever.co/netflix` |
| Ashby | `https://jobs.ashbyhq.com/ramp` |
| Workable | `https://apply.workable.com/persado` |
| SmartRecruiters | `https://jobs.smartrecruiters.com/Visa` |
| Rippling | `https://ats.rippling.com/rippling/jobs` |
| Breezy HR | `https://acme.breezy.hr` |
| Workday | `https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite` |

You can also write `greenhouse:stripe` or `lever:netflix` if you already know the
platform.

### Why scrape career boards rather than a job site

Postings appear on a company's own board first and reach the aggregators later,
with fields dropped along the way. Going to the source gives you the department,
the team, the employment type, and the real application link, on the day it goes
live.

### What makes this one different

**Only-new delivery.** The Actor remembers what it already returned. Schedule it
daily and each run gives you what appeared since yesterday, not the same 600 rows
every morning. A run that finds nothing new costs nothing beyond platform compute.

**One dead board does not kill the run.** Companies rename and close boards
constantly. Every board is fetched independently; a 404 is logged and skipped and
you still get results from the rest. Watching 200 companies is normal use here.

**Correct billing on multi-location roles.** Rippling publishes one row per
location — its own board returns 691 rows for 367 actual jobs. Those are collapsed
into one posting with a list of locations, so you are not charged for the same
role four times. This is checked by a test.

**Workday is included.** Large employers run Workday, and it needs a different
request shape from every other board. Most career-board Actors skip it.

### Output

One record per posting:

```json
{
  "uid": "143fa3766650b2e1",
  "platform": "ashby",
  "company": "ramp",
  "company_name": null,
  "source_id": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Security Engineer, Cloud",
  "location": "New York, NY (HQ)",
  "locations": ["New York, NY (HQ)", "Remote (US)"],
  "remote": true,
  "department": "Engineering",
  "team": "Backend",
  "employment_type": "FullTime",
  "salary": "$180K – $220K",
  "posted": "2026-05-01",
  "updated": null,
  "description": "Secure the cloud …",
  "url": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245"
}
```

### Filters

- **keywords** / **excludedKeywords** — match against title, department, and team
- **locations** — plain text, so `London` and `United Kingdom` both work
- **departments** — match against department and team
- **remoteOnly** — uses the board's own remote flag where there is one, the
  location text otherwise
- **postedWithinDays** — publication window
- **onlyNew** — only what has appeared since the last run (on by default)
- **includeDescription** — drop the body if you only need titles and links
- **maxResults** — hard cap on postings delivered, and therefore on cost

### What each board actually publishes

Boards differ, and pretending otherwise would make the output look complete when
it is not:

| Platform | Description in output | Publication date | Salary |
|---|---|---|---|
| Greenhouse | yes | yes | no |
| Lever | yes | yes | no |
| Ashby | yes | yes | when the employer opts in |
| Breezy | when set | yes | when set |
| Workable | no | yes | no |
| SmartRecruiters | no | yes | no |
| Rippling | no | **no** | no |
| Workday | no | **no** | no |

Rippling and Workday publish no dates at all, so `postedWithinDays` cannot filter
them and their postings are always kept. Use **onlyNew** to get recency on those
boards — that is exactly what it is for.

### Use cases

- **Job boards and aggregators** — pull fresh postings from a list of employers
  you track, deduplicated across runs
- **Recruiters** — watch competitors and target accounts for new openings
- **Market research** — measure hiring by department across a sector over time
- **Job seekers** — monitor a shortlist of companies and see new roles the day
  they post
- **AI agents** — a clean, typed job feed to call as a tool

### Notes and limits

- Public board endpoints only. No logins, no cookies, no access controls
  circumvented.
- Workday returns 20 postings per request and stops serving results past 2,000 per
  board.
- Workday's list response gives a location summary such as `5 Locations` rather
  than the individual cities, and no department. That is what the board publishes.
- Descriptions are truncated to 5,000 characters.
- Recruitee, Personio, Teamtailor, and Comeet are **not** supported. Their
  endpoints could not be verified against a live board, and shipping a parser that
  has never seen real data is how scrapers end up silently returning nothing.

### Pricing

Pay per event: you are charged per posting delivered. A scheduled run that finds
nothing new delivers nothing and charges nothing.

# Actor input Schema

## `boards` (type: `array`):

Paste the career board URL of each company you want watched. The applicant tracking system is detected automatically — Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Rippling, Breezy, and Workday are supported. A prefix form such as greenhouse:stripe works too.

## `keywords` (type: `array`):

Keep only postings whose title, department, or team contains one of these. Leave empty to keep everything the boards publish.

## `excludedKeywords` (type: `array`):

Drop postings whose title, department, or team contains one of these. Useful for stripping out internships or contract roles.

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

Keep only postings whose location matches one of these. Matched as plain text, so 'London' and 'United Kingdom' both work.

## `departments` (type: `array`):

Keep only postings in these departments or teams.

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

Keep only remote postings. Uses the board's own remote flag where it publishes one, and the location text otherwise.

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

Keep only postings published in the last N days. Rippling and Workday publish no dates, so their postings are always kept — use 'Only new postings' to get recency on those boards.

## `onlyNew` (type: `boolean`):

Remember what was already delivered and return only what has appeared since. This is what makes a daily schedule cheap: a run that finds nothing new charges nothing. Turn it off to get the full board every time.

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

Descriptions are long and dominate storage. Turn this off if you only need titles, locations, and links. Workable, SmartRecruiters, Rippling, and Workday do not publish a body in their list responses, so those postings have none either way.

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

Hard cap on how many postings this run delivers, and therefore on what it costs.

## Actor input object example

```json
{
  "boards": [
    "https://boards.greenhouse.io/stripe"
  ],
  "keywords": [
    "engineer",
    "data"
  ],
  "excludedKeywords": [
    "intern",
    "contract"
  ],
  "locations": [
    "London",
    "Remote"
  ],
  "departments": [
    "Engineering"
  ],
  "remoteOnly": false,
  "postedWithinDays": 7,
  "onlyNew": true,
  "includeDescription": true,
  "maxResults": 1000
}
```

# Actor output Schema

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

Every posting delivered by this run, as JSON. One record per posting, with company, location, department, employment type, and a link to the posting on the company's careers site.

## `jobsCsv` (type: `string`):

The same postings as a CSV file, for opening in Excel or Google Sheets.

## `datasetView` (type: `string`):

Table view of the postings returned by 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 = {
    "boards": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.lever.co/netflix"
    ]
};

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fuyuki0/ats-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/owaj8mYSDcPuhYe9Q/builds/yJc2T4CE6ulTxKkpN/openapi.json