Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: public developer portal.
Integration path
How composerID connects to this destination, at a glance.Vendor documentation
The Coupa Core API (Compass)
Coupa Core API: Get Started
OAuth 2.0 and OIDC
Exception handling & rate limits
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.Requisition (Contingent)
Create external worker request
Requisition (Contingent)
Create external worker request
Statement of Work
Services / SOW engagement
Statement of Work
Services / SOW engagement
Intent ID correlation
Carry the Intent ID
Intent ID correlation
Carry the Intent ID
Purchase Order
Read for back-sync
Purchase Order
Read for back-sync
SOW / Contingent Workforce is not a distinct top-level REST resource; confirm the CCW module resource name in your tenant. Each customer has a separate sandbox instance with its own OAuth clients and scopes.
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.