Workday Jobs API: point it at any careers site and get rows back
Thousands of employers publish vacancies through Workday. This reads any one of them from its URL alone.
Unofficial. Not affiliated with, endorsed by, or sponsored by Workday, Inc. Structured facts only by default; no personal data is collected.
In plain language.
Workday hosts the careers site for an enormous number of large employers, and every one of those sites is built the same way underneath. That shared structure is what makes a single tool able to read all of them.
You supply a careers URL and nothing else. The tenant and site are resolved from the address itself, which is why this works on employers nobody has configured in advance — including one you discovered five minutes ago.
The verification run on 1 August 2026 pointed at Red Hat’s board and returned twenty-five roles spread across ten countries: eight in the United States, four each in Singapore and India, two apiece in the Netherlands and Japan, and single postings in France, Switzerland, Brazil, the United Kingdom and Czechia.
That international spread is the argument for reading a Workday site properly rather than scraping its first page. Raleigh led on volume, but Singapore, Tokyo, Pune, Amsterdam and Zurich all appeared, and two rows were published as Remote Netherlands and Remote France.
Roles in that run were senior engineering: a Senior Software Engineer, a Principal Forward Deployed Engineer working on AI platform and Kubernetes, a Senior Principal Chief Architect. Twenty-three of the twenty-five were full-time, and the rest left the field unstated.
Pagination on these sites is genuinely awkward. Later pages can report a total of zero even while returning results, which is exactly the kind of quirk that makes a naive scraper silently truncate. The first non-zero total is what is trusted here, so the walk does not stop early.
Every row keeps the identifier Workday assigned the requisition, along with the tenant and site it came from. Feed those identifiers back on a later run and you get a straight answer about what opened and what closed.
Because the same schema comes back regardless of which employer you pointed it at, two different boards can be compared directly. That is the difference between a scraper and a feed.
Apply links resolve to the employer’s own Workday posting, so candidates and downstream systems always reach the authoritative page rather than a copy.
Results are JSON or CSV, and a white-label HTML hiring report can be produced from the same run when the output is for a person to read.
Who it's for
- For agencies covering many employers. One tool, any Workday client. A new account can be onboarded by pasting its careers URL, with no code change and nothing to configure first.
- For developers building on hiring data. A consistent schema across every tenant means the awkward part — tenant resolution, pagination, unreliable totals — is already handled and does not need reimplementing per employer.
- For AI agents. Callable over MCP with a URL as the only argument. An agent handed a company’s careers link can return its open roles without any employer-specific integration existing beforehand.
- For market and competitive researchers. Comparable output across boards makes cross-employer comparison meaningful, rather than an exercise in reconciling five differently shaped scrapes.
Pricing
$1.50 per 1,000 jobs returned.
A single charge against the final result set, whichever employer you pointed it at. An empty run costs only the start event.
What it does not do.
Workday-hosted sites only. Employers on Greenhouse, Lever, Ashby, SmartRecruiters or Recruitee need the tool built for that platform. A URL from one of those will not resolve here.
Public postings only. Internal-only requisitions and roles behind a login are not part of a public careers site and are not reachable.
Descriptions are not returned by default. Advert bodies are the employer’s copyrighted text. The structured fields are returned as standard and the prose is an explicit choice.
No personal data. No recruiters, no hiring managers, no candidates. Vacancies only.
Field coverage follows the tenant. Workday lets each employer decide what to publish, so department, seniority and salary are populated on some boards and empty on others. Missing values are returned as null rather than filled in.
Unofficial. Not affiliated with, endorsed by, or sponsored by Workday, Inc. Workday is a trademark of Workday, Inc., used here only to identify the platform whose publicly published careers sites this tool reads. Employer names and trademarks belong to their respective owners, and all data comes from each employer’s own public careers site.
Fewer knobs. Better defaults.
Any tenant from a URL
Tenant and site are resolved from the careers address, so no employer needs configuring first.
Pagination handled properly
A page reporting a total of zero does not end the walk, so later results are not silently lost.
One schema across employers
Two different boards return the same shape, which makes them directly comparable.
Same tool, callable as an MCP server.
Workday Jobs API runs on Apify, which means it's exposed as a remote MCP tool with no extra setup. Point any MCP-compatible agent (Claude, Cursor, and others) at the endpoint below.
View full API reference on Apify{ "boards": ["https://redhat.wd5.myworkdayjobs.com/Jobs"] }