Import a candidate into Workday Recruiting via the Staffing web services SOAP API
domain: workday.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain your Workday tenant name, hostname, and an Integration System User (ISU) account with the Staffing functional area security policy permissions needed for candidate import.
The Workday Staffing WSDL is available at https://<hostname>/ccx/service/<tenant>/Staffing; download and generate client stubs or use a SOAP library.
Authenticate using WS-Security UsernameToken in the SOAP header, including the ISU username in the format ISU_name@tenant and the ISU password.
Use the Import_Candidate operation (or its equivalent in your Workday version) to submit candidate data including name, contact information, and source; map your fields to the Candidate_Data complex type.
Handle the response: on success, Workday returns a Candidate_Reference containing a WID (Workday ID); store this for subsequent operations like attaching the candidate to a job requisition.
For job application linking, use the Staffing web service operation to create a Candidate_Application referencing the WID and the Job_Requisition_Reference.
Known gotchas
Workday SOAP APIs use version-specific namespaces (e.g., wd:v40.0); mismatching the namespace version in your request against the WSDL version causes all requests to fail.
WS-Security UsernameToken credentials must use the format username@tenant — omitting the @tenant suffix results in authentication failures.
Workday rate-limits integration calls; batch candidate imports should be implemented as sequential requests with backoff rather than parallel bursts.
Give your agent this knowledge — and 6,400+ more routes
One MCP install gives any agent live access to the full route map across 2,100+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp