Source · Workday

Workday Jobs API.

Every public posting from every public Workday tenant - one normalized endpoint, no per-tenant OAuth.

10,000+ public tenants
24h refresh
12 months retention

Why people are confused about the Workday API

Workday does not offer a public job-postings API. The Workday Staffing REST API requires OAuth credentials granted by each tenant. That works if you are the company; it does not work if you want to consume jobs from many companies.

Every Workday customer hosts their careers site at a subdomain of myworkdayjobs.com (or wd1.myworkdayjobs.com, wd3, wd5, etc.). The page is rendered through Workday's UI, but the underlying job data is fetched from an internal JSON endpoint that varies in shape across tenant versions. JobsPipe normalizes that data across every public tenant so you don't have to.

Option 1
Scrape each tenant directly

Possible, but you need per-tenant configuration, the underlying JSON shape varies between Workday versions, and Workday's bot detection blocks naïve scrapers.

Option 2
Use one company's Staffing REST API

Works for that one company only - and only after they grant you OAuth credentials. Not a path to multi-tenant coverage.

Option 3
Use JobsPipe

Every public tenant, one call. Normalized JSON schema. Free tier covers 5,000 requests/month, no credit card.

Workday API documentation

Workday's official API documentation lives at community.workday.com/api and is gated behind a Workday Community login. The two REST surfaces a developer can read about are the Workday Staffing REST API (employees, workers, time-off) and the Public Web Services SOAP API (50+ services across HCM, finance, and recruiting). Neither documents a public job-postings endpoint, because there isn't one - Workday's job-board functionality lives in the tenant career site, not in any public API. JobsPipe's docs at /docs cover the normalized JSON schema we return for every tenant's public postings, so you only have to learn one shape regardless of which Workday version a tenant is running.

Workday REST API

The Workday REST API is the modern OAuth-based interface Workday added in v32+. It covers Staffing (workers, organizations, supervisory hierarchy), Time and Absence, Compensation, and a handful of recruiting endpoints - but only for the authenticated tenant. There is no equivalent of a Greenhouse Job Board API where any developer can hit a public endpoint and get a tenant's jobs without OAuth. If you need that pattern across the Workday universe, your options are either per-tenant OAuth onboarding or a JobsPipe-style aggregator that consumes the public career sites.

Workday API integration

For a single Workday tenant integration - payroll sync, employee provisioning, custom report extraction - you'll go through OAuth onboarding with that tenant's admin: register an integration system, scope API client credentials, and call the Staffing or HCM endpoints. For cross-tenant job-postings integration - what most teams arriving at this page actually want - JobsPipe is the integration. One API key, every public Workday tenant, normalized into the same JSON schema as 30+ other ATSs. Sample request and response are below.

Sample request

curl "https://api.jobspipe.dev/v1/jobs?source=workday" \
     -H "Authorization: Bearer $JOBSPIPE_KEY" \
     -H "Accept: application/json"

Sample response

{
  "id": "wd_eyJrIjoiZGZmYjI1OWYtOWE",
  "source": "workday",
  "tenant": "salesforce",
  "title": "Senior Software Engineer, Distributed Systems",
  "company": "Salesforce",
  "location": {
    "city": "San Francisco",
    "region": "CA",
    "country": "US",
    "remote": false
  },
  "salary": {
    "min": 165000,
    "max": 220000,
    "currency": "USD",
    "period": "year",
    "source": "explicit"
  },
  "employment_type": "full_time",
  "posted_at": "2026-05-14T09:23:00Z",
  "expires_at": null,
  "apply_url": "https://salesforce.wd1.myworkdayjobs.com/External_Career_Site/job/...",
  "description": "We are looking for a Senior Software Engineer to design and operate the distributed coordination layer underneath ..."
}

Every Workday job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.

Fields in every Workday job record

idsourcetenanttitlecompanylocationsalaryemployment_typeremoteposted_atexpires_atapply_urldescription

FAQ

Does JobsPipe need OAuth credentials from each Workday tenant?+

No. JobsPipe reads only public job postings from public tenant career sites. We never have access to applicant data, candidate PII, or any non-public Workday object.

How fresh is Workday data on JobsPipe?+

Every public tenant is re-crawled at least every 24 hours. High-volume tenants (over ~500 active postings) are refreshed every 6 hours.

Can I filter to one specific Workday tenant?+

Yes. Add ?tenant=salesforce (or any other tenant slug) to narrow results to one company's postings.

What about Workday tenants that block scrapers?+

JobsPipe respects robots.txt and rate-limits per tenant. If a tenant explicitly disallows indexing, those jobs are not on JobsPipe.

Try Workday data free - 5,000 requests/month, no credit card.

Get a free API key