Workday jobs API

Where the enterprise employers are. Also the most awkward endpoint of the twelve, and the one most likely to hand you numbers that are quietly wrong.

The endpoint

POST https://{tenant}.{cluster}.myworkdayjobs.com/wday/cxs/{tenant}/{site}/jobs

No key, no login. The slug is three parts, not one — the tenant, the cluster (wd1, wd5, wd103…) and the site name, all visible in the careers URL {tenant}.{cluster}.myworkdayjobs.com/en-US/{site}.

curl -s -X POST 'https://acme.wd5.myworkdayjobs.com/wday/cxs/{tenant}/acmecareers/jobs' \
  -H 'Content-Type: application/json' \
  -d '{"appliedFacets":{},"limit":20,"offset":0,"searchText":""}'

What it returns, measured

Measured across every live Workday board in our registry — 41,683 postings from 2,658 boards, not a sample. yes means 99.5% or more; no means the field does not exist on this endpoint.

Field	Workday
Posting date	78.2%
Description	no
Pay	no
Marked remote	no

Title, company, location and an apply URL come back on every row.

What it is good at

By far the deepest boards. A single Workday tenant can carry tens of thousands of open postings — the largest board in our registry has over 93,000. If you want volume from household-name employers, it is here.

Where it falls short

The list endpoint carries no description, no pay and no department. Dates are prose — "Posted Today", "Posted 30+ Days Ago" — so only 78.2% of rows resolve to a real timestamp, and the rest are genuinely unknown rather than old.

Mistakes that cost us time

total saturates at 2000.: It is not the number of postings. The facets counts are, and they match total exactly on boards that have not saturated.
The API serves rows past the end.: Probing offsets until a page comes back empty never terminates. We recorded twelve boards at a 60,000 probe ceiling once and would have advertised 720,000 postings that did not exist.
Site names are case-insensitive.: The same board arrives twice under different casing unless you lowercase the key.
Twenty rows per request.: A fifth of what the other platforms return, so a deep board is a lot of round trips.

So should you use it

Yes, for volume and large-employer coverage.

No, for anything needing description, pay, department, or a dependable date.

How Workday compares with the other eleven on the same four fields is on the comparison page. If you would rather not write and maintain a client, this Actor reads Workday and emits the same row shape as the other eleven, and ATS Database is a free lookup for finding which platform a given company is on.

Finding the boards

Workday keys are compound — cluster, tenant and site — so a board is not identified by one string, and the same board arrives twice from archive URLs unless the site name is lowercased. Our first pass also probed offsets until a page came back empty, which never terminates on this API; twelve boards hit a 60,000 probe ceiling and would have advertised 720,000 postings that do not exist. The registry holds 2,658 Workday boards.