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
Globality Developer API
Integration overview
OpenAPI spec (spec.json)
Webhooks overview
Webhooks documentation (PDF, v5)
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.Project (create)
Container for sourcing intent
Project (create)
Container for sourcing intent
Brief (read)
Scoped requirement
Brief (read)
Scoped requirement
Award (read)
Outcome / receipt
Award (read)
Outcome / receipt
Intent ID correlation
Carry the Intent ID
Intent ID correlation
Carry the Intent ID
Public docs + OpenAPI, but credentials are customer-gated (an admin assigns the in-app Developer role). Region-specific base URLs and Auth0 audience per environment. The API is read-centric: Project create + status update only; there is no public endpoint to push your own supplier lists. Pre-built connectors exist for Ariba, Fieldglass and Coupa.
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.