Skip to main content
This page records how composerID publishes into JAGGAER: 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. JAGGAER ONE is a source-to-pay suite (Sourcing, Supplier Management, Contracts, eProcurement) - a system of record for procurement. composerID publishes the canonical decision via JAGGAER’s REST/JSON services (request/response or event-driven push), carrying the Intent ID for correlation; cXML handles transactional documents where used.
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

JAGGAER Integrations (Trust Center)

Integration via JAGGAER Public APIs (PDF)

Advanced Sourcing Optimizer API

Supplier Identity Management (SSO)

​
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.
JAGGAER ONE integration specifics (object/field names, available REST services) are largely provided to customers/partners; the ASO API and the Integration via Public APIs guide are the public entry points. OAuth client credentials are generated per-tenant in the admin panel; cXML SharedSecrets have no rotation API, so schedule manual rotation.

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