Workday Jobs Scraper
Pricing
from $2.50 / 1,000 open jobs
Workday Jobs Scraper
Extract public Workday jobs from myworkdayjobs careers URLs. Get descriptions, locations, requisition IDs, published salary evidence and application links. Read source facets beyond capped lists and compare complete snapshots.
Workday Jobs Scraper: Descriptions, Salary & Job Changes
Turn public myworkdayjobs careers-site URLs into current vacancies with descriptions, job IDs, requisition IDs, locations, published salary evidence and application links. Read source facets beyond capped lists and compare complete snapshots.
$0.0025 per job with descriptions ($2.50 per 1,000), or $0.002 without descriptions ($2 per 1,000). Failed jobs and change notes have no job charge. The prefill samples up to 20 jobs from one large public Workday board, subject to its spending limit.
Smallest input: {"boards":[{"board":"example-employer/wd5/PublicJobs"}],"maxResults":1,"maxChargeUsd":0.00255}. Replace the example board with your chosen Workday careers site. provider defaults to workday.
What you get
| Field | What it holds |
|---|---|
| verdict | A plain sentence describing the job or why no data was returned. |
| provider, board, jobId, resultId | Source identity and a stable delivery ID. Duplicate inputs and migrated deliveries are not charged twice. |
| company, locations, remoteType, employmentType | Published metadata only. Company is null where the feed does not name it. Workplace is Unknown unless a source workplace/location label establishes it. |
| tenant, site, shard, requisitionId, locationSummary, country, workplaceLabel, postedOn, detailStatus | Additional source fields where available. Workday keeps the original workplace label and relative posting text; it does not turn ambiguous labels into a remote-work claim. |
| descriptionText | Published description with HTML formatting removed. Contact blocks, email addresses and phone numbers are removed. |
| salaryText, salaryMin, salaryMax, salaryCurrency, salaryPeriod, salarySource | Source evidence. Missing values remain null. Multiple pay ranges stay in the text; a bare dollar sign does not prove USD. |
| publishedAt, updatedAt, jobUrl, applyUrl, sourceUrl, observedAt | Published dates where available, job/application links and observation time. Links are returned, never submitted. |
| changeType, snapshotComplete | Optional baseline/opened/updated/unchanged/reopened labels and free closure notes, only for complete comparable runs. |
| SUMMARY | Delivered and charged counts, free notes, duplicates, skipped boards, source failures, coverage and limits. |
What people use it for
- Job-board feeds: Refresh vacancies for a known list of employers.
- Recruiting-data workflows: Normalize seven public ATS feeds without collecting people or applicant data.
- Vacancy monitoring: Compare sequential complete snapshots with the same namespace and filter.
How to use it
- Paste a public Workday careers-site URL into urls, or use boards with tenant/wdN/site. Optional locale paths are accepted. The input form has a prefill that samples up to 20 jobs subject to its spending limit.
- Choose a total result cap and spending limit. The lower of maxChargeUsd and Apify Maximum cost per run applies.
- Run the Actor and open Jobs and notes. Check SUMMARY for coverage before using the data as a complete feed.
Input
| Field | Example | Notes |
|---|---|---|
| boards | [{"board":"example-employer/wd5/PublicJobs"}] | provider defaults to workday. Supply tenant/wdN/site or a Workday careers-site URL. Up to 20 unique boards. Other providers from the shared ATS engine require an explicit provider. |
| urls | ["https://careers.example.test/PublicJobs"] | Use a real supported careers-site URL. Workday locale paths are accepted. Individual jobs, employer homepages and login URLs are rejected. url and startUrls are aliases. |
| query | engineer | One case-insensitive literal filter over titles and fetched descriptions. Workday, SmartRecruiters and Workable filter titles only when descriptions are off. Selective filters can reach source limits. |
| maxResults | 20 | Global maximum, 1–10,000. A truncated result set cannot establish closures. |
| maxJobsPerBoard | 10000 | Optional per-board maximum. Use a small cap to sample every input board; a truncated board cannot establish closures. |
| includeDescriptions | true | Workday, SmartRecruiters and Workable fetch one detail per job when true. False skips those requests; detail-only fields and description-derived pay are unavailable. Other feeds include descriptions in the list response. |
| snapshotKey | example-monitor | Optional namespace in a private named key-value store in your account. Use the same value for sequential runs. |
| maxChargeUsd | 0.04 | Zero makes no source requests. Repeated jobs in a new run are paid current rows, including unchanged jobs. |
Output
Each result is one row in the run's dataset (download it as JSON, CSV, Excel, XML or HTML, or read it through the API). An example row (values shortened):
{"verdict": "Open vacancy: Mechanical Engineer.","recordType": "job","resultId": "job-example-id","provider": "workday","board": "example-employer/wd5/PublicJobs","region": "global","tenant": "example-employer","site": "PublicJobs","shard": "wd5","jobId": "JR2027384","requisitionId": "JR2027384","title": "Mechanical Engineer","company": "Example Employer","locations": ["Israel, Yokneam"],"locationSummary": "Israel, Yokneam","country": "Israel","remoteType": "Unknown","workplaceLabel": null,"employmentType": "Full time","descriptionText": null,"salaryText": null,"salaryMin": null,"salaryMax": null,"salaryCurrency": null,"salaryPeriod": null,"salarySource": null,"publishedAt": "2026-10-25T00:00:00","updatedAt": null,"postedOn": "Posted Today","jobUrl": "https://careers.example.test/jobs/example-job","applyUrl": "https://careers.example.test/jobs/example-job","detailSourceUrl": "https://careers.example.test/api/jobs/example-job","detailStatus": "fetched","changeType": null,"snapshotComplete": false,"status": "open","sourceUrl": "https://careers.example.test/api/jobs","observedAt": "2026-10-25T15:39:54Z"}
This example is based on a real 20-job Workday run on 25 October 2026. Employer names, board/site identifiers and site addresses are replaced. The description is omitted from this shortened example; the run returned it. SUMMARY records delivered and charged jobs, free notes, failures, source totals, facet coverage and limits. The first output column is verdict.
Pricing
- $0.0025 per job with includeDescriptions true (Open job); $0.002 per job with includeDescriptions false (Job without description). The price is selected by the input setting. Notes and changes are free.
- The same price on every Apify plan. No board, salary or change-report fee. Failed jobs, input notes, source-failure notes and closures have no job charge.
- Apify adds its standard $0.00005 start charge per run at the default memory setting. It counts towards the buyer’s Maximum cost per run.
- A new run charges for current jobs again, including unchanged jobs. When Apify restarts the same run, jobs already in its dataset are skipped and are not charged again.
What typical jobs cost at the list price:
| Job | Cost |
|---|---|
| 1 job with description | $0.0025 |
| 20 jobs with descriptions | $0.05 |
| 1,000 jobs with descriptions | $2.50 |
| 1,000 jobs without descriptions | $2 |
| Failed or empty board | $0 in job charges |
The lower of maxChargeUsd and Apify Maximum cost per run applies. Apify’s $0.00005 start charge counts towards Maximum cost per run; allow it in addition to the jobs you want. Free notes remain available after the limit. Source work stops when there is no room for another paid job.
Tips
- For complete comparisons, allow enough results and budget for every matching vacancy across every board.
- Reuse snapshotKey with unchanged boards, provider regions, filter and description setting. A changed scope creates a new baseline without reporting closures.
- Schedule each snapshot namespace sequentially. Concurrent runs with the same namespace are unsupported because the snapshot store is not a transactional lock.
Use it through the API
Python
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("zaiq/workday-jobs-scraper").call(run_input={"boards": [{"board": "example-employer/wd5/PublicJobs"}], "maxResults": 20, "maxChargeUsd": 0.04, "includeDescriptions": true})for row in client.dataset(run.default_dataset_id).iterate_items():print(row)
JavaScript
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });const run = await client.actor('zaiq/workday-jobs-scraper').call({"boards": [{"board": "example-employer/wd5/PublicJobs"}], "maxResults": 20, "maxChargeUsd": 0.04, "includeDescriptions": true});const { items } = await client.dataset(run.defaultDatasetId).listItems();
HTTP (one call, results back)
curl -X POST 'https://api.apify.com/v2/acts/zaiq~workday-jobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>' \-H 'Content-Type: application/json' \-d '{"boards": [{"board": "example-employer/wd5/PublicJobs"}], "maxResults": 20, "maxChargeUsd": 0.04, "includeDescriptions": true}'
Integrations and schedules
- Schedules: run it every hour, day or week from the Apify Console (Schedules) and keep a history of results.
- Make, Zapier, n8n, Google Sheets, Slack, Airtable: connect it through Apify's integrations, or send each finished run to a webhook.
- Datasets: results stay in the run's dataset; export them or read them by API whenever you need them.
Use it with AI agents (MCP)
Add Apify's MCP server (https://mcp.apify.com) to Claude, ChatGPT, Cursor, VS Code or any MCP client. The agent can find this Actor and run it for you: ask it for "read these public ATS boards and return their current vacancies". AI agents can also pay for runs directly through Apify's agentic payments.
Limits
- Reads signed-out public postings only. No applications, applicant records, account access, private jobs or employer discovery. Supply supported ATS-hosted board URLs; custom employer domains are not discovered automatically.
- Workday sites can clip a result set at exactly 2,000. Larger scans split using the site’s own returned facets, including nested facets where necessary. A run that encounters the cap remains incomplete for snapshot purposes even if all returned facet buckets are read. Missing or changing facets, repeated pages and source limits cannot prove a closure.
- Up to 20 boards, 10,000 delivered jobs, and 10,000 jobs per board. Responses are limited to 24 MB of decoded JSON. Original Greenhouse, Lever and Ashby feeds retain a 24 MB per-board limit, 60 seconds per board and 240 seconds of source time. The newer providers allow up to 720 seconds of source time and 20,000 requests per run; a Workday board allows up to 600 seconds. Requests time out after 30 seconds. Large runs may need more than one run; SUMMARY states what was covered.
- Workday, SmartRecruiters, Workable and Recruitee try direct access, then an Apify datacenter address and up to two fresh residential sessions for address refusals. Original providers retain direct/datacenter routing. No challenge is solved and no login or redirect is followed. HTTP 429 stops that host for the rest of the run.
- For residential fallback, Workday needs room for at least 3 jobs from that board and Recruitee needs room for at least 10. Query-filtered runs use direct/datacenter access only. If those routes are refused, a smaller or filtered request returns a free note; raise the job and spending caps or remove the filter to allow the fallback.
- A requested detail that fails is a free failure note, not a charged metadata substitute. Repeated detail failures stop that board. With descriptions off, published dates, employment type, company and salary can be null when available only on detail pages.
- snapshotComplete means every requested board was read successfully and all matching jobs fit the limits. Capped lists, failed details, repeated pages, changed totals and run limits keep the previous baseline and produce no closure notes. A changed input scope starts a new baseline.
- Source responses are reused within a restarted run, so a restart continues that run’s observed data. A fresh run reads current postings again. Stable Workday IDs combine provider, tenant, site and posting ID; moving shards or changing the title slug does not change the delivery ID.
- Company and employment fields can be null where the source omits them. Remote work is not inferred from benefits text. Ambiguous workplace labels are preserved separately. Salary figures are not guessed, converted or annualised.
- Descriptions have HTML and recognizable contact blocks, emails and phone numbers removed. Complex salary ranges remain source text. Snapshot data stays in a private named store in your account; schedule each namespace sequentially. The most recent 50,000 closed IDs support reopen recognition.
FAQ
Can I search for every employer hiring a role?
No. Supply public boards or their supported URLs. query filters those boards only.
Does a missing job always mean closed?
No. A closure note requires two complete successful snapshots with the same scope. Partial or failed runs keep the baseline.
Do unchanged jobs cost money on the next scheduled run?
Yes. Every new run delivers current jobs at the per-job price. Change notes have no additional charge.
Why is company or salary null?
The feed did not supply enough explicit evidence. Board slugs are not presented as verified company names, and missing pay is not inferred.
Does it apply for jobs?
No. It returns published links and never sends an application or reads applicant data.
Why does Workday show 2,000 jobs?
Some sites cap their reported list. This Actor reads available facet partitions for larger scans and explicitly marks the run incomplete for closure comparisons. It never equates a capped total with the complete board.
Can I paste a localized careers URL?
Yes. Workday careers-site URLs with a locale path are accepted. The API may return its default language; translated output is not requested or guaranteed.
Why can an employer have several IDs for a requisition?
A requisition can have several public postings. Each source posting is kept separately; requisitionId lets you group them without discarding locations or posting variants.
Related Actors from Zaiq
- ats-jobs-scraper: one dataset from seven public ATS systems
Support
Questions, a site that changed, or a field you need? Open an issue on this Actor's Issues tab: we answer there, usually within a day.
Also found as: workday jobs, workday scraper, myworkdayjobs, workday jobs scraper, workday API, workday careers scraper, workday job descriptions, workday requisition IDs, job change tracker.