Workday Jobs API & Scraper
The Workday Jobs API returns the job postings of any company's public Workday career site (<company>.wdN.myworkdayjobs.com) as JSON: search with the site's own filters and counts, full postings with requisition id, exact posting date, locations and pay ranges, and a company-name lookup.
🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.
Workday itself offers no public API for reading the postings its customers publish; this API reads the career sites logged out. `resolve` turns a company name, domain, Workday link or the company's own careers page into its Workday tenant and career sites. `search` takes keywords and every filter the site itself shows (country, city, state, job category, job type, full or part time, remote or on-site, posting age, hiring company), returns 1 to 20 postings per page and the site's own count for every filter value. `job` returns the whole posting: title, requisition id, link and apply link, the full description, every location, the country with its ISO code, the exact posting date, the closing date where the employer set one, the hiring legal entity, the pay ranges the posting prints, contact e-mails and phone numbers printed in the posting, and the similar jobs the site recommends. `all_jobs` reads a whole career site in one call, also past the point where Workday stops counting at 2,000; max_jobs sets how many postings it returns (1,000 by default, up to 5,000) and the call is billed per posting returned. `latest_jobs` lists the links of a site's newest postings (up to 100, newest first) to open with `job`, and `companies` is a directory of the 205 employers whose Workday career sites were verified live.
What a Workday field actually contains
Fields that read differently from how they look. Every row was measured on live Workday career sites on 2026-11-15.
| Field | What it holds |
|---|---|
| total, total_capped, total_estimate | total is Workday's own count. On some career sites it stops at 2,000: NVIDIA reported 2,000 while its own full-time/part-time filter counted 2,692 postings. total_capped is then true and total_estimate gives the filter's sum (2,692). Capital One reported 2,061 and its page 104 returned the 2,061st posting. |
| page, page_size | 1 to 20 postings per page; Workday refuses more than 20. Three pages of 20 and six pages of 10 returned the same 60 postings in the same order on 3 of 3 career sites, with no repeats. |
| posted_on, posted_date_estimate (search) | A search row carries only the site's text, e.g. "Posted 3 Days Ago". posted_date_estimate is today minus those days; for "Posted 30+ Days Ago" it is empty. The posting itself (job) carries the exact posted_date. |
| requisition_id | The employer's requisition number (JR2027818, R00356794, 0000040240). It matched the posting page's own identifier on 14 of 14 postings and the search row on 34 of 34. |
| posting_id, path | Workday's id for the posting (title slug + requisition id) and its path on the career site. Either one, a requisition id, or the full link opens the posting in job. |
| country | The posting's country name, ISO code and Workday's country id. The same country id is used by every career site, so a country filter can be written once (countries lists 119). |
| pay_ranges, pay_text | Workday has no salary field. Many US postings print pay in the description ("$23.50 to $26.70", "184,000 USD – 299,000 USD", one range per level). pay_ranges gives min, max, currency and hour or year where the sentence says it; pay_text keeps the sentence. |
| hiring_organization.name, name_clean | The legal entity that hires, as Workday prints it with its internal code ("CN15 NVIDIA Semiconductor(Shenzh)Co Ltd"); name_clean drops the code. It matched the posting page on 13 of 14 postings; the 14th was empty on both. |
| contacts | E-mail addresses and phone numbers the posting itself prints, such as a recruiter's contact line. Returned as published. |
| all_jobs complete, stop_reason | all_jobs stops at max_jobs (1,000 by default, up to 5,000). complete says whether every posting of the site or view came back; stop_reason says why it stopped when not. |
Titles and descriptions are returned in the language the employer wrote them. The locale parameter switches the filter labels and "Posted …" texts to the site's other languages (de-DE: "Heute ausgeschrieben").
Real request and response JSON
Captured from the indexed primary action, search, on .
{
"method": "POST",
"url": "https://api.reefapi.com/workday/v1/search",
"headers": {
"x-api-key": "$REEF_KEY",
"content-type": "application/json"
},
"body": {
"site": "nvidia/NVIDIAExternalCareerSite",
"query": "engineer"
}
}{
"ok": true,
"meta": {
"api": "workday",
"endpoint": "search",
"mode": "live",
"latency_ms": 2007.3,
"record_count": 20,
"bytes": 19063,
"cache_hit": false,
"total": 2000,
"upstream_requests": 1,
"charged_credits": 2,
"version": "0.1.0",
"request_id": "d8de1f857ae04031",
"fetched_at": "2026-11-15T18:52:19.771Z"
},
"data": {
"site": {
"tenant": "nvidia",
"wd": "wd5",
"host": "nvidia.wd5.myworkdayjobs.com",
"site_id": "NVIDIAExternalCareerSite",
"url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
"locale": null
},
"query": "engineer",
"applied_filters": {},
"jobs": [
{
"posting_id": "Senior-Security-Engineer--Detection-Engineering_JR2022836",
"requisition_id": "JR2022836",
"title": "Senior Security Engineer, Detection Engineering",
"path": "US-CA-Remote/Senior-Security-Engineer--Detection-Engineering_JR2022836",
"url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Remote/Senior-Security-Engineer--Detection-Engineering_JR2022836",
"locations_text": "3 Locations",
"location_count": 3,
"time_type": null,
"remote_type": null,
"posted_on": "Posted 11 Days Ago",
"posted_days_ago": 11,
"posted_days_ago_open_ended": false,
"posted_date_estimate": "2026-11-04",
"bullet_fields": [
"JR2022836"
]
},
{
"posting_id": "Senior-System-Engineer--Solution-Engineering_JR2026094",
"requisition_id": "JR2026094",
"title": "Senior System Engineer, Solution Engineering",
"path": "Poland-Remote/Senior-System-Engineer--Solution-Engineering_JR2026094",
"url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/Poland-Remote/Senior-System-Engineer--Solution-Engineering_JR2026094",
"locations_text": "3 Locations",
"location_count": 3,
"time_type": null,
"remote_type": null,
"posted_on": "Posted 15 Days Ago",
"posted_days_ago": 15,
"posted_days_ago_open_ended": false,
"posted_date_estimate": "2026-10-31",
"bullet_fields": [
"JR2026094"
]
},
{
"posting_id": "Senior-Software-Engineer--Test-Engineering_JR2025964",
"requisition_id": "JR2025964",
"title": "Senior Software Engineer, Test Engineering",
"path": "China-Beijing/Senior-Software-Engineer--Test-Engineering_JR2025964",
"url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/China-Beijing/Senior-Software-Engineer--Test-Engineering_JR2025964",
"locations_text": "3 Locations",
"location_count": 3,
"time_type": null,
"remote_type": null,
"posted_on": "Posted 30+ Days Ago",
"posted_days_ago": 30,
"posted_days_ago_open_ended": true,
"posted_date_estimate": null,
"bullet_fields": [
"JR2025964"
]
}
],
"count": 20,
"total": 2000,
"total_capped": true,
"total_estimate": {
"count": 2555,
"from_facet": "timeType"
},
"page": 1,
"page_size": 20,
"offset": 0,
"has_more": true,
"page_beyond_last": false,
"rows_without_path": 0,
"facets": [
{
"param": "jobFamilyGroup",
"label": "Job Category",
"group": null,
"filter": "category",
"value_count": 14,
"values": [
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
},
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
},
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
}
]
},
{
"param": "workerSubType",
"label": "Job Type",
"group": null,
"filter": "job_type",
"value_count": 6,
"values": [
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
},
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
},
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
}
]
},
{
"param": "timeType",
"label": "Time Type",
"group": null,
"filter": "time_type",
"value_count": 2,
"values": [
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
},
{
"id": "[trimmed-depth]",
"label": "[trimmed-depth]",
"count": "[trimmed-depth]",
"selected": "[trimmed-depth]"
}
]
}
]
}
}What the Workday Jobs API does
| Action | Description | Concrete use case | Key params |
|---|---|---|---|
| resolve | Find a company's Workday career sites: from a company name (NVIDIA, Capital One), its domain (capitalone.com), a Workday tenant (nvidia), any myworkdayjobs.com / myworkdaysite.com link, or the company's own careers page (the Workday link on it is followed). Returns the tenant, its wd host and every career site it lists, each with its link. | Recruiting teams call resolve to find a company's Workday career sites. | company |
| search | Search one Workday career site, 1-20 postings per page, with every filter the site shows (country, location, region, category, job type, time type, remote type, posting age, hiring company, or any facet by id) and the site's own counts per filter value. Each row: title, posting id, requisition id, link, location text and count, time type / remote type where the site shows them, and how long ago it was posted. `total` is Workday's own count; some sites stop counting at 2000 (`total_capped`, with `total_estimate` from the site's own filter counts). | Labor-market analysts call search to search one Workday career site, 1-20 postings per page, with every filter the site shows (cou…. | site, query, page, page_size, locale, ... |
| filters | Every filter one Workday career site shows, with each value's id, label and job count, for the whole site or for a query / filtered view (counts follow the filters applied). Tells which named filter (country, category, …) each facet answers to on this site. | Job boards call filters to get every filter one Workday career site shows, with each value's id, label and job count, for th…. | site, query, locale, country, location, ... |
| job | One Workday posting in full: title, requisition id, posting id, link and apply link, the whole description (text and HTML), primary and additional locations, the requisition's location, country with ISO code, remote type, time type, exact posting date, closing date and time left where the employer set one, apply flags, the hiring legal entity, every pay range the posting prints (min, max, currency, period, level) with its sentence, the e-mail addresses and phone numbers the posting prints (recruiter / HR contact lines), and the similar jobs the site recommends. | Sales intelligence teams call job to get one Workday posting in full. | job, site, locale |
| similar_jobs | The jobs a Workday career site recommends next to one posting (0-5 on the sites measured), each with its exact posting date. | Recruiting teams call similar_jobs to get the jobs a Workday career site recommends next to one posting (0-5 on the sites measured), ea…. | job, site, locale |
| latest_jobs | The newest postings of one Workday career site from its own site map (the 100 most recent, newest first): each posting's link, path, posting id and its language versions. Open any of them with `job` for the full posting. | Labor-market analysts call latest_jobs to get the newest postings of one Workday career site from its own site map (the 100 most recent, ne…. | site, limit, locale |
| all_jobs | Every posting on one Workday career site (or of one query / filtered view) in one call, as search rows. A site whose count stops at Workday's 2000 ceiling is read slice by slice over its own filter values and de-duplicated, so sites with more than 2000 openings come back whole. | Job boards call all_jobs to get every posting on one Workday career site (or of one query / filtered view) in one call, as se…. | site, query, max_jobs, locale, country, ... |
| company | A company's Workday presence: every career site of its tenant with its job count, the site's top categories / countries / locations / job types with counts, the main site's title, about text, languages, default country, home page, privacy policy and social links, and the legal entities hiring through it. | Sales intelligence teams call company to get a company's Workday presence. | company, locale |
| companies | Our directory of employers whose Workday career sites we verified live: tenant, name, wd host, career sites and their job counts at measurement time. No upstream request. | Recruiting teams call companies to get our directory of employers whose Workday career sites we verified live. | query, page, page_size |
| countries | The countries Workday career sites filter on, with ISO code and Workday's country id (the same id on every tenant). No upstream request. | Labor-market analysts call countries to get the countries Workday career sites filter on, with ISO code and Workday's country id (the sam…. | query |
Call search from your stack
curl -X POST https://api.reefapi.com/workday/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"site":"nvidia/NVIDIAExternalCareerSite","query":"engineer"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/workday/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"site": "nvidia/NVIDIAExternalCareerSite",
"query": "engineer"
},
timeout=90,
)
print(r.json()["data"])const res = await fetch("https://api.reefapi.com/workday/v1/search", {
method: "POST",
headers: {
"x-api-key": process.env.REEF_KEY,
"content-type": "application/json",
},
body: JSON.stringify({
"site": "nvidia/NVIDIAExternalCareerSite",
"query": "engineer"
}),
});
const { ok, data, meta, error } = await res.json();Ask your MCP-connected assistant: call reefapi.workday.search with {"site":"nvidia/NVIDIAExternalCareerSite","query":"engineer"}.Who uses this API and why
- Track every new opening at a list of target companies, with the exact posting date.
- Build a job board or alert from company career sites, filtered by country, category and remote type.
- Collect pay ranges from US postings for compensation benchmarks.
- Measure a company's hiring by country, job family and job type from the site's own counts.
- Turn a list of company names into their Workday career sites and full job lists.
Questions developers ask before integrating
Is there a Workday API for job postings?
Yes. The workday API on ReefAPI reads any company's public Workday career site (<company>.wdN.myworkdayjobs.com) and returns its postings as JSON, no Workday account needed. Workday's own APIs are for its customers' HR systems and need their login.
Which companies can I read?
Any employer with a public Workday career site. On 2026-11-15 we verified 205 employers live on 11 Workday hosts; companies is that directory, with their career sites and job counts. resolve finds any other employer from its name, domain, Workday link or careers page.
How do I find a company's Workday site?
Call resolve with the company name ("Capital One"), its domain (capitalone.com), a myworkdayjobs.com link or its own careers page. It returns the tenant and every career site the company lists, e.g. 9 for Salesforce (Salesforce, MuleSoft, Tableau, Slack, Heroku and others).
Which filters does search support?
Every filter the career site shows, measured against the unfiltered count: NVIDIA 2,000+ postings → category Sales 316, country DE 29, remote 567, intern 224; Salesforce 1,608 → Ireland 147; 3M 786 → posted within 1 week 124, hybrid 5; CommBank 216 → India + Engineering 82. Which filters exist differs per company; filters lists them with counts.
Can I get more than 2,000 postings?
Yes, with all_jobs. Where Workday stops counting at 2,000, all_jobs reads the site one filter value at a time and removes duplicates: NVIDIA returned 2,692 postings, the number its own filter counts add up to. Set max_jobs to how many postings you want (1,000 by default, up to 5,000); the call is billed per posting returned.
Does it return salaries?
When the posting prints them. Workday has no salary field; US postings often state a range in the text, which pay_ranges returns as numbers with currency and period (Nordstrom "$25.45 - $26.45 Hourly", NVIDIA one range per level).
How fresh is the data?
Every call reads the career site live. latest_jobs returns the links of the site's newest postings (up to 100, newest first) from the site's own site map; open each with job for the full posting.
Can I search in another language?
Search words go to the site's own search box as typed ("Kundenberater" on Deutsche Bank matched 115 postings). locale switches filter labels to the site's other languages; titles stay as the employer wrote them.
What is the Workday Jobs API?
Workday Jobs API is a ReefAPI endpoint group for job postings from any company's workday career site: search with the site's own filters, full postings with pay ranges, and a company-name lookup. It returns live JSON through POST requests under /workday/v1.
Is the Workday Jobs API free to try?
Yes. ReefAPI starts with 1,000 free credits, no card required. Workday Jobs calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Workday Jobs login or account?
No login to Workday Jobs is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Workday Jobs data?
The page example is captured from a live resolve call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Workday Jobs API use?
Workday Jobs actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Workday Jobs from an AI assistant or MCP client?
Yes. Connect ReefAPI once through MCP and your assistant can call workday actions with the same key, credit pool and JSON envelope used by normal REST requests.