Skip to main content
This page records how composerID publishes into Ivalua: 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. Ivalua is a unified source-to-pay suite - a system of record for sourcing, contracts, orders and invoices - with a highly configurable open data model. composerID publishes the canonical decision into the relevant object (Sourcing event, Contract, or Requisition/Order) via Ivalua’s REST services and Integration Hub, carrying the Intent ID for correlation.
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

Ivalua Open Ecosystem

Procurement Platform / Integration Hub

Multi-ERP Integration

​
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.
Ivalua’s data model is highly configurable per client - object and field names are not fixed across tenants, so mapping requires each customer’s configured schema and an issued API key. The full REST API reference is provided to customers/partners rather than via a public developer portal; the Open Ecosystem page is the public entry point.

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