Workday: How to Use Apideck’s Proxy API for SOAP Requests

The Apideck Proxy API enables you to execute direct requests against the Workday SOAP API, providing a flexible and direct way to access and manipulate data according to your specific requirements.

Connect to Workday via our Proxy API

Send a POST request to: https://unify.apideck.com/proxy

Example cURL:

curl --location 'https://unify.apideck.com/proxy' \

--header 'Authorization: Bearer {YOUR_API_KEY}' \

--header 'x-apideck-consumer-id: {YOUR_CONSUMER_ID}' \

--header 'x-apideck-app-id: {YOUR_APP_ID}' \

--header 'x-apideck-service-id: workday' \

--header 'x-apideck-downstream-url: https://{WSDL}/ccx/service/{tenant}/Resource_Management/v44.2' \

--header 'Content-Type: application/soap+xml' \

--header 'Accept: application/soap+xml'

Example Downstream URL:

https://impl-services1.wd105.myworkday.com/ccx/service/{tenant}/{service}/{version}

The *WSDL** (e.g., impl-services1.wd105.myworkday.com) depends on your Workday environment (implementation vs. production)
The *service** (e.g., Resource_Management) and the version (e.g., v44.2) change depending on which Workday service you are calling
The *operation** you call changes in the SOAP body (see below)

Example SOAP Body:

Be sure to keep the placeholders such as {username}, {password} and {tenant_id} in curly braces as-they are for Apideck to handle dynamically.

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wd="urn:com.workday/bsvc">

<soapenv:Header>

<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

<wsse:UsernameToken wsu:Id="UsernameToken-">

<wsse:Username>{username}@{tenant_id}</wsse:Username>

<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{password}</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

</soapenv:Header>

<soapenv:Body>

<wd:Get_Suppliers_Request></wd:Get_Suppliers_Request>

</soapenv:Body>

</soapenv:Envelope>

Switching Operations

You can switch operations depending on the service you need. Update the SOAP body with the correct operation, and adjust the downstream URL to the right service and version.

For accounting operations, the most common ones are:

Resource_Management, Revenue_Management and Financial_Management

Resource management:

1. Get_Purchase_Items

Revenue management:

1. Get_Sales_Items

Financial management:

1. Get_Cost_Centers

2. Get_Tax_Applicabilities

3. Get_Tax_Recoverabilities

4. Get_Payment_Terms

5. Get_Payment_Types