Provision an Integration System User (ISU) in Workday with appropriate domain security permissions for the Human Resources worklet.
Construct a SOAP envelope targeting the Human_Resources web service, including a WS-Security UsernameToken header containing the ISU username and password.
Set the SOAPAction header and Content-Type: text/xml and POST the request to your tenant's Human Resources endpoint (e.g., https://{tenant}.workday.com/ccx/service/{tenant}/Human_Resources/{version}).
Inside the SOAP body, use the Get_Workers_Request element; add a Response_Filter child element with Page and Count to paginate results.
Iterate through pages by incrementing the Page value until the response indicates no further pages remain.
Known gotchas
Workday API versions are pinned per endpoint URL — always specify a concrete version in the URL rather than relying on a default; newer data fields may not exist in older versions.
The ISU must be added to a security group with the correct domain permissions (e.g., 'Worker Data: Personal Data') — missing permissions produce a SOAP fault, not an HTTP error code.
Get_Workers returns a subset of worker data by default; use Response_Group elements to opt in to additional data groups such as compensation, roles, or organization assignments.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp