Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    English (US)
    MX Spanish (Mexico)
    CA French (Canada)
    US English (US)
    • Home
    • Management Tools
    • Workday Implementation

    Workday: X509 Certificate

    Written by Lindsey Stanifer

    Updated at August 31st, 2026

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Getting Started
      Setting up your calendar Managing your alerts Additional Settings
    • Daily Processes
      Candidate Inbox Candidate Profile My Calendar/Calendars Browser Extension My Jobs Approvals Engine Manual and Common Scheduling Practices Form I-9 processes Troubleshooting Forms & Offers
    • Candidate and User Engagement
      Campaigns Conversation Builder Surveys Channels Talent Community Voice Web Management Analytics & Reporting Data Privacy Career Sites
    • Management Tools
      Job Management Scheduling Security Journeys Content Management System (CMS) Multiple Brands Workflows Users, Roles and Permissions Data Feeds Location Management Lookup Tables Assistant Messaging Company Information Client Setup System Attributes Integration Center Workday Implementation
    • Contextual AI
      Knowledge Training Library
    • Conversational Events and Campus
      Conversational Events Campus Events
    • Employee Communications
      Communications App Employee Management
    • Release Notes
      2025 2026
    • Workday Feature Descriptions
    + More

    If a Workday client requests that an X509 certification be used for signing requests made to Workday, the following must be completed:

    1. Send the public key to the client, this can be re-used in PROD and STG.
    2. The client will then need to provide a username to be used in the payload.
    3. You will need use the following node for the signature: <ds:Signature Id="placeholder"></ds:Signature>

    Sample Payload

    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
        <env:Header>
            <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                <wsse:UsernameToken>
                    <wsse:Username>{USERNAME GOES HERE}</wsse:Username>
                </wsse:UsernameToken>
                <ds:Signature Id="placeholder"></ds:Signature>
            </wsse:Security>
        </env:Header>
        <env:Body>
            <wd:Move_Candidate_Request xmlns:wd="urn:com.workday/bsvc" wd:version="v41.0">
                <wd:Dynamic_Business_Process_Parameters>
                    <wd:Next_Step_Reference>
                        <wd:ID wd:type="Workflow_Step_ID">{{__journey_candidate_status|mapvalue('statusUpdate')}}</wd:ID>
                    </wd:Next_Step_Reference>
                </wd:Dynamic_Business_Process_Parameters>
                <wd:Move_Candidate_Data>
                    <wd:Job_Application_Reference>
                        <wd:ID wd:type="WID">{{__ex_id_1}}</wd:ID>
                    </wd:Job_Application_Reference>
                </wd:Move_Candidate_Data>
            </wd:Move_Candidate_Request>
        </env:Body>
    </env:Envelope>
     
     

    The <ds:Signature Id="placeholder"></ds:Signature> will be translated after the payload is sent, so you won’t be able to see it in the Integration Center's preview.

    You can run a test by sending to a test endpoint here.  

     





     

    credential

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • Workday: Status movements integration
    • Workday: Conversational Apply (Chat to Apply) integration
    • Workday: Common integration IDs for PUT candidate
    • Workday: API Access for browser extension

    Copyright 2026 – Paradox.

    Knowledge Base Software powered by Helpjuice

    Expand