# Workday, Greenhouse, Lever, Ashby & Oracle Jobs Scraper (ATS) (`hirewatch/career-sites-jobs-tracker`) Actor

Scrape all open jobs from company career sites on Workday, Greenhouse, Lever, Ashby and Oracle Recruiting Cloud (ATS) into one clean schema. Track new and closed job postings between runs and get per-company hiring signals.

- **URL**: https://apify.com/hirewatch/career-sites-jobs-tracker.md
- **Developed by:** [HireWatch](https://apify.com/hirewatch) (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

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

## Workday, Greenhouse, Lever, Ashby & Oracle Jobs Scraper (ATS) + Hiring Signals

Scrape **every open job from company career sites** built on **Workday, Greenhouse, Lever, Ashby and Oracle Recruiting Cloud** in one clean, consistent format, and see **which job postings are new and which closed** since your last run. It's a career site / ATS jobs scraper and hiring-signals tracker in one: paste career-site URLs or company names and get normalized jobs plus an optional per-company hiring summary.

*Independent tool: not affiliated with or endorsed by Workday, Oracle, Greenhouse, Lever or Ashby. Names are used only to describe compatibility.*

Supported applicant-tracking systems (ATS):

| Career-site platform | What you paste | Example |
|---|---|---|
| Workday | the career-site URL | `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite` |
| Oracle Recruiting Cloud | the Candidate Experience URL | `https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1001/jobs` |
| Greenhouse | board URL **or just the company name** | `https://boards.greenhouse.io/stripe` or `Stripe` |
| Lever | board URL **or just the company name** | `https://jobs.lever.co/palantir` or `Palantir` |
| Ashby | board URL **or just the company name** | `https://jobs.ashbyhq.com/ramp` or `Ramp` |

Want a specific display name? Write `Name | URL`, e.g. `JPMorgan Chase | https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1001/jobs`.

You can also paste a company's own careers page (e.g. `https://acme.com/careers`) or just its domain (e.g. `figma.com`). The Actor looks for an embedded or linked board from the list above and uses it.

### What you can use it for

- **Sales & recruiting signals.** A company that opens 40 new engineering roles this week is buying tools and services. Schedule a daily run and get only the changes.
- **Market and competitor research.** See open headcount by department and location, the remote/hybrid mix, and how fast a company is hiring.
- **Job boards and aggregators.** Pull complete, de-duplicated listings straight from the source, with salary ranges where the company publishes them.
- **Investors and analysts.** Hiring velocity (new minus closed jobs) is a leading indicator of growth or cutbacks.

### Why this Actor

- **One schema for five platforms.** Title, department, location(s), country, remote/hybrid/onsite, employment type, posted date, salary, job URL and apply URL.
- **New / closed tracking built in.** Each run labels jobs `new`, `unchanged` or `closed` (state is kept in a named key-value store). Use **Only changes** mode for cheap daily monitoring.
- **Gets more than 2,000 jobs from big Workday sites.** Workday's own listing stops at 2,000 results. The Actor splits the listing by job family (or another filter) to collect all of them.
- **Company hiring-signal summary.** One optional row per company: open jobs, new and closed since the last run, net change and trend, jobs posted in the last 7 and 30 days, top departments and locations, and remote mix.
- **Polite and reliable.** It uses only the public job-listing data that each career page itself loads in your browser. There are no logins and no browser automation. It respects robots.txt and keeps at least 1 second between requests to a site. It retries timeouts, 429 and 5xx responses with exponential back-off and honours `Retry-After`.
- **Clear errors.** Stale or wrong URLs, unknown company names, unsupported pages and sites that disallow crawling are reported per company in the run's `RUN_REPORT` and status message. One bad input never fails the whole run.

### Input examples

**All jobs at a few companies (first run):**

```json
{
  "targets": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
    "https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1001/jobs",
    "Stripe",
    "Palantir",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "maxJobsPerCompany": 0,
  "includeCompanySummary": true
}
```

**Daily change feed for engineering roles (schedule this daily):**

```json
{
  "targets": ["Stripe", "OpenAI", "https://intel.wd1.myworkdayjobs.com/External"],
  "maxJobsPerCompany": 0,
  "outputMode": "changesOnly",
  "titleKeywords": ["engineer", "developer"],
  "trackerId": "eng-daily"
}
```

**Hiring signals only (cheapest: one row per company, no job rows):**

```json
{
  "targets": ["Stripe", "Palantir", "Ramp"],
  "includeJobs": false,
  "includeCompanySummary": true,
  "maxJobsPerCompany": 0
}
```

**Remote jobs with full descriptions:**

```json
{ "targets": ["Ramp"], "remoteOnly": true, "includeDescriptions": true }
```

**Fresh roles only, with a hard cap on rows (and cost):**

```json
{
  "targets": ["Stripe", "Databricks", "https://intel.wd1.myworkdayjobs.com/External"],
  "titleKeywords": ["engineer"],
  "postedWithinDays": 7,
  "maxItems": 200
}
```

`postedWithinDays` keeps only jobs posted in the last N days, and jobs without a posted date are left out. `maxItems` stops the run after that many job rows across all companies.

### Output

#### Job record (real example, trimmed of empty fields)

```json
{
  "recordType": "job",
  "platform": "ashby",
  "companySlug": "ramp",
  "companyName": "Ramp",
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "globalId": "ashby:ramp:34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Security Engineer, Cloud",
  "department": "Engineering",
  "team": "Backend",
  "employmentType": "full_time",
  "remoteType": "hybrid",
  "location": "New York, NY (HQ)",
  "locations": ["New York, NY (HQ)", "Remote (Canada)", "Remote (US)", "Miami, FL"],
  "country": "USA",
  "postedAt": "2026-04-07T17:12:35Z",
  "salaryText": "$211.4K – $290.6K • Offers Equity",
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryInterval": "year",
  "url": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245/application",
  "changeStatus": "new",
  "firstSeenAt": "2026-10-08T03:07:59Z",
  "closedAt": null,
  "scrapedAt": "2026-10-08T03:07:59Z"
}
```

Every record has the same fields (missing values are `null`), including `careerSite`, `requisitionId`, `legalEntity` (Workday hiring entity, with descriptions on), `postedAtText`, `descriptionText` and `descriptionHtml`.

`companyName` is the name the platform publishes (Greenhouse), the name you searched for, or the label you gave with `Name | URL`. Otherwise it is the board's slug (e.g. `capitalone`).
`changeStatus` is `new` (first time seen; on the very first run every job is new), `unchanged`, or `closed` (gone since the previous run, with `closedAt` set). `globalId` is stable across runs, so use it as your primary key. When a site's own job count is off by a few (common on Oracle, or when jobs change while the list is being read), a missing job is reported `closed` only after it has been missing for two runs in a row.

#### Company summary record (`recordType: "company_summary"`)

`totalOpenJobs`, `jobsRetrieved`, `jobsMatchingFilters`, `newSinceLastRun`, `closedSinceLastRun`, `netChange`, `trend` (`growing` / `stable` / `shrinking`), `postedLast7Days`, `postedLast30Days`, `newestPostedAt`, `topDepartments`, `topLocations`, `remoteTypeCounts`, `employmentTypeCounts`, `newJobTitlesSample`, `closedJobTitlesSample`, `warnings`.

Company summaries are also saved as one JSON record, `COMPANY_SUMMARIES`, in the run's key-value store. The dataset has three views: **Jobs**, **Company hiring signals**, and **Jobs with descriptions**. A per-company run report (status, counts and error message for each input) is saved as `RUN_REPORT` in the run's key-value store.

#### Per-input statuses in RUN_REPORT

`ok`, `not_found` (the board or career site does not exist; often a stale URL), `robots_disallowed` (the site asks crawlers not to fetch that page, so it was skipped), `unsupported` (no supported job board found), `duplicate`, `error` (network or site problem after retries), `skipped_charge_limit`.

### Pricing (pay per event)

- **$1.50 per 1,000 job records** ($0.0015 per job pushed to the dataset, including jobs labelled `closed`)
- **$0.01 per company summary**

You pay only for results. Examples:

- 10 companies, about 5,000 open jobs with summaries: **≈ $7.60**
- Daily changes-only monitoring of 50 companies (about 300 changed jobs a day plus 50 summaries): **≈ $0.95 per day**
- Summaries only for 100 companies: **$1.00 per run**

Set **Maximum cost per run** in the run options to cap spending. The Actor stops cleanly when the cap is reached and says so in the status message. Companies whose jobs could not all be delivered keep their previous tracking state, so no change is lost; it is delivered on the next run.

### Tips & limits

- **Workday and Oracle need a URL.** Their sites are not addressable by company name. Open the company's "Search jobs" page and copy the URL from your browser.
- **Company-name lookups** check Greenhouse, Lever and Ashby with a few spellings (e.g. `Scale AI` → `scaleai`, `scale-ai`) and pick the board with the most jobs. If the result isn't the board you meant, pass the URL instead.
- **Closed jobs are only reported when the whole board was fetched in both runs.** Use `maxJobsPerCompany: 0` when you track changes.
- **Speed:** in our tests, 11 companies with about 18,900 open jobs took about 2.5 minutes. Listings are fast (about 20 jobs per request on Workday, 200 on Oracle, and the whole board in one request on Greenhouse/Lever/Ashby). Full descriptions on Workday and Oracle need one extra request per job at about 1 per second per site. Use them on filtered or smaller sets.
- **Remote type on Workday** is only known when descriptions are fetched. Oracle often leaves the workplace type blank.
- **Posted dates on Workday** are approximate when descriptions are off (the listing says "Posted 3 Days Ago"; `postedAtText` keeps the original text).
- **Salaries** come from the board's published pay ranges (Greenhouse pay transparency, Ashby compensation). `salaryText` keeps the original wording.
- EU-hosted Greenhouse boards (`job-boards.eu.greenhouse.io`) are not supported yet.
- Contact details are never collected. Recruiter and hiring-manager fields are ignored, and e-mail addresses and phone numbers inside descriptions are masked.

### Use with AI agents / MCP

This Actor is built to be called by AI agents (Grok Bot, Claude, ChatGPT, Cursor, LangChain and others) through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) or the Apify API.

- **Add only this tool:** `https://mcp.apify.com?tools=hirewatch/career-sites-jobs-tracker`. You can also let your agent find it through `search-actors`.
- **Keep calls small so they finish fast.** The MCP `call-actor` tool waits up to 45 seconds, so set `maxItems` (e.g. 50) and `maxJobsPerCompany` (e.g. 100), and leave `includeDescriptions` off unless you need the text. Cap spend with `maxTotalChargeUsd` in `callOptions`.
- **Read results** with `get-dataset-items` using the run's `datasetId`. Each row has `recordType`: `job` rows share one flat schema, and `company_summary` rows hold the hiring signals. Per-company errors are in the `RUN_REPORT` key-value record, so one bad input never fails the whole run.
- **Pay without an Apify account.** The Actor uses pay-per-event pricing with limited permissions, so agents can pay per run with [agentic payments](https://docs.apify.com/agents/payments) (x402 / MPP prepaid tokens or Skyfire).

Minimal agent call:

```json
{
  "targets": [
    "Stripe",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "titleKeywords": [
    "engineer"
  ],
  "maxJobsPerCompany": 100,
  "maxItems": 50,
  "includeCompanySummary": false
}
```

### Other HireWatch jobs Actors

| Actor | Best for |
|---|---|
| [Workday Jobs Scraper](https://apify.com/hirewatch/workday-jobs-scraper) | Workday career sites (`*.myworkdayjobs.com`), including sites with more than 2,000 jobs |
| [Greenhouse Jobs Scraper](https://apify.com/hirewatch/greenhouse-jobs-scraper) | Greenhouse boards by company name or domain, with published salary ranges |
| [Lever Jobs Scraper](https://apify.com/hirewatch/lever-jobs-scraper) | Lever boards (`jobs.lever.co`) by company name or domain, with salaries and remote/hybrid type |
| [Ashby Jobs Scraper](https://apify.com/hirewatch/ashby-jobs-scraper) | Ashby boards (`jobs.ashbyhq.com`), popular with startups and AI companies, with salary ranges |
| [Workday, Greenhouse, Lever, Ashby & Oracle Jobs Scraper](https://apify.com/hirewatch/career-sites-jobs-tracker) | Mixed lists across all five platforms in one run and one schema |
| [Website Tech Stack Detector + DMARC/SPF Checker](https://apify.com/hirewatch/tech-stack-domain-profiler) | Find out what the hiring companies' websites are built with |

All of them use the same output schema and the same new/closed tracking, so you can combine their datasets.

### Is it legal?

This Actor reads only publicly available job postings, which companies publish so they can be found. It does not log in, does not bypass any access control, and follows each site's robots.txt. Job postings are not personal data, but you are responsible for how you use the results. Check the terms of the sites involved and the laws that apply to you. The Actor is not affiliated with or endorsed by Workday, Oracle, Greenhouse, Lever, Ashby, or any company whose jobs it lists. Product names are used only to describe compatibility.

### Support

Found a site that doesn't work, or need another platform (SmartRecruiters, iCIMS, SuccessFactors…)? Open an issue on the Actor's **Issues** tab with the URL. Issues are usually answered within a few days.

# Actor input Schema

## `targets` (type: `array`):

REQUIRED. List of companies to scrape, one per item. Each item is a job-board / career-site URL (Workday, Oracle Recruiting Cloud, Greenhouse, Lever, Ashby), a company careers page that embeds one, a company website domain (e.g. 'stripe.com'), or just a company name (looked up on Greenhouse, Lever and Ashby). Workday and Oracle always need the career-site URL. Optional display name: 'Name | URL'. Example: \["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite", "Stripe"].

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

Stop after this many jobs per company (default 1000). 0 = no limit (fetch the whole board). New/closed tracking is only fully accurate when the whole board is fetched.

## `maxItems` (type: `integer`):

Overall cap on job records this run outputs across all companies (and therefore on cost). 0 = no overall cap. AI agents: set e.g. 50-200 for quick answers.

## `includeDescriptions` (type: `boolean`):

Adds descriptionText and descriptionHtml (e-mails and phone numbers removed). Free for Greenhouse/Lever/Ashby; for Workday and Oracle it needs one extra polite request per job (about 1 job per second per site), so runs are much slower.

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

Only output jobs whose title contains at least one of these words or phrases (case-insensitive), e.g. \["engineer", "data"]. Tracking still covers all jobs.

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

Only output jobs whose location or country contains at least one of these, e.g. \["Remote", "London", "United States"].

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

Only output jobs marked remote. Workday marks remote type only when descriptions are fetched.

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

Only output jobs posted in the last N days (e.g. 7). 0 = any date. Jobs without a posted date are excluded when this is set. Workday only shows approximate dates ('Posted 3 Days Ago', '30+ Days Ago').

## `trackChanges` (type: `boolean`):

Remembers each company's jobs in a named key-value store, so every run labels jobs as new / unchanged / closed. Schedule the Actor (e.g. daily) to get a hiring-change feed.

## `outputMode` (type: `string`):

'allJobs' outputs every open job (plus jobs closed since the last run, labelled). 'changesOnly' outputs just new and closed jobs since the previous run, which is cheaper for daily monitoring.

## `includeBaselineOnFirstRun` (type: `boolean`):

In 'changesOnly' mode the first run just records a baseline and outputs nothing. Turn this on to also get the full list on the first run.

## `includeCompanySummary` (type: `boolean`):

One extra record per company (charged as one 'company-summary' event): total open jobs, new/closed since last run, trend, jobs posted in the last 7/30 days, top departments and locations, remote mix.

## `includeJobs` (type: `boolean`):

Turn off to get only company summaries (cheapest way to monitor hiring at many companies).

## `trackerId` (type: `string`):

Separate change histories for different tasks/schedules that watch the same companies.

## `stateStoreName` (type: `string`):

Named key-value store that keeps the previous run's jobs.

## `requestDelaySecs` (type: `number`):

Polite rate limit per host (minimum 0.5 s). A site's robots.txt Crawl-delay is used when larger.

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

How many companies are fetched at the same time. Requests to any single site are still spaced by the delay above.

## `maxRetries` (type: `integer`):

Retries on timeouts, 429 and 5xx responses, with exponential back-off and Retry-After support.

## Actor input object example

```json
{
  "targets": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
    "https://boards.greenhouse.io/stripe",
    "Palantir",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "maxJobsPerCompany": 200,
  "maxItems": 100,
  "includeDescriptions": false,
  "remoteOnly": false,
  "postedWithinDays": 0,
  "trackChanges": true,
  "outputMode": "allJobs",
  "includeBaselineOnFirstRun": false,
  "includeCompanySummary": true,
  "includeJobs": true,
  "trackerId": "default",
  "stateStoreName": "job-listings-tracker-state",
  "requestDelaySecs": 1,
  "maxConcurrency": 4,
  "maxRetries": 3
}
```

# Actor output Schema

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

No description

## `summaries` (type: `string`):

No description

## `runReport` (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 = {
    "targets": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
        "https://boards.greenhouse.io/stripe",
        "Palantir",
        "https://jobs.ashbyhq.com/ramp"
    ],
    "maxJobsPerCompany": 200,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("hirewatch/career-sites-jobs-tracker").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 = {
    "targets": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
        "https://boards.greenhouse.io/stripe",
        "Palantir",
        "https://jobs.ashbyhq.com/ramp",
    ],
    "maxJobsPerCompany": 200,
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("hirewatch/career-sites-jobs-tracker").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 '{
  "targets": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
    "https://boards.greenhouse.io/stripe",
    "Palantir",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "maxJobsPerCompany": 200,
  "maxItems": 100
}' |
apify call hirewatch/career-sites-jobs-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hirewatch/career-sites-jobs-tracker"
        }
    }
}
```

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/q81deejaoCAlsZLqK/builds/wV2txQQ6qpX4R2yWp/openapi.json
