Workday Jobs Api
Pricing
Pay per event
Workday Jobs Api
Pricing
Pay per event
Rating
0.0
(0)
Developer
Sam Towers
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Workday, SmartRecruiters & Workable Jobs
Collect normalized public job postings from Workday, SmartRecruiters, and Workable career sites in one dataset.
Input
Provide a non-empty companies array. Each entry can be a supported career URL or an object with value and optional source, tenant, and site fields.
Supported filter fields are title, location, remoteOnly, postedAfter, includeDescription, and maxResultsPerCompany (1–10,000; default 200). Company names and domains can be resolved when they identify a supported public career source; successful name/domain resolutions are cached for later runs.
Optional filters fields are title, location, remoteOnly, postedAfter (ISO 8601), includeDescription (default true), and maxResultsPerCompany (default 200, maximum 10,000).
Output and billing signals
Each dataset item is a normalized job with fields including id, source, company, title, location, remote, posted_at, url, apply_url, description, employment_type, and department. Results are deduplicated within a run, filtered before persistence, and capped separately for each company.
The run summary reports published jobs, newly resolved companies, and isolated company errors. A partial run can still publish successful companies.
Supported sources
- Workday hosted career sites on
wd1,wd3,wd5, andwd103. - SmartRecruiters public career APIs.
- Workable public career APIs.
The Actor uses public HTTP endpoints and does not require browser automation or private credentials for these sources.
The implementation emits internal billing signals only after the corresponding action succeeds:
job-scrapedis emitted only after one filtered, deduplicated normalized record is successfully persisted.tenant-resolvedis emitted only for a successful uncached name/domain resolution; explicit URLs, tenants, cached mappings, and failed resolutions do not emit it.
Provider or persistence failures are isolated per company and returned in the summary, preserving successful partial-run output and billing semantics.
