# Workday Jobs Scraper (`devilscrapes/workday-jobs-scraper`) Actor Scrape job postings from any Workday-powered career site (\*.myworkdayjobs.com) via Workday's own internal JSON API — no login, no browser required. Supply career-site URLs or explicit tenant/dc/site objects; get titles, locations, req IDs, and optional full descriptions. - **URL**: https://apify.com/devilscrapes/workday-jobs-scraper.md - **Developed by:** [DevilScrapes](https://apify.com/devilscrapes) (community) - **Categories:** Jobs - **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.50 / 1,000 results 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
Devil Scrapes mark ## Workday Jobs Scraper **💰 $1.50 / 1 000 results**  ·  pay only for results  ·  no credit card to try *We do the dirty work so your dataset stays clean.* 😈 Scrape job postings from any Workday-powered career site (`*.myworkdayjobs.com`) through Workday's own internal JSON API — no login, no browser, no per-company setup. Feed it career-site URLs and get titles, locations, req IDs, posting dates, and optional full descriptions as clean typed rows.
*** ### 🎯 What this scrapes A huge share of enterprise career sites run on Workday, and every one of them is backed by the same internal JSON endpoint (`/wday/cxs/{tenant}/{site}/jobs`) that the page's own search box calls. This Actor talks to that endpoint directly: point it at one or more Workday career sites — as a URL like `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`, or as an explicit `{tenant, dc, site}` object — and it paginates the full board, optionally fetches each posting's detail, and normalizes everything into one row schema. One scraper, every Workday tenant. ### 🔥 Features - 🛡️ **Browser fingerprint impersonation** — `curl-cffi` presents a real Chrome TLS/H2 handshake, so the endpoint sees a browser, not a bare Python client. Workday sits behind Cloudflare; a convincing fingerprint is what keeps requests flowing. - 🔁 **Retries with exponential backoff** on `408 / 429 / 5xx`, up to 5 attempts, `Retry-After` honoured — a batch that hits a blip recovers instead of crashing mid-run. - 🌐 **Proxy session rotation** via Apify Proxy — a fresh exit IP when you're pulling many tenants or deep boards. - 🏢 **One schema across every tenant** — mix career-site URLs and `{tenant, dc, site}` objects in a single run (up to 1 000); rows come back identically shaped, tagged with `company`, `dc`, and `site`. - 📝 **Optional full descriptions** — flip `includeDescription` on for the complete posting body plus start date, time type, and req ID; leave it off for a fast titles-and-locations pull. - 🧊 **Clean, typed rows** — Pydantic-validated, ISO-8601 timestamps, stable IDs. Export JSON / CSV / Excel straight from the Apify Console. ### 💡 Use cases - **Recruiting & talent intelligence** — track what a target employer is hiring for, where, and how fast their reqs turn over. - **Job-board aggregation** — add Workday coverage alongside Greenhouse / Lever / Ashby, pulling fresh postings from dozens of employers in one run. - **Labor-market research** — sample hiring demand across an industry by role, location, or time type. - **Competitive hiring intel** — watch a competitor's open reqs to infer team growth and roadmap direction. - **ATS data pipelines** — wire structured job rows into your own CRM, dashboard, or n8n / Make workflow on a schedule. ### ⚙️ How to use it 1. Click **Try for free** at the top of the Store listing. 2. Add one or more **Career sites** — a bare URL like `nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`, or a `{tenant, dc, site}` object. 3. Optionally set **Search text**, a **Location filter**, **Max results per site** (`0` = all), and toggle **Include description**. 4. Click **Start**. Rows stream into the dataset as each site paginates. 5. Export from **Storage → Dataset** as JSON, CSV, or Excel — or pull via the Apify API. ### 📥 Input | Field | Type | Required | Default | Notes | |---|---|:--:|---|---| | `careerSites` | `array` | ✅ | — | 1–1000 Workday career-site URLs or `{tenant, dc, site}` objects. Mix freely. | | `searchText` | `string` | no | `null` | Free-text keyword passed verbatim to Workday's own search. | | `locationFilter` | `string` | no | `null` | Human-readable location, matched against each tenant's live facet tree. | | `maxResultsPerSite` | `integer` | no | `0` | Cap rows emitted per site; `0` = all. | | `includeDescription` | `boolean` | no | `false` | Fetch each posting's full description + start date + time type + req ID (one extra call per job). | | `proxyConfiguration` | `object` | no | `{"useApifyProxy": true}` | Apify Proxy configuration. | #### Example input ```json { "careerSites": [ "nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite" ], "maxResultsPerSite": 25, "includeDescription": true, "proxyConfiguration": { "useApifyProxy": true } } ``` ### 📤 Output One dataset item per job posting. Fields marked **(detail)** are populated only when `includeDescription` is on. | Field | Type | Notes | |---|---|---| | `job_id` | `string` | Workday `externalPath`; unique within one company / dc / site. | | `title` | `string` | Job title. | | `location` | `string \| null` | Primary listed location. | | `additional_locations` | `array` | Extra locations **(detail)**. | | `posted_on_text` | `string \| null` | Workday's relative "Posted On" label, e.g. `Posted Today`. | | `start_date` | `string \| null` | ISO `YYYY-MM-DD` **(detail)**. | | `time_type` | `string \| null` | e.g. `Full time` **(detail)**. | | `job_req_id` | `string \| null` | Employer requisition ID **(detail)**. | | `url` | `string` | Canonical public posting URL. | | `company` | `string` | Tenant, lowercased. | | `dc` | `string` | Workday data-center shard, e.g. `wd5`. | | `site` | `string` | Career-site path segment. | | `description_html` | `string \| null` | Full posting body **(detail)**. | | `scraped_at` | `string` | UTC ISO-8601 fetch timestamp. | #### Example output ```json { "job_id": "/job/US-CA-Santa-Clara/Senior-Factory-Support-Firmware-Engineer_JR1998421", "title": "Senior Factory Support Firmware Engineer", "location": "US, CA, Santa Clara", "additional_locations": [], "posted_on_text": "Posted 5 Days Ago", "start_date": null, "time_type": "Full time", "job_req_id": "JR1998421", "url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Factory-Support-Firmware-Engineer_JR1998421", "company": "nvidia", "dc": "wd5", "site": "NVIDIAExternalCareerSite", "description_html": "NVIDIA is seeking a Senior Factory Support Firmware Engineer...", "scraped_at": "2026-07-21T11:40:00Z" } ``` ### 💰 Pricing Pay-Per-Event — you're charged only when these fire: | Event | USD | What it covers | |---|---:|---| | `actor-start` | $0.005 | One-off warm-up per run | | `result` | $0.0015 | Per job posting written to the dataset | **Example**: 1 000 postings ≈ **$1.51**. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit. ### 🚧 Limitations - **Public career sites only** — external Workday career sites, not SSO/authenticated internal portals. - **No salary/compensation field** — Workday doesn't expose structured comp data, so we don't invent it. - **Descriptions cost an extra fetch** — `includeDescription` adds one detail request per posting (it changes speed, not the per-result price). Leave it off for the fastest pull. - **Point-in-time snapshot** — returns the board as it stands now; schedule recurring runs to track changes over time. ### ❓ FAQ **Do I need a Workday account or API key?** No — every field comes from the same public JSON endpoint the career-site search box already calls. **Does one run handle several companies?** Yes. Put multiple career sites in `careerSites` (URLs and `{tenant, dc, site}` objects can be mixed) and every row comes back identically shaped, tagged with `company` / `dc` / `site`. **How do I find a company's tenant and data center?** They're in the career-site URL: `https://{tenant}.{dc}.myworkdayjobs.com/{site}`. Paste that URL directly — no need to split it yourself. **Why doesn't `maxResultsPerSite` change the price?** You're charged per row written, not per HTTP call — so turning on descriptions (extra calls) or capping results doesn't change the per-result rate. **Is this legal?** We fetch public, unauthenticated job-posting data that employers publish for candidates to browse. No login, no private endpoints. ### 💬 Your feedback Spotted a bug, hit a tenant that behaves differently, or need an extra field? Open an issue on the Actor's **Issues** tab in Apify Console — we ship fixes weekly and read every report. ***
Built by **[Devil Scrapes](https://apify.com/DevilScrapes)** 😈 — a small fleet of opinionated public-data Actors. Honest pricing, real engineering, zero fine print.
### 🔗 Related Devil Scrapes Actors Hiring intel across the whole ATS landscape? These siblings cover the other major job-board platforms — same keyless, pay-per-result approach: - [SmartRecruiters Jobs Scraper](https://apify.com/DevilScrapes/smartrecruiters-jobs-scraper) — postings from any SmartRecruiters-hosted employer - [Workable Jobs Scraper](https://apify.com/DevilScrapes/workable-jobs-scraper) — postings from any Workable-hosted employer board - [Multi-ATS Jobs Scraper](https://apify.com/DevilScrapes/multi-ats-jobs-scraper) — one normalized feed across Greenhouse, Lever & Ashby Browse the full fleet at [apify.com/DevilScrapes](https://apify.com/DevilScrapes). # Actor input Schema ## `careerSites` (type: `array`): List of Workday career sites to scrape. Each entry may be a URL, e.g. "nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite" (tenant/dc/site are parsed from the host and path), or an explicit object {"tenant": "nvidia", "dc": "wd5", "site": "NVIDIAExternalCareerSite"} that skips URL parsing entirely. ## `searchText` (type: `string`): Free-text query, passed verbatim as Workday's own searchText on every page. Leave empty to return every posting. ## `locationFilter` (type: `string`): Human-readable location, e.g. "Austria" or "Remote". Resolved per-site against that site's own live facet tree (case-insensitive substring match). Leave empty to skip. ## `maxResultsPerSite` (type: `integer`): Cap job postings collected per careerSites entry, applied after locationFilter/searchText narrowing. Set to 0 (default) to collect all available postings. ## `includeDescription` (type: `boolean`): When enabled, fetch the full job description (HTML) plus start date, time type, requisition ID, and additional locations for every emitted job. Doubles HTTP calls per job. ## `proxyConfiguration` (type: `object`): Apify Proxy configuration. No anti-bot behaviour has been observed on Workday's public career-site API, so the standard (non-residential) group is enough. ## Actor input object example ```json { "careerSites": [ "nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite" ], "maxResultsPerSite": 0, "includeDescription": false, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `datasetItems` (type: `string`): All dataset items as JSON. ## `datasetItemsCsv` (type: `string`): Same data exported to CSV. ## `datasetView` (type: `string`): Open the run dataset in the Console. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "careerSites": [ "nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite" ], "maxResultsPerSite": 0, "includeDescription": false, "proxyConfiguration": { "useApifyProxy": true } }; // Run the Actor and wait for it to finish const run = await client.actor("devilscrapes/workday-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "careerSites": ["nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"], "maxResultsPerSite": 0, "includeDescription": False, "proxyConfiguration": { "useApifyProxy": True }, } # Run the Actor and wait for it to finish run = client.actor("devilscrapes/workday-jobs-scraper").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 '{ "careerSites": [ "nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite" ], "maxResultsPerSite": 0, "includeDescription": false, "proxyConfiguration": { "useApifyProxy": true } }' | apify call devilscrapes/workday-jobs-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=devilscrapes/workday-jobs-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/acts/IYlcd8fcqxstNGT8v/builds/8sbZQNVgb7IQKKOMX/openapi.json