> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Workday

> Workday (Vendor Management & Sourcing): the API posture, publish target and field mapping composerID publishes a decision reference through.

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.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Carrier mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                                                                                                                                                                                                                                                                         |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication       | OAuth 2.0 (auth-code + ISU client-credentials) for REST; WS-Security or OAuth via an Integration System User (ISU) for SOAP.                                                                                                                                                                                                                                   |
| composerID publishes | Contingent worker (contract): Contract\_Contingent\_Worker (Staffing SOAP BP)                                                                                                                                                                                                                                                                                  |
| Intent ID lands on   | `job_requisition` `customObject.intentId`, written into the destination record                                                                                                                                                                                                                                                                                 |
| Carrier evidence     | Cited: the vendor documents API-writable custom fields on this object; the field name is configured at onboarding. Source: [Workday Recruiting: Edit\_Job\_Requisition\_Additional\_Data](https://community.workday.com/sites/default/files/file-hosting/productionapi/Recruiting/v47.0/Edit_Job_Requisition_Additional_Data.html), checked 23 September 2026. |
| Back-sync            | Polling: the destination publishes no events composerID can subscribe to, so state is read back on a schedule.                                                                                                                                                                                                                                                 |

## Vendor documentation

<Columns cols={2}>
  <Card title="Workday SOAP API Reference" icon="external-link" href="https://community-content.workday.com/en-us/public/products/platform-and-product-extensions/soap-api-reference.html" horizontal />

  <Card title="Workday Web Services Production Directory" icon="external-link" href="https://community.workday.com/sites/default/files/file-hosting/productionapi/index.html" horizontal />

  <Card title="Contract_Contingent_Worker operation" icon="external-link" href="https://community.workday.com/sites/default/files/file-hosting/productionapi/Staffing/v47.0/Contract_Contingent_Worker.html" horizontal />

  <Card title="Workday REST Directory" icon="external-link" href="https://community.workday.com/sites/default/files/file-hosting/restapi/" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                     |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication | OAuth 2.0 (auth-code + ISU client-credentials) for REST; WS-Security or OAuth via an Integration System User (ISU) for SOAP. Access tokens \~1h; non-expiring refresh tokens configurable. |
| Style          | SOAP (Workday Web Services: primary), REST/JSON (partial subset), RaaS (reports-as-a-service)                                                                                              |
| Base URL       | REST https\://\{host}/ccx/api/\{service}/v\{n}/\{tenant}  \|  SOAP https\://\{host}/ccx/service/\{tenant}/\{WebService}/v\{n}                                                              |
| Webhooks       | No native webhooks. Event-driven via the Business Process Framework, EIB outbound, Studio and Extend. RaaS is poll-based.                                                                  |
| Events posture | Polling                                                                                                                                                                                    |
| Rate limits    | Not officially published; practitioner \~10 req/s per tenant, HTTP 429 + Retry-After. Queue + exponential backoff.                                                                         |
| Objects        | Staffing (Create\_Position, Contract\_Contingent\_Worker, End\_Contingent\_Worker\_Contract), Job Requisition, Position, Worker, Supplier, Purchase Order                                  |

## 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.

<AccordionGroup>
  <Accordion title="Contingent worker (contract)" icon="arrow-right-left" description="Onboard external worker">
    | Mapping                  | Detail                                                |
    | ------------------------ | ----------------------------------------------------- |
    | Canonical to destination | worker, position, start\_date, supplier, job\_profile |
    | Target                   | Contract\_Contingent\_Worker (Staffing SOAP BP)       |
    | Requirement              | Required + tenant BP                                  |
    | Notes                    | Approvals run via the tenant business process         |
  </Accordion>

  <Accordion title="Position (create)" icon="arrow-right-left" description="Create the headcount">
    | Mapping                  | Detail                                |
    | ------------------------ | ------------------------------------- |
    | Canonical to destination | role\_title, org, location, headcount |
    | Target                   | Create\_Position (Staffing SOAP)      |
    | Requirement              | Required                              |
    | Notes                    | Precedes contracting                  |
  </Accordion>

  <Accordion title="End contract" icon="arrow-right-left" description="Offboard / liveness">
    | Mapping                  | Detail                            |
    | ------------------------ | --------------------------------- |
    | Canonical to destination | worker\_id, end\_date, reason     |
    | Target                   | End\_Contingent\_Worker\_Contract |
    | Requirement              | Required                          |
    | Notes                    | Drives liveness + offboarding     |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                                                              |
    | ------------------------ | ----------------------------------------------------------------------------------- |
    | Canonical to destination | intent\_id, intent\_version                                                         |
    | Target                   | Integration reference ID / custom object field on the requisition                   |
    | Requirement              | Required                                                                            |
    | Notes                    | Reference IDs or a tenant custom object carry the correlation; confirmed per tenant |
  </Accordion>
</AccordionGroup>

<Note>
  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.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>