The largest enterprise career system, with no public API and twenty results per page: the hardest source we maintain.
The official route
Workday exposes no public job board API. Every customer career site is rendered by a front end that calls an internal endpoint, /wday/cxs/{tenant}/{site}/jobs, with a POST. It requires no key, but it is not documented, not supported, capped at 20 results per page, and different for every tenant: each company has its own host, tenant and site identifiers that you must discover first. Reading all of Workday reliably is a maintained integration, not an afternoon of scripting.
# internal, undocumented: no key, no support, 20 results per page
curl -X POST "https://{tenant}.{wd}.myworkdayjobs.com/wday/cxs/{tenant}/{site}/jobs" \
-H "Content-Type: application/json" \
-d '{"limit": 20, "offset": 0, "searchText": ""}'
The Nivult route
Reading Workday yourself buys you one source and a maintenance burden. The Nivult index already reads Workday next to 77+ other career systems, every day, in one schema: seniority, workplace, language, skills and a salary signal added by our own measured models. A posting is marked closed only when it leaves the employer's page, never because it grew old.
Free sample export on the actor page · no credit card required
Live right now
Counted on active postings in our index, 11 Oct 2026. Company names come from our employer spine, with the board slug as fallback.
| # | Company | Active postings |
|---|---|---|
| 1 | Cvshealth | 29,623 |
| 2 | Accenture | 25,300 |
| 3 | trinityhealth | 6,561 |
| 4 | Advocate Health | 5,328 |
| 5 | globalhr | 5,095 |
| 6 | Hitachi Energy | 4,256 |
| 7 | citi | 3,576 |
| 8 | babilou | 3,523 |
| 9 | Fresenius Medical Care | 3,217 |
| 10 | Micron | 3,153 |
| 11 | Airbus | 3,069 |
| 12 | thermofisher | 3,020 |
| 13 | petco | 3,010 |
| 14 | pacs | 2,941 |
| 15 | Johnson Controls (Ireland) | 2,735 |
Real rows, real links
The most recent live Workday postings in the index. Links go to the employer's own page, where the posting either still stands or shows its closure.
The shape of the feed
The first posting above, serialized with the field names of the daily export. Fields we could not measure on this row are simply absent: a declared salary appears as salary_observed_*, and when the employer declares nothing the modelled salary_estimate_* fields take its place in the full export.
{
"title": "RN - Registered Nurse - Emergency - 11am - 11:30pm",
"company": "trinityhealth",
"ats": "workday",
"country": "US",
"city": "Dublin",
"posted_at": "2026-10-11",
"url": "https://trinityhealth.wd1.myworkdayjobs.com/jobs/job/Dublin-Ohio/RN---Registered-Nurse---Emergency---11am---11-30pm_00691913"
}
Before you ask
No. Workday does not publish a public job board API: postings live behind JavaScript portals or internal endpoints that are neither documented nor supported. Reading them reliably at scale is a maintained integration, which is the part we already run daily.
As of the last refresh (11 Oct 2026), our index holds 450,321 active Workday postings across 2,189 companies. A posting counts as active only while it appears on the employer's own board; when it leaves the source we mark it closed, we never let it age out silently.
Through the Nivult index: Workday postings arrive already unified with 77+ other ATS sources in one schema, enriched with seniority, workplace, language, skills and a salary signal. Start with the free sample on the Apify actor linked above, or book a call for the full daily export.
Because there is no public API and no registry of tenants. Every Workday site has its own host and internal identifiers, the listing endpoint is undocumented and paginated at 20 results, and the payload format changes between tenants. The endpoint works, and we read it daily, but nobody at Workday will help you when it changes.
Yes: the Workday Jobs Dataset on Apify reads every Workday career site in our index, daily. Link in the Nivult route section above.
Numbers on this page are measured from our own index of employer career systems, refreshed daily. The «last refresh» date is the timestamp of the last real data change, not the page build time. How we collect data · All ATS sources