Home / Workday jobs API — scraping myworkdayjobs.com past the 2,000 cap

Job boards

Workday jobs API — scraping myworkdayjobs.com past the 2,000 cap

Workday career sites have no documented public API and the UI stops at 2,000 jobs. Here is how the unofficial endpoints work, what breaks, and a hosted Actor that returns pay ranges and exact posting dates.

Workday career sites live on hostnames like {company}.myworkdayjobs.com. Unlike Greenhouse, Lever and Ashby, there is no documented public job-board API. The careers UI itself is backed by unofficial CXS endpoints, and several of them cap a single query at 2,000 jobs. A large employer can be over that cap, so a naive scrape looks "complete" when it is not.

What you can get when it works

A careful client can still read, without a login:

  • job title, locations and remote type;
  • pay ranges when the company publishes them;
  • the exact posting date;
  • the full description, if you ask for it;
  • the rest of the board past the 2,000-result window, by paging with the right cursors rather than by asking for offset 2000.

What goes wrong

Workday rate-limits datacenter IPs, including the ones shared by cloud platforms. A run that is being blocked can come back with zero jobs even when the company is hiring. An earlier version of our own Actor treated that as a successful empty result; that was wrong. A blocked site should be retried, then reported as a failed run, not as "no openings."

Residential proxies can sometimes get through when datacenter IPs cannot. They cost more, so they should be a fallback, not the default.

The Actor

Workday Jobs Feed is built for myworkdayjobs.com career sites. It pages past the 2,000 cap, keeps pay ranges and posting dates, and fails the run if every site is blocked rather than returning an empty success. $1.50 per 1,000 jobs, no start fee.

Example tasks:

For Greenhouse, Lever and Ashby, use ATS Jobs Feed instead — those platforms have official public board APIs. See the Greenhouse jobs API guide.