MyWorkdayJobs Scraper

MyWorkdayJobs Scraper extracts job listings from any Workday-hosted career site — domains such as company.wd5.myworkdayjobs.com — through the same public JSON endpoints the career site itself uses to render job search and job detail pages. It works out of the box for any employer running Workday's career-site product, including large enterprises like NVIDIA and Salesforce, so it is a good fit for recruiters, sales-intelligence teams, job boards, and researchers who need structured hiring data from one company or many.

Features

• Works against any Workday career site — just point it at the site's URL, no per-company configuration.
• Returns the full search result set plus, optionally, the full job detail page (description, salary parsing, organization data, similar jobs).
• Parses salary ranges out of free-text descriptions when the employer discloses them.
• Keyword filtering at the source (Workday's own search API), so you only pay for jobs you actually want.
• Built-in retry-safe pay-per-result billing — a failed retry never double-charges.
• Runs on Apify's RESIDENTIAL proxy by default for reliable access; no extra keys or accounts required.

How to use

1. Find the Workday career site URL for the company you want (format: https://<company>.<datacenter>.myworkdayjobs.com/<lang>/<SiteName>, e.g. https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite).
2. Paste one or more of these URLs into Company career site URLs.
3. Optionally set a Search keyword to filter to specific roles (leave blank for all open jobs).
4. Leave Fetch full job details on to get the complete description, salary, and organization fields; turn it off for a faster, cheaper listing-only pass.
5. Set Max items to cap how many job records are returned, then run the Actor.

Input

• companyUrls — Required list of Workday career site URLs to scrape.
• keyword — Search filter; leave empty to retrieve all jobs.
• fetchDetails — Fetches full job details for each listing; defaults to true.
• maxItems — Maximum number of records to return across all URLs.
• proxyConfiguration — Apify proxy settings; RESIDENTIAL is recommended.

Output

Every record contains the following fixed set of fields:

• rowType
• source
• jobReqId
• postingInternalId
• jobPostingId
• jobPostingSiteId
• questionnaireId
• title
• jobUrl
• externalPath
• postedOn
• startDate
• timeType
• posted
• canApply
• includeResumeParsing
• locationText
• country
• employerName
• description
• descriptionText
• salary
• applyUrl
• applyType
• externalUrl
• location
• employer
• hiringOrganization
• similarJobs
• scrapedAt

Salary is parsed from the description text and is null when it is not disclosed. When fetchDetails is false, detail-only fields are null.

Pricing

Billing uses a pay-per-result model: one charge of $0.0034 applies for each job listing delivered to the dataset. There is no charge for empty runs. Scraping 1,000 job listings costs approximately $3.40, plus a small one-time Actor-start fee and Apify's own platform/proxy usage (billed separately, standard Apify rates). Turning off Fetch full job details does not change the price but does make each run faster if you only need the listing summary.

FAQ / Support

Does this work for every company on Workday? Yes — any career site running on *.myworkdayjobs.com is supported; just supply that company's career-site URL.

Why is a field null? Workday does not require employers to publish every field (salary, questionnaire ID, etc.). A null means the source data itself was empty, not a parsing failure.

Found a career site that doesn't work? Open an issue on the Actor's Issues tab with the URL and we'll investigate.