# 💼 ATS Job Scraper: Workday, Greenhouse, Lever, Ashby + more (`findata/ats-jobs-feed`) Actor

One job feed from Workday, Greenhouse, Lever, Ashby and SmartRecruiters career sites. Title, location, pay, posted date, description and apply link in one clean format. Full Workday boards past the 2,000 cap. Only-new mode for monitoring. No login, no proxies.

- **URL**: https://apify.com/findata/ats-jobs-feed.md
- **Developed by:** [Fin Data](https://apify.com/findata) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $2.10 / 1,000 job records

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

## Workday, Greenhouse, Lever, Ashby and SmartRecruiters Job Scraper

One clean job feed across the five applicant tracking systems that power most corporate career sites. Paste career-site URLs, get every open role as a normalized record: title, department, location, remote flag, employment type, salary, posting date, description and apply link. The same schema whether the company runs Workday or Greenhouse.

Built for recruiters, staffing firms, job boards, sales teams that use hiring as a buying signal, and AI agents that need job data without parsing five different APIs.

### Why these five, in this order

Workday runs the career sites of most large enterprises, and it is the hardest of the five to scrape well: its job API is undocumented, pages 20 at a time, and stops at 2,000 results. This actor handles all of that and returns the whole board. Greenhouse, Lever and Ashby cover most technology and growth companies and publish clean public APIs, so descriptions and (for Lever and Ashby) structured salary ranges come free. SmartRecruiters rounds out the large-employer coverage, especially outside the US.

Together they cover the majority of employers that post jobs on their own career site rather than only on job boards.

### What you get

- Five ATS vendors, one output schema. The vendor is detected from the URL; you never say which ATS a company uses.
- Whole Workday boards, including sites over the 2,000-job cap (split by facet automatically and de-duplicated).
- Only-new mode. Run it on a schedule and get only postings that were not on the board last time. You pay only for jobs that are output.
- Filters that run before billing: title keywords, exclude words, locations, departments, remote only, posted within N days.
- Salary parsing. Structured ranges when the ATS provides them (Lever, Ashby), parsed from text when it does not (Workday pay ranges, Greenhouse descriptions).
- Fail soft. One moved or broken board is logged and skipped; the rest of the run completes.

### Supported career sites

| ATS | URL pattern | Description in list call | Notes |
| --- | --- | --- | --- |
| Workday | {tenant}.{wd1..wd5}.myworkdayjobs.com/{site} | With Fetch details | Any language path works; the actor strips it. Boards over 2,000 jobs are split by facet |
| Greenhouse | boards.greenhouse.io/{company}, job-boards.greenhouse.io/{company} | Yes | EU-hosted boards detected automatically |
| Lever | jobs.lever.co/{company}, jobs.eu.lever.co/{company} | Yes | Structured salary ranges when published |
| Ashby | jobs.ashbyhq.com/{company} | Yes | Structured compensation when published |
| SmartRecruiters | careers.smartrecruiters.com/{Company}, jobs.smartrecruiters.com/{Company} | With Fetch details | Company identifier is case-sensitive |

You can also write sources as `vendor:identifier`, for example `workday:workday.wd5/Workday` or `greenhouse:stripe`.

### Input

```json
{
  "sources": [
    "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/notion",
    "https://careers.smartrecruiters.com/BoschGroup"
  ],
  "keywords": ["accountant", "financial analyst", "controller"],
  "locations": ["Atlanta", "Georgia", "GA", "Remote"],
  "postedWithinDays": 14,
  "onlyNew": true,
  "fetchDetails": false
}
```

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| preset | string | custom | Employer list: `custom` (default), `sample`, `georgia-sc`. `custom` runs the sites you list and falls back to the sample boards when the list is empty |
| sources | string\[] | \[] | Career-site URLs or `vendor:identifier` strings |
| keywords | string\[] | \[] | Keep jobs whose title contains any of these (case-insensitive) |
| excludeKeywords | string\[] | \[] | Drop jobs whose title contains any of these |
| locations | string\[] | \[] | Keep jobs whose location text contains any of these |
| departments | string\[] | \[] | Keep jobs whose department or team contains any of these |
| remoteOnly | boolean | false | Keep only jobs flagged remote |
| postedWithinDays | integer | 0 | Keep only jobs posted or updated in the last N days; 0 disables |
| fetchDetails | boolean | false | One extra request per job for Workday and SmartRecruiters to get description, exact dates, additional locations. Only jobs that pass the title and location filters are fetched, so a 2,000-job board filtered to one city costs a few dozen requests |
| includeDescriptionHtml | boolean | false | Add the raw HTML description next to the plain text |
| onlyNew | boolean | false | Output only jobs not seen on a previous run of this source |
| seenStoreName | string | ats-jobs-feed-seen | Key-value store that remembers seen job IDs; use one name per monitor |
| maxJobsPerSource | integer | 0 | Stop after N jobs per source; 0 means all |
| maxConcurrency | integer | 5 | Career sites pulled in parallel |

### Output

One record per job. Fields are identical across vendors; vendor-specific extras sit under `extra`.

```json
{
  "vendor": "workday",
  "source": "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
  "company": "Workday, Inc.",
  "jobId": "JR-0110787",
  "title": "Senior Product Manager, Technical",
  "department": null,
  "team": null,
  "location": "USA, CA, Pleasanton",
  "locations": ["USA, CA, Pleasanton"],
  "country": "US",
  "remote": null,
  "employmentType": "Full Time",
  "postedAt": "2026-11-04T00:00:00.000Z",
  "updatedAt": null,
  "url": "https://workday.wd5.myworkdayjobs.com/Workday/job/USA-CA-Pleasanton/Senior-Product-Manager--Technical_JR-0110787",
  "applyUrl": "https://workday.wd5.myworkdayjobs.com/Workday/job/USA-CA-Pleasanton/Senior-Product-Manager--Technical_JR-0110787",
  "descriptionText": "Your work days are brighter here...",
  "salaryMin": 168000,
  "salaryMax": 252000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salaryText": "Primary Location Base Pay Range: $168,000 USD - $252,000 USD",
  "extra": { "postedOnText": "Posted Today", "remoteType": null, "bulletFields": ["JR-0110787"], "endDate": null, "externalPath": "/job/USA-CA-Pleasanton/Senior-Product-Manager--Technical_JR-0110787" },
  "scrapedAt": "2026-11-05T01:47:38.912Z"
}
```

| Field | Meaning |
| --- | --- |
| vendor | workday, greenhouse, lever, ashby or smartrecruiters |
| company | Company name as the ATS reports it, or the board identifier when the ATS does not expose a name. Workday reports the hiring organization name when Fetch details is on, otherwise the tenant |
| jobId | Stable ID within the vendor (Workday requisition ID, Greenhouse numeric ID, Lever and Ashby UUIDs, SmartRecruiters posting ID). Use `vendor + jobId` as a global key |
| location, locations | Primary location text and every location listed, primary first |
| remote | true when the ATS flags remote or the location says so; false when the ATS says on-site; null when unknown |
| postedAt, updatedAt | ISO 8601. Workday list pages give relative dates ("Posted 3 Days Ago"); these are converted, and "30+ Days Ago" becomes null unless Fetch details is on |
| salaryMin, salaryMax, salaryCurrency, salaryPeriod | Numbers when the ATS publishes a range or the description states one; otherwise null |
| descriptionText | Plain text. Available in the list call for Greenhouse, Lever and Ashby; needs Fetch details for Workday and SmartRecruiters |

A `RUN_SUMMARY` record in the default key-value store reports sources processed, jobs fetched, filtered, de-duplicated, skipped as already seen, and any source failures with the error text.

### Pricing

Pay per event. You are charged per job record written to the dataset, plus a small actor-start event. Filtered-out jobs and already-seen jobs in only-new mode are not charged. No proxies are needed, so platform usage is minimal: a run returning 186 jobs from three boards used under one cent of platform resources.

### Monitoring new postings

1. Set `onlyNew` to true and give `seenStoreName` a name for this monitor.
2. Add your filters.
3. Schedule the actor (daily works well; hourly for high-volume boards).
4. Connect the dataset to Google Sheets, Slack, Make, Zapier, or a webhook from the Integrations tab.

The first run outputs everything currently on the boards and remembers it. Each later run outputs only what is new. Jobs that leave a board and come back are treated as new.

### Finding career-site URLs

Open a company's careers page and click any job. The address bar shows the ATS: `myworkdayjobs.com`, `boards.greenhouse.io`, `jobs.lever.co`, `jobs.ashbyhq.com`, or `smartrecruiters.com`. Paste that URL as a source; the actor trims it to the board.

### Limits and notes

- Public job-board endpoints only. No login, no proxies, no private data.
- Workday returns at most 2,000 jobs per query. Boards above that are split by facet; a handful of very large boards with coarse facets may still miss a few postings. Tested on a 2,763-job board.
- Workday `company` is the tenant name unless Fetch details is on, which reads the hiring organization name.
- Greenhouse and Lever boards that are closed or renamed return an error for that source only; the run continues.
- Descriptions are plain text by default. Turn on `includeDescriptionHtml` for the original markup.

### For AI agents

Every field is optional: an empty input `{}` runs the sample boards and returns jobs, so a first call never fails. Pick `"preset": "sample"` to say so explicitly, or `"preset": "georgia-sc"` for the curated Georgia and upstate SC employer list. Minimal call: `{ "sources": ["https://boards.greenhouse.io/stripe"] }`. Pass any careers URL from the five supported systems; the vendor is detected. Add `"keywords"` and `"locations"` arrays to narrow, `"fetchDetails": true` for Workday and SmartRecruiters descriptions. Every record has the same fields; `vendor + jobId` is the stable key.

### Related FinData job scrapers

Same engine, same output fields, so records from any of them can be combined.

- [Workday Job Scraper](https://apify.com/findata/workday-job-scraper)
- [Greenhouse Job Scraper](https://apify.com/findata/greenhouse-job-scraper)
- [Lever Job Scraper](https://apify.com/findata/lever-job-scraper)
- [Ashby Job Scraper](https://apify.com/findata/ashby-job-scraper)
- [Career Site Job Scraper (any company, ATS auto-detected)](https://apify.com/findata/career-site-job-scraper)

### Using it from code

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('findata/ats-jobs-feed').call({
    sources: ['https://workday.wd5.myworkdayjobs.com/en-US/Workday'],
    keywords: ['engineer'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Works the same through the Apify API, MCP server and the Python client.

# Changelog

This Actor's version history is a separate document: https://apify.com/findata/ats-jobs-feed/changelog.md

# Actor input Schema

## `preset` (type: `string`):

Pick a ready-made list or use your own. "The career sites I list below" runs exactly the sites in the next field, and if that field is empty it falls back to the sample boards so a run never fails for lack of input. The other choices add a curated list on top of anything you paste.

## `sources` (type: `array`):

Career-site URLs, one per line. Open a company's careers page, click any job and paste the address; the ATS is detected from the URL. Examples: https://workday.wd5.myworkdayjobs.com/en-US/Workday, https://boards.greenhouse.io/stripe, https://jobs.lever.co/palantir, https://jobs.ashbyhq.com/notion, https://careers.smartrecruiters.com/BoschGroup. Short forms also work: greenhouse:stripe or workday:workday.wd5/Workday. Optional when an Employer list is chosen above.

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

Keep jobs whose title contains at least one of these words or phrases. Case-insensitive. Leave empty to keep all.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these words or phrases. Case-insensitive.

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

Keep jobs whose location text contains at least one of these, e.g. Atlanta, Georgia, GA, United States. Case-insensitive. Leave empty to keep all. With the Georgia and upstate SC list chosen and this left empty, the list's own Georgia and South Carolina locations are used.

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

Keep jobs whose department or team contains at least one of these, e.g. Finance, Engineering, People.

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

Keep only jobs the ATS marks as remote or whose location says remote.

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

Keep only jobs posted or updated within this many days. 0 means no limit. Workday list pages only give relative dates, so this is applied to the parsed value.

## `fetchDetails` (type: `boolean`):

Workday and SmartRecruiters list calls do not include descriptions. Turn this on to make one extra request per job for the description, exact posted date, job family and additional locations. Greenhouse, Lever and Ashby return descriptions in the list call either way. Title and location filters are applied before the extra request, so only jobs that can pass them are fetched. Slower and uses more platform usage.

## `includeDescriptionHtml` (type: `boolean`):

Add the raw HTML description to each record alongside the plain text. Makes datasets larger.

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

Remember every job ID seen per source in a named key-value store and output only jobs not seen before. Use with a schedule to get a feed of new postings. You are charged only for jobs that are output.

## `seenStoreName` (type: `string`):

Name of the key-value store used by only-new mode. Use a different name per monitor if you run several configurations.

## `maxJobsPerSource` (type: `integer`):

Stop paging a source after this many jobs. 0 means no limit. Workday boards cap at 2,000 per query; the actor splits large boards by facet automatically so you still get the whole board.

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

How many career sites to pull at the same time.

## Actor input object example

```json
{
  "preset": "custom",
  "sources": [
    "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/notion",
    "https://careers.smartrecruiters.com/BoschGroup"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "fetchDetails": false,
  "includeDescriptionHtml": false,
  "onlyNew": false,
  "seenStoreName": "ats-jobs-feed-seen",
  "maxJobsPerSource": 0,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

One record per job posting, normalized across Workday, Greenhouse, Lever, Ashby and SmartRecruiters.

## `jobsTable` (type: `string`):

Same records in the Console table view.

## `runSummary` (type: `string`):

Sources processed, jobs fetched, filtered, de-duplicated, already seen, and any source failures.

# 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 = {
    "sources": [
        "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/notion",
        "https://careers.smartrecruiters.com/BoschGroup"
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("findata/ats-jobs-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 = {
    "sources": [
        "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/notion",
        "https://careers.smartrecruiters.com/BoschGroup",
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
}

# Run the Actor and wait for it to finish
run = client.actor("findata/ats-jobs-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 '{
  "sources": [
    "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/notion",
    "https://careers.smartrecruiters.com/BoschGroup"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": []
}' |
apify call findata/ats-jobs-feed --silent --output-dataset

```

## MCP server setup

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