John Cole

Sep 06, 2026 • 5 min read

Workday API: Pull Every Job From Any Workday Careers Site as JSON

A public Workday API that turns any myworkdayjobs.com careers site into structured JSON: titles, locations, salaries, and apply links, priced per job.

Workday API: Pull Every Job From Any Workday Careers Site as JSON

I kept hitting the same wall on hiring research: a company posts every open role on its Workday careers site, but there is no clean way to read those jobs programmatically. The pages load over JavaScript, the public HR APIs Workday documents are for enterprise systems behind a login, and copy-paste does not scale past one company. So I built a public Workday API for the part anyone can see: the careers site itself.

The Workday Careers API takes any Workday careers URL and returns every open job on that site as structured JSON, one row per posting, with no tenant, recruiting license, or account required.

What the Workday API returns

Give it a myworkdayjobs.com or myworkdaysite.com URL in any locale form. For each job you get:

  • Title, company, tenant, and siteId

  • Job URL and direct apply URL

  • All locations for the posting, not just the first

  • ISO posted date and end date

  • Time type and remote type

  • Full description as HTML and plain text

  • Extracted salary min, max, and currency where the posting lists them

  • Total jobs on the site, plus site facets in a separate summary record

Run it in three steps

Paste a careers URL, run, and read the dataset. There is nothing to configure and no proxy to set up. Pricing is per job result plus a small run fee, so a 200-job site costs cents and you only pay for rows you

actually get back.

Use it as a REST API

Every run is a normal REST call. Start the Actor with a careers URL, poll the run, then pull the dataset as JSON, CSV, or Excel. That makes it easy to drop Workday job data into a spreadsheet, a database, or a nightly job that watches a set of employers. The output shape stays the same across companies, so one parser handles every Workday tenant.

Wire it into Claude with MCP

The Actor also runs as a Workday MCP server, so an AI agent can call it as a tool with no scraping code. Point an MCP client at the Apify MCP server and ask something like "list every remote engineering job on Nvidia's Workday site with salary ranges." The agent runs it and gets back structured rows it can filter and summarize.

What people build with it

The common thread is hiring signal: which companies are growing, in which locations, at what pay. A few runnable examples on the project page:

You can see the full set on the examples page or the Peerlist project. For a longer walkthrough with sample output, I wrote up how to scrape any Workday careers site as JSON.

FAQ About Scraping Workday Careers Sites

Where does the Workday scraper get its data?

It reads the public careers site you point it at, the same pages a job seeker sees, and returns them as clean JSON. Jobs come back fresh at run time, so a scheduled run reflects what is live that day. It does not touch any internal HR system or logged-in data.

Is Workday an ATS, and can this API read any Workday tenant?

Yes, Workday is an applicant tracking system, and thousands of employers run their careers sites on it. The API works on any public Workday careers URL regardless of company, because the output fields are the same across tenants. If a site is public, you can read it.

How do I call the Workday API, and what does it cost?

Call it over REST: start a run with a careers URL and pull the dataset in JSON, CSV, or Excel. Billing is per job result plus a small run fee, so a 200-job site is a few cents and you never pay for an empty result.

Can I use the Workday API from Claude or another AI agent through MCP?

Yes. The Actor is exposed as an MCP tool, so Claude or any MCP client can run it directly and get structured job rows back without writing any code. It is a good fit for headcount tracking and hiring-signal agents.

Can an AI agent pay for this scraper in USDC with x402?

Yes. The Workday Careers API supports agentic payments via the x402 protocol, so AI agents and MCP clients can pay for runs in USDC on Base with no Apify account or API token. Point your agent at the Apify MCP server and it can discover, pay for, and run the scraper autonomously; the Apify x402 announcement has the details.

If something looks off with a specific careers site, open an issue on the Actor and I usually reply within a day.

Join John on Peerlist!

Join amazing folks like John and thousands of other builders on Peerlist.

peerlist.io/

It’s available... this username is available! 😃

Claim your username before it's too late!

This username is already taken, you’re a little late.😐

0

0

0