Workday Job Scraper — Workday Careers Site API | $3/1K
Pricing
from $3.00 / 1,000 job listings
Workday Job Scraper — Workday Careers Site API | $3/1K
Unofficial — not affiliated with Workday. Paste any myworkdayjobs.com or myworkdaysite.com URL and get every open role the site's own search will serve — title, location, posted date, apply link, job family on smaller tenants. Reads an undocumented endpoint, so it can change without notice.
Pricing
from $3.00 / 1,000 job listings
Rating
0.0
(0)
Developer
KENKO
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
10 days ago
Last modified
Categories
Share
Workday Job Scraper — Workday Careers Site API
Unofficial — not affiliated with Workday. Paste any myworkdayjobs.com or myworkdaysite.com URL and get every open role the site's own search will serve — title, location, posted date, apply link, job family on smaller tenants. Reads an undocumented endpoint, so it can change without notice.
Input
Every filter is optional; companies is the only required field. maxJobsTotal
is what caps spend — you are billed per row delivered.
Output
One row per open role, the same schema for every company:
| field | notes |
|---|---|
title, department, team | title as the board publishes it. Workday publishes no category and no team on a posting, so team is always null and department is not read from the posting — it is filled by replaying the search once per jobFamilyGroup facet, which is extra requests to the same host. On a board that is large relative to the rows you asked for that pass is skipped, the run log says so, and department stays null |
location, locations, country | locations is every place the role is open; location is the first of them and country its ISO-2 code, resolved from the feed where the feed has one and otherwise computed from the location text |
workplaceType, isRemote | the board's own field where it publishes one, otherwise inferred from the location text — remote if any published location reads remote; null when neither says, and isRemote follows workplaceType. It is a heuristic over free text and it is sometimes wrong: "Remote, OR" reads as remote work, not Oregon |
salaryMin, salaryMax, salaryCurrency, salaryPeriod | the Workday feed this reads carries no pay field, so these and salaryText are always null. They are in the schema because the multi-ATS build fills them from boards that do publish pay |
postedAt | ISO 8601, only where the board publishes a date. An open-ended age ("30+ days ago") is null, not a guess |
url, jobId, company, companySlug, provider |
Workday's board carries no job body, so description and descriptionHtml are always null and the description options are not offered.
Fields the board does not publish are null rather than guessed — except the ones
the table above marks as computed or inferred, which are derived from another field
on the same row and ship beside the field they came from.
Pricing
$3 per 1,000 rows. You are charged for rows delivered — filters are applied before anything is pushed, so a run that matches nothing costs nothing beyond the platform's start event.
Scope
Reads Workday's public job feed only, and only where the host's own robots.txt permits it. No logins, no candidate data, no applications, no personal data of any kind — job postings are the only thing it touches.
The endpoint this reads is undocumented, so it can change without notice. A career site also caps its own search: large tenants serve roughly the first 2,000 roles however many they list, so treat a run as "what the site will show", not "every requisition in the system".
Need more than one ATS? The multi-ATS build detects Greenhouse, Lever, Ashby, Rippling, Workable and Personio from a bare company name, and reads Workday from a career-site URL.
Unofficial. Not affiliated with, endorsed by, or sponsored by Workday.
