> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Ivalua

> Ivalua (Vendor Management & Sourcing): the API posture, publish target and field mapping composerID publishes a decision reference through.

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.

<Info>
  Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                   |
| -------------------- | ---------------------------------------------------------------------------------------- |
| Authentication       | Customer-provisioned API keys; SSO via SAML/OIDC for user contexts.                      |
| composerID publishes | Sourcing / RFx: Ivalua Sourcing REST service                                             |
| Intent ID lands on   | `requisition` `customFields.intentId`, written into the destination record               |
| Back-sync            | Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule. |

## Vendor documentation

<Columns cols={2}>
  <Card title="Ivalua Open Ecosystem" icon="external-link" href="https://www.ivalua.com/technology/ivalua-open-ecosystem/" horizontal />

  <Card title="Procurement Platform / Integration Hub" icon="external-link" href="https://www.ivalua.com/technology/procurement-platform/" horizontal />

  <Card title="Multi-ERP Integration" icon="external-link" href="https://www.ivalua.com/solutions/business/multi-erp-integration/" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                 |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication | Customer-provisioned API keys; SSO via SAML/OIDC for user contexts. Access is enabled per customer (an API key is issued on request).                  |
| Style          | REST web services, JSON & XML; also AS2 / SFTP / HTTPS batch; Integration Hub + Console for orchestration and monitoring                               |
| Base URL       | Per-tenant Ivalua instance (customer-specific host)                                                                                                    |
| Webhooks       | Integration Hub orchestration plus Integration Console transaction monitoring; event / ETL / EAI patterns rather than a single public webhook catalog. |
| Events posture | Webhooks and polling                                                                                                                                   |
| Rate limits    | Tenant/deployment-specific; governed via the Integration Console.                                                                                      |
| Objects        | Suppliers, Sourcing/RFx, Contracts, Requisitions, Orders, Invoices, Catalogs, Items, Performance evaluations (open, configurable data model)           |

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

<AccordionGroup>
  <Accordion title="Sourcing / RFx" icon="arrow-right-left" description="Open a sourcing event">
    | Mapping                  | Detail                                         |
    | ------------------------ | ---------------------------------------------- |
    | Canonical to destination | service\_category, sow\.summary, dates, budget |
    | Target                   | Ivalua Sourcing REST service                   |
    | Requirement              | Tenant                                         |
    | Notes                    | For competitively-sourced services             |
  </Accordion>

  <Accordion title="Contract" icon="arrow-right-left" description="Create or land a contract">
    | Mapping                  | Detail                                                       |
    | ------------------------ | ------------------------------------------------------------ |
    | Canonical to destination | counterparty, dates, budget, terms                           |
    | Target                   | Ivalua Contract REST service                                 |
    | Requirement              | Tenant                                                       |
    | Notes                    | Object/field names follow the tenant's configured data model |
  </Accordion>

  <Accordion title="Requisition / Order" icon="arrow-right-left" description="Commit spend">
    | Mapping                  | Detail                                       |
    | ------------------------ | -------------------------------------------- |
    | Canonical to destination | cost\_center, amount, supplier, start\_date  |
    | Target                   | Ivalua Requisition/Order REST service        |
    | Requirement              | Tenant                                       |
    | Notes                    | Read Orders/Invoices back for reconciliation |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                                                   |
    | ------------------------ | ------------------------------------------------------------------------ |
    | Canonical to destination | intent\_id, intent\_version                                              |
    | Target                   | Custom field on the sourcing / requisition object                        |
    | Requirement              | Required                                                                 |
    | Notes                    | Ivalua's data model is customer-extended; field key agreed at onboarding |
  </Accordion>
</AccordionGroup>

<Note>
  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.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>