Skip to main content

​
Summary

The Workday Learning integration lets you read learning content, users, enrollments and completions from your customer’s Workday tenant, and write content, courses and completions back into it. StackOne exposes two Workday Learning connectors. They cover the same unified models but sit on different Workday APIs, and each API can do things the other can’t. Which one your customer links determines what the integration can support, so pick before onboarding rather than after.

​
Which connector should I use?

Write use cases need the SOAP connector. The REST API doesn’t expose all of the write operations required to support the full sync use case, so anything that pushes data into Workday has to go through SOAP. Read use cases are better served by the REST connector. The SOAP API has limitations when pulling large volumes of data, so read-heavy integrations against a large tenant will perform better on REST. If you need both — reading a large catalog and writing back — link both connectors for the customer and route each set of calls to the one that supports it.

​
Limitations

  • SOAP: Struggles with large data volumes. Expect degraded read performance on big tenants.
  • REST: Does not support the full set of write operations, so it cannot back a full sync on its own.
  • Rate Limits: Workday rate limits vary by tenant configuration.

​
Testing and Validation

  • Standard testing procedures apply.
  • Confirm which connector the customer has linked before troubleshooting a missing operation — a “not supported” write against the REST connector is expected behaviour, not a bug.

Connection Guides

Setup steps for your customers: Workday Learning (SOAP) · Workday Learning (REST API)