Workday Jobs API

What does Workday Jobs API do?

Collect live Workday job listings and full descriptions directly from public employer career-board APIs. Supply Workday career URLs, search by keyword, and filter by location. Direct mode needs no third-party API key. The default input uses Adobe's public career board.

The existing Fantastic.jobs integration remains available by selecting that data source and supplying your own key. Both modes fetch live API responses. Sample mode is rejected; failed requests never produce fabricated jobs.

Why use Workday Jobs API?

• Retrieve job IDs, titles, employers, locations, dates, employment types, original links, and descriptions.
• Search employer boards using the same public CXS endpoints as their career sites.
• Continue pagination after location filtering to reach later matches.
• Schedule runs, use the Apify API, connect integrations, and export datasets.
• Inspect source endpoints, request counts, and detail failures in SOURCE_METADATA.

What data can it extract?

Field	Description
recordId, jobId	Board-qualified unique record ID and source requisition ID
jobTitle, companyName	Published title and employer name, or board tenant when no employer name is supplied
location, locations, country	Primary/additional locations and published country
description, descriptionHtml	Plain text and original HTML description
jobType, postedDate	Published employment type and source posting date
jobUrl, applyUrl, sourceUrl	Public job/application page and API endpoint
extractionStatus, dataMode	full or listing_only; live API provenance
rawData	Source fields after recursive removal of null values

Optional fields such as salary stay empty when the source does not publish them. They are not inferred.

How to scrape Workday jobs

1. Open Input and keep Public Workday API (no key) selected.
2. Enter the complete employer career-board URL, including its site path.
3. Optionally add a keyword and location. Leave them empty for a broad search.
4. Set maxItems and start the Actor. Download the dataset as JSON, HTML, CSV, or Excel.

Supported formats include https://tenant.wd5.myworkdayjobs.com/en-US/site and https://wd5.myworkdaysite.com/recruiting/tenant/site. A Workday CXS jobs endpoint is also accepted. Other sites and authenticated application portals are not supported.

Input

{
  "dataSource": "workday",
  "startUrls": [{"url": "https://adobe.wd5.myworkdayjobs.com/external_experienced"}],
  "keyword": "Engineer",
  "location": "",
  "maxItems": 10,
  "maxPages": 50,
  "maxConcurrency": 3,
  "requestTimeoutSecs": 45
}

maxItems limits matching jobs across boards. maxPages limits pages per board; each requests up to 20 listings. location searches primary/additional locations and country, case-insensitively. appliedFacets accepts the selected board's own facet IDs. The runtime accepts searchQuery or query as aliases for keyword.

For Fantastic.jobs, select dataSource: "fantastic" and supply fantasticJobsApiKey through the secret input field or FANTASTIC_JOBS_API_KEY. Existing time-window, description-format, organization, enrichment, and advanced-filter options apply to that provider. They do not alter direct Workday searches. Selecting Fantastic.jobs without credentials fails explicitly.

Output and diagnostics

Every record identifies its source. RUN_SUMMARY reports the live data mode and output count. SOURCE_METADATA reports per-board pages, listed jobs, matches, errors, and detail failures. If a detail request fails, its real listing can be retained with extractionStatus: "listing_only" and an empty description. If every board request fails, the run fails and stores ERROR_DIAGNOSTIC. A successful search with no matches reports no_results.

Pricing

Result events cost $1.99 per 1,000 output items, plus Apify platform usage. Any Actor Start event is listed on the Pricing tab. Fantastic.jobs usage, when selected, depends on your own provider subscription.

Local development

Install locked dependencies with npm ci. Run apify run --input-file test/live-default.json for a live default-input test or apify run --input-file test/live-filtered.json for another employer and keyword/location test. Inspect the local dataset and run node dataset-validator.js. Unit tests run with node --test test/workday.test.js.

Local storage is separate from Apify cloud storage. Deploy and run on Apify to verify production behavior.

Tips and support

Restrictive filters can legitimately return zero jobs. If a board moves, update its start URL. A page-limit warning in source metadata means more matches may exist beyond the limit. Keep detail concurrency modest and respect employer rate limits and terms. Public listings can change or disappear during a run. Use the Issues tab for support and the API tab for programmatic access.