Skip to main content
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.
Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

Workday VNDLY: product site

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

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