Skip to main content
This page records how composerID publishes into Workday: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Workday is the worker and staffing system of record. composerID contracts contingent workers through the Staffing business-process operations; writes are largely SOAP-only, while reads are available via REST and RaaS.
Category: Vendor Management & Sourcing. Coverage status: Carrier mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Vendor documentation

Workday SOAP API Reference

Workday Web Services Production Directory

Contract_Contingent_Worker operation

Workday REST Directory

API posture

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
Pin a WWS version (e.g. v46.1) in every endpoint. Requires an ISU + integration security group + registered API client. Implementation and production tenants use different hosts.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.