Workday Jobs Scraper — every role from a Workday careers site
Pricing
from $2.00 / 1,000 job results
Workday Jobs Scraper — every role from a Workday careers site
Get every open role from any Workday careers site. Reads the official public job-board API that the company's own careers page uses — no browser, no cookies, no blocking. Handles boards with thousands of roles.
Pricing
from $2.00 / 1,000 job results
Rating
0.0
(0)
Developer
Shun Furu
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Workday Jobs Scraper
Get every open role from any Workday careers site.
Paste the careers URL — https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite — and this
Actor reads the official public job-board API that the company's own careers page calls, and
returns clean, flat JSON.
No browser. No cookies. No proxies. No blocking.
Input: ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"]Output: 2,000 rows — title, location, remote flag, requisition ID, URL
Why this one
Workday runs the careers site of a large share of the world's biggest employers, and those boards are big: NVIDIA publishes about 2,000 open roles, Salesforce about 1,530, Cisco about 1,180 (measured 2026-08-22).
Most scrapers render those pages in a headless browser and parse HTML, which is slow, gets blocked, and breaks whenever the page changes. This Actor talks to the same JSON endpoint the page itself uses, so it is fast and it does not break.
Workday returns 20 roles per request. A 2,000-role board is therefore 100 requests. This Actor reads the total up front and fetches the remaining pages in parallel, which takes a full 2,000-role board from minutes down to about 16 seconds.
Input
| Field | Type | Default | What it does |
|---|---|---|---|
careerSites | array of strings | one example site | Workday careers URLs. A link to a single job works too — the site is taken from it |
keyword | string | — | Keep only roles whose title matches any of these words |
location | string | — | Keep only roles whose location contains any of these words |
remoteOnly | boolean | false | Keep only roles whose location mentions remote |
includeDescription | boolean | false | Also fetch each role's detail page — see below |
maxJobsPerSite | integer | 0 (no limit) | Cap roles per site |
maxTotalJobs | integer | 0 (no limit) | Cap the whole run — use this to cap cost |
Finding the careers URL
Open the company's job search page. If the address bar shows
something.wdn.myworkdayjobs.com/SiteName, that is the URL to paste. Some employers put a
branded domain in front of it (jobs.example.com); in that case, click through to a single job and
copy the myworkdayjobs.com URL that appears.
The Workday tenant cannot be derived from a company domain —
nvidia.comgives no hint that the board lives atnvidia.wd5.myworkdayjobs.com. That is why this Actor asks for the URL rather than pretending to guess.
About includeDescription
Workday's listing endpoint is deliberately thin. It gives the title, location, requisition ID and a
relative date (Posted Yesterday, returned as postedLabel).
Turn includeDescription on and the Actor also reads each role's detail page, which adds:
description— the full job description as plain textpublishedAt— a real ISO dateemploymentType— e.g.Full time
That is one extra request per role, so on a 2,000-role board it is much slower. Pair it with
maxJobsPerSite when you only need details for the newest roles.
Output
{"careersSite": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite","tenant": "nvidia","workdayHost": "nvidia.wd5.myworkdayjobs.com","siteName": "NVIDIAExternalCareerSite","jobId": "JR2019870","title": "Senior Systems Software Engineer, Data Center Platform Enablement","url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/...","location": "US, CA, Santa Clara","remote": null,"employmentType": "","publishedAt": null,"postedLabel": "Posted Yesterday","scrapedAt": "2026-08-22T09:48:35.371Z"}
A SUMMARY record is written to the key-value store listing every site that was read, the tenant
and site name it resolved to, and how many roles matched your filters.
Pricing
You pay for roles, not for attempts.
| Price | |
|---|---|
| Starting a run | $0.00001 (one US cent per 1,000 runs — effectively nothing) |
| Each role returned | $0.002 ($2 per 1,000 roles) |
If a URL cannot be read, no rows are produced, so there is nothing to pay for. Errors are written
to the log and to SUMMARY, never to the dataset, specifically so a failed run does not appear on
your bill.
A full 2,000-role board costs about $4. Use maxTotalJobs to cap a run.
Typical uses
- Talent intelligence — watch which teams a large employer is growing, and where.
- Job aggregators — pull a curated list of big employers on a schedule.
- Market research — measure hiring velocity across an industry over time.
- Job seekers — track a shortlist of employers and catch roles the day they open.
Notes on data and compliance
- Only the public, unauthenticated job-board endpoint is used. Nothing behind a login is touched.
- Job postings are company business information, not personal data. No candidate or employee data is collected.
- No bot protection is bypassed and no rate limits are circumvented; the Actor backs off on
429.
Limitations — stated up front
- A careers URL is required. A bare company domain is not enough, for the reason given above.
publishedAtandemploymentTypeare empty unlessincludeDescriptionis enabled — Workday does not put them in the listing.locationis free text as the employer wrote it (US, CA, Santa Clara, or2 Locationswhen a role spans several). It is not normalised.- Salary is not published in Workday's public endpoints, so it is not returned.
Other ATS platforms
If the company is not on Workday, use Company Jobs Scraper — same approach, for Greenhouse, Ashby, Lever, SmartRecruiters, Rippling and Personio, and it detects the platform from a company domain.