Workday Jobs API reference
Get the jobs on any company's public Workday career site as clean JSON: titles, locations, remote flags, links and full postings, with the site's own filters and their counts. Send the career site link and a search.
The Workday Jobs API has 4 endpoints, called the same way: POST /execute with the endpoint ID as capability and its fields as input, or pin Workday Jobs in the MCP server and call each one as a tool. The data comes back as JSON in results[0].data, with what the call cost in billing.credits_charged.
The input most of them take is board_url. Prices run from 1–10 credits to 1–10 credits per call, and a failed call costs nothing.
Endpoints
Open an endpoint for its input, the fields it returns and the request in cURL, Python and Node.js.
| Endpoint | What it returns | Price |
|---|---|---|
workday.jobs.search |
Search a company's Workday career site by keyword and its own filters. | 1–10 credits |
workday.job.get |
Get one posting from its link or job ID: the full description, location and remote flag. | 1 credit |
workday.jobs.facets |
List the filters a career site offers, such as job category, location and time type, with how many jobs each one has. | 1 credit |
workday.career_sites.discover |
Check which Workday data centres serve a company's career site, to find the right link. | 1–4 credits |
What to know
- The site's own filters Filters and their IDs come from the career site itself, so they match what candidates see.
- Search, then details Search gives titles, places and links. Ask for details, or call the job endpoint, for the full posting.
- Totals with every search Each search says how many jobs matched, so you can track a company's openings over time.
- Posted as the employer posts Titles, places and descriptions are the employer's own at the time of the call.
Something missing or unclear? Ask the team that builds the Workday Jobs endpoints.