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

# VNDLY

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

This page records how composerID publishes into VNDLY: 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 VNDLY is a cloud-native VMS aligned to the Workday suite. composerID treats VNDLY as a destination system of record (publishing Intent Records and maintaining the audit spine) with tenant mapping validated in a customer sandbox because API documentation is customer/partner-scoped.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                         |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| Authentication       | Customer/partner-provisioned credentials within the Workday ecosystem.                                         |
| composerID publishes | Requisition (Contingent): Customer API (Workday ecosystem)                                                     |
| Intent ID lands on   | `work_order` `customFields.intentId`, written into the destination record                                      |
| 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 VNDLY: product site" icon="external-link" href="https://www.vndly.com/" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                        |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | Customer/partner-provisioned credentials within the Workday ecosystem. Confirm auth flow (OAuth 2.0 / ISU-style integration user) per tenant. |
| Style          | Customer-scoped APIs; public endpoint documentation not confirmed. Workday-suite alignment drives object and required-field conventions.      |
| Base URL       | Provisioned per customer tenant. No public base URL.                                                                                          |
| Webhooks       | Not publicly documented; plan poll-based reconciliation and confirm event options per tenant.                                                 |
| Events posture | Polling                                                                                                                                       |
| Rate limits    | Not publicly documented; defined per tenant/integration agreement.                                                                            |
| Objects        | Requisition, Worker, Assignment, Timesheet, Supplier (per Workday-ecosystem conventions)                                                      |

## 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="Requisition (Contingent)" icon="arrow-right-left" description="Create worker request">
    | Mapping                  | Detail                                                         |
    | ------------------------ | -------------------------------------------------------------- |
    | Canonical to destination | role\_title, location, start\_date, cost\_center, worker\_type |
    | Target                   | Customer API (Workday ecosystem)                               |
    | Requirement              | Tenant required                                                |
    | Notes                    | Workday alignment drives required fields                       |
  </Accordion>

  <Accordion title="Worker / Assignment" icon="arrow-right-left" description="Assignment lifecycle">
    | Mapping                  | Detail                          |
    | ------------------------ | ------------------------------- |
    | Canonical to destination | worker\_id, dates, rate, status |
    | Target                   | Customer API                    |
    | Requirement              | Tenant required                 |
    | Notes                    | Back-sync into intent timeline  |
  </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                   | Custom field on the job posting / work order                                |
    | Requirement              | Required                                                                    |
    | Notes                    | Customer-scoped API: field key agreed with the joint customer at onboarding |
  </Accordion>
</AccordionGroup>

<Note>
  Workday VNDLY documentation is customer/partner-scoped. composerID starts with minimum viable mapping and relies on tenant discovery (required fields, custom fields, code lists) to generate a working MappingProfile.
</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>