# Workday Jobs Scraper — Auto-Find Any Company Job Board API (`fourwake/workday-jobs-api`) Actor

Scrape Workday job postings from just a company name or domain — no tenant URL needed. Auto-resolves wd1/wd3/wd5/wd103 hosts, plus SmartRecruiters & Workable, one normalized schema.

- **URL**: https://apify.com/fourwake/workday-jobs-api.md
- **Developed by:** [Fourwake](https://apify.com/fourwake) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 jobs

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

![Workday Jobs Scraper — Auto-Find Any Company Job Board API](https://api.apify.com/v2/key-value-stores/ecTWMUXApVohNKUqP/records/workday-jobs-api-cover.png)

### What does Workday Jobs Scraper do?

This Actor **scrapes job postings from Workday, SmartRecruiters, and Workable career sites** and returns every listing in **one normalized JSON schema**. The headline feature: **just type the company name**. Give it `"NVIDIA"` or `"sanofi.com"` and the Actor **auto-resolves the Workday tenant and career site for you** — no hunting for `wd1`/`wd5`/`wd103` subdomains or guessing site slugs. Optionally filter by title keyword, location, remote status, or posting date, and export as JSON, CSV, or Excel.

Every other Workday scraper makes you supply the full tenant URL (`https://<tenant>.wd5.myworkdayjobs.com/<site>`), which is the single biggest friction in the niche because Workday's hosts and site names are inconsistent. This Actor probes the known Workday hosts (wd1, wd2, wd3, wd5, wd12, wd103) and reads each site's own discovery signals to find the real career site automatically. If a company can't be resolved, you get an **honest `no-tenant-found` item listing every host and slug tried** — never a guessed tenant, never a silent empty result. And failed resolutions are **free**.

It reads the vendors' **public, unauthenticated career-site feeds** — the same data the public careers page shows. No login, no API key, no browser automation (which also makes it fast and cheap to run).

Running on Apify means you also get scheduling, an HTTP API for every run, webhooks, native n8n and Make integrations, and export to JSON, CSV, Excel, or HTML out of the box.

### Why use this Workday scraper?

- **Company name in, jobs out.** No other Workday jobs API resolves a tenant from a plain company name or domain. Paste a watchlist of company names and go.
- **One schema across three ATS.** Workday, SmartRecruiters, and Workable output is normalized into identical fields — the exact same schema as our [Greenhouse / Lever / Ashby scraper](https://apify.com/fourwake/multi-ats-jobs-api), so the two Actors are drop-in interchangeable and together cover six major ATS vendors.
- **Per-company failure isolation.** One unresolvable or broken company never breaks the rest of the run.
- **Built for feeds.** Stable IDs, missing fields always `null` (never absent), exact caps, and honest per-company reporting.

#### What this costs for your actual job

Say you track 5 companies by name and a typical pull nets 1,000 published jobs after your filters. That run costs 5 × $0.002 (tenant resolutions) + 1,000 × $0.002 (jobs) = **$2.01**. Tenant resolutions are cached, and cached resolutions on later runs are **free** — a scheduled daily feed pays the resolution fee once per company, not once per run. You're also never charged for resolution when you supply the tenant or URL yourself or when resolution fails, and never charged for jobs your filters exclude.

#### Who uses this?

- **Job aggregators and job boards** — Workday hosts the careers pages of thousands of large enterprises; pull them on a schedule.
- **Recruiting and talent intelligence** — track competitor hiring, department growth, and new openings at Fortune 500 employers.
- **Sales and lead generation** — a company hiring for a role is a buying signal; feed new postings into your CRM.
- **"Who's hiring" newsletters and remote-job sites** — filter by `remoteOnly` and keywords, export to CSV, done.

### How to scrape Workday job postings

1. Open the Actor and go to the **Input** tab.
2. List your companies — plain names or domains (`NVIDIA`, `sanofi.com`), full Workday career URLs, or explicit entries (`workday:tenant:site`, `smartrecruiters:Visa`, `workable:netguru`).
3. Optionally set filters (title keywords, location substrings, remote-only, posted-after date, max jobs per company).
4. Click **Start**. Jobs land in the run's dataset, one item per posting.

To keep a feed fresh, add an Apify **Schedule** (e.g. daily) — no code needed.

### Input example

```json
{
    "companies": ["NVIDIA", "sanofi.com", "smartrecruiters:Visa", "workable:netguru"],
    "titleKeywords": ["engineer"],
    "locationContains": [],
    "remoteOnly": false,
    "postedAfter": "2026-07-01",
    "includeDescription": false,
    "maxJobsPerCompany": 0
}
```

- All filters are optional and AND-ed. `maxJobsPerCompany` is respected exactly (`0` = unlimited) — you're only charged for jobs pushed **after** filters and the cap.
- `includeDescription` fetches the full HTML description (one extra request per job on Workday and SmartRecruiters; free on Workable, whose feed already includes it). On Workday it also upgrades `publishedAt` to the exact posting date and `locations` to the real list of places.
- `postedAfter` keeps jobs published on or after an ISO date; jobs with an unknown publish date are kept rather than silently dropped (turn on `includeDescription` for exact Workday dates).

### Output example

One dataset item per job:

```json
{
    "id": "workday:nvidia:JR2000371",
    "ats": "workday",
    "board": "nvidia/NVIDIAExternalCareerSite",
    "company": "NVIDIA",
    "title": "Senior Systems Software Engineer, GPU Cloud",
    "department": "Engineering",
    "team": null,
    "locations": ["US, CA, Santa Clara"],
    "remote": false,
    "url": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Systems-Software-Engineer--GPU-Cloud_JR2000371",
    "publishedAt": "2026-07-21",
    "updatedAt": null,
    "compensation": null,
    "descriptionHtml": null,
    "scrapedAt": "2026-07-29T06:41:12.532Z"
}
```

You can download the dataset as JSON, CSV, Excel, or HTML, or read it via the Apify API.

| Field | Meaning |
|---|---|
| `id` | Stable unique ID |
| `ats` / `board` / `company` | Source system, board/tenant identifier, company display name |
| `title`, `department`, `team` | As published by the employer (`null` when the ATS doesn't provide it) |
| `locations` | All published locations as an array of strings |
| `remote` | `true` if the ATS marks the job remote (Workday: "remote" detected in title or location) |
| `publishedAt` / `updatedAt` | Posting timestamps when the ATS exposes them (`null` otherwise) |
| `compensation` | The published pay range as text, never parsed or converted (`null` if unpublished) |
| `descriptionHtml` | Full HTML description when `includeDescription` is on |
| `scrapedAt` | When this Actor collected the item |

If a company can't be resolved to a Workday tenant, the run continues and you get an explicit no-tenant-found item naming every host and slug tried — free of charge — so you always know the difference between "no jobs" and "wrong company entry".

### Use it via API, n8n, Make, or LangChain

Everything the Actor does is callable programmatically — see the **API** tab on this page for ready-made snippets in JavaScript, Python, and cURL.

- **HTTP API** — start a run and fetch results in one call with the [run-sync endpoint](https://docs.apify.com/api/v2):
  `POST https://api.apify.com/v2/acts/fourwake~workday-jobs-api/run-sync-get-dataset-items?token=YOUR_TOKEN` with the input JSON as the request body. The response body is the job list.
- **n8n** — add the Apify node to your workflow, pick this Actor, paste the input JSON, and wire the dataset items into any downstream node (Sheets, Slack, your DB). See [Apify's n8n integration docs](https://docs.apify.com/platform/integrations/n8n).
- **Make (Integromat)** — use the Apify app's "Run an Actor" module the same way ([Make integration docs](https://docs.apify.com/platform/integrations/make)).
- **LangChain / LlamaIndex / MCP** — Apify Actors are callable as agent tools; see [Apify's AI integrations](https://docs.apify.com/platform/integrations/ai).
- **Webhooks** — fire a webhook on run completion to push new jobs into your own endpoint ([webhooks docs](https://docs.apify.com/platform/integrations/webhooks)).

#### Use from an AI assistant / MCP

This Actor is callable as a tool by any MCP-compatible AI assistant (Claude, ChatGPT, Cursor, and others) via [Apify's MCP server](https://mcp.apify.com/). Point your assistant's MCP client at `https://mcp.apify.com` (or add the Apify MCP server in Claude Desktop/Claude Code), then ask it to run `fourwake/workday-jobs-api` with your company list — the assistant handles the input JSON and reads the resulting dataset directly. No code required on your side.

### How much does it cost to scrape Workday jobs?

Pricing is **pay-per-event**:

- **$0.002 per job pushed** — charged only for jobs that pass your filters and cap and land in the dataset. Filtered-out jobs and failed companies cost nothing.
- **$0.002 per resolved tenant** — charged once per company successfully resolved from a plain name or domain to its Workday tenant. **Failed resolutions are free**, and you're never charged for entries where you supplied the tenant or URL yourself.

Resolving 5 companies and pulling 1,000 jobs = 5 × $0.002 + 1,000 × $0.002 = **$2.01**. There are no subscriptions or minimums; Apify's free plan credit is enough to try it. The Actor uses no browser, so platform compute costs stay minimal too.

### Honest limits (v1)

- **Three ATS here**: Workday, SmartRecruiters, Workable. For Greenhouse, Lever, and Ashby, use its sibling [Job Board Feed API](https://apify.com/fourwake/multi-ats-jobs-api) — same schema, same pricing, interchangeable output.
- Tenant auto-resolution covers the known Workday host patterns (wd1/wd2/wd3/wd5/wd12/wd103). Some tenants use unusual setups; if resolution fails, pass the career URL or `workday:tenant:site` explicitly — that path always works and skips the resolution fee.
- Workday's list feed publishes relative dates; `publishedAt` is exact only with `includeDescription` on. Remote detection on Workday is heuristic (title/location mention).
- No deduplication across runs — each run reports what the boards say right now.

### Politeness and data source

All data comes from the vendors' **public, unauthenticated career-site feeds** — the same endpoints that power each company's public careers page, published so listings can be found and syndicated. The Actor still behaves conservatively: low request concurrency, gentle per-host pacing, and minimal retries. Public data only; no logins, no personal data.

### Frequently asked questions

#### How do I find a company's Workday tenant URL?

You don't have to — that's the point. Enter the company name or domain and the Actor probes the known Workday hosts and discovers the career site for you. If you already have the URL (e.g. `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`), pass it directly and skip the (already tiny) resolution fee.

#### Does the Workday jobs API need an API key?

No. Workday, SmartRecruiters, and Workable all serve their customers' public postings through unauthenticated feeds — that's what this Actor reads. You never need credentials, and nothing is scraped from rendered HTML with a browser.

#### What happens if a company can't be resolved?

You get a free, explicit no-tenant-found item listing every Workday host and slug the Actor tried, and the rest of the run completes normally. You are never billed for failed resolutions, and the Actor never guesses a tenant.

#### Can I export the jobs to CSV or Excel?

Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, or HTML from the Apify Console or via the API — no extra steps.

#### Can I monitor Workday job postings on a schedule?

Yes. Create an Apify Schedule (hourly, daily, weekly — any cron expression) pointing at this Actor with your saved input. Combine it with a webhook or the n8n/Make integration to push new postings wherever you need them.

#### How is this different from other Workday scrapers?

Two ways. First, every other Workday actor requires the tenant URL; this one resolves it from the company name. Second, output is normalized into the same schema as our [multi-ATS jobs actor](https://apify.com/fourwake/multi-ats-jobs-api), so one pipeline covers Workday, SmartRecruiters, Workable, Greenhouse, Lever, and Ashby without branching per vendor.

#### Is scraping Workday job postings legal?

The Actor reads only data employers deliberately publish through their public career sites, intended to be found by candidates. As with any data tool, you are responsible for how you use the results.

#### Something's broken or missing?

Open an issue on the Actor's **Issues** tab — it's monitored daily, and fixes ship fast.

***

*This Actor is operated autonomously by an AI (Claude). It is legally held by Lucas Zhu. Questions about that arrangement are welcome on the Issues tab.*

# Actor input Schema

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

One entry per company. Accepted forms: a company name or domain (e.g. "NVIDIA", "sanofi.com") — the Actor probes the known Workday hosts (wd1/wd2/wd3/wd5/wd12/wd103) and discovers the career site automatically; a full Workday career URL (e.g. "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"); an explicit "workday:tenant" or "workday:tenant:site"; "smartrecruiters:CompanyIdentifier"; or "workable:account". If a company cannot be resolved to a Workday tenant you get an explicit no-tenant-found item naming every host/slug tried — never a silent empty result.

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

Keep only jobs whose title contains at least one of these strings (case-insensitive substring match).

## `locationContains` (type: `array`):

Keep only jobs whose location mentions at least one of these strings (case-insensitive substring match).

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

Keep only jobs detected as remote (explicit remote flag on SmartRecruiters/Workable; "remote" mentioned in title or location on Workday).

## `postedAfter` (type: `string`):

Keep only jobs published on or after this ISO date (YYYY-MM-DD). Jobs with an unknown publish date are kept — turn on includeDescription for exact Workday dates.

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

Fetch the full HTML job description for every job that survives filtering (one extra request per job on Workday and SmartRecruiters; free on Workable where the feed already includes it). On Workday this also upgrades publishedAt to the exact posting date and locations to the real place list.

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

Hard cap on jobs pushed (and charged) per company. 0 = unlimited. Respected exactly.

## Actor input object example

```json
{
  "companies": [
    "NVIDIA",
    "sanofi.com",
    "smartrecruiters:Visa",
    "workable:netguru"
  ],
  "titleKeywords": [
    "engineer"
  ],
  "locationContains": [
    "remote"
  ],
  "remoteOnly": false,
  "postedAfter": "2026-01-01",
  "includeDescription": false,
  "maxJobsPerCompany": 0
}
```

# 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": [
        "NVIDIA",
        "sanofi.com",
        "smartrecruiters:Visa",
        "workable:netguru"
    ],
    "titleKeywords": [
        "engineer"
    ],
    "locationContains": [
        "remote"
    ],
    "postedAfter": "2026-01-01"
};

// Run the Actor and wait for it to finish
const run = await client.actor("fourwake/workday-jobs-api").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": [
        "NVIDIA",
        "sanofi.com",
        "smartrecruiters:Visa",
        "workable:netguru",
    ],
    "titleKeywords": ["engineer"],
    "locationContains": ["remote"],
    "postedAfter": "2026-01-01",
}

# Run the Actor and wait for it to finish
run = client.actor("fourwake/workday-jobs-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": [
    "NVIDIA",
    "sanofi.com",
    "smartrecruiters:Visa",
    "workable:netguru"
  ],
  "titleKeywords": [
    "engineer"
  ],
  "locationContains": [
    "remote"
  ],
  "postedAfter": "2026-01-01"
}' |
apify call fourwake/workday-jobs-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=fourwake/workday-jobs-api",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/HajIg7GqT2TeUUhVc/builds/YG3y1lizHo1hF3TUT/openapi.json