Workday: How to use the Proxy API for Accounting SOAP requests

Edited

1. Overview

The Apideck Proxy API lets you execute direct requests against the Workday SOAP API. This guide covers Accounting operations using the Resource_Management, Revenue_Management, and Financial_Management services.

If you have multiple Workday connections configured (e.g. HRIS and Accounting), you must include the x-apideck-unified-api header so Apideck knows which connection to use.


2. Example request

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-unified-api: accounting' \
  --header 'x-apideck-downstream-url: https://{WSDL}/ccx/service/{tenant}/Financial_Management/v44.2' \
  --header 'Content-Type: application/soap+xml' \
  --header 'Accept: application/soap+xml' \
  --data '{SOAP_BODY}'

Downstream URL format:

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 changes depending on which Accounting operations you need (see section 4)

  • The version (e.g. v44.2) depends on your Workday tenant configuration


3. Example SOAP body

Keep the placeholders such as {username}, {password}, and {tenant_id} in curly braces - Apideck handles these 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_Cost_Centers_Request></wd:Get_Cost_Centers_Request>
  </soapenv:Body>
</soapenv:Envelope>

4. Common Accounting operations

Update the operation in the SOAP body and adjust the downstream URL service accordingly.

Resource_Management service:

  • Get_Purchase_Items

Revenue_Management service:

  • Get_Sales_Items

Financial_Management service:

  • Get_Cost_Centers

  • Get_Tax_Applicabilities

  • Get_Tax_Recoverabilities

  • Get_Payment_Terms

  • Get_Payment_Types


5. Related links

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.