Skip to main content
This page records how composerID publishes into Keelvar: 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. Keelvar is a sourcing optimisation and autonomous sourcing platform: buyers run RFx events and auctions with lots, bid sheets and optimisation scenarios in Sourcing Optimizer, and Sourcing Automation bots run tactical events end to end from a requisition, handing awards back to the buyer’s source-to-pay suite. Keelvar markets API-based integration with SAP Ariba, Coupa, JAGGAER and Ivalua, but publishes no self-service endpoint reference, so path-level detail is confirmed per tenant. composerID publishes an approved services or managed-service decision as the sourcing event Keelvar runs, writes the Intent ID as a fixed token in the event description, and records the event id linkage on its own side until a reference field is confirmed at onboarding.
Category: Procurement Orchestration. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation). No developer portal is evident.

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

Keelvar (vendor site)

Keelvar integrations (source-to-pay suites)

​
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.
Keelvar’s public material describes integration capability, not an endpoint reference: base URL, credentials, the token model, rate limits and any event-out mechanism are provisioned per tenant at onboarding, and every path-level claim here is indicative until then. Event templates, bid sheets, lot structure and supplier lists are tenant-configured, and awards flow to the buyer’s source-to-pay suite (SAP Ariba, Coupa, JAGGAER or Ivalua) through Keelvar’s own connectors, so the PO or contract of record lives there, not in Keelvar. At onboarding, check whether the tenant’s event template exposes a reference or custom field; if it does, move the Intent ID off the description into that field and switch the carrier from link to stamp.

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