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

# ORO Labs

> ORO Labs (Procurement Orchestration): the API posture, publish target and field mapping composerID publishes a decision reference through.

This page records how composerID publishes into ORO Labs: 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.

ORO Labs is an AI procurement-orchestration platform built on an embedded iPaaS. Rather than one public REST object model, ORO federates 200+ semantically rich integrations across ERP, procure-to-pay, contract and risk systems. composerID maps canonical intent onto ORO's intake-request and workflow objects so services and contingent demand enter the orchestrated source-to-pay flow.

<Info>
  Category: Procurement Orchestration. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation). No developer portal is evident.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                         |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| Authentication       | SSO + role-based access control with encryption; SOC 1, SOC 2 and ISO 42001 (responsible AI) certified.        |
| composerID publishes | Intake request: Intake request (orchestrated workflow)                                                         |
| Intent ID lands on   | `intake_request` `workflowFields.intentId`, held by composerID against the destination record                  |
| Back-sync            | Polling: the destination publishes no events composerID can subscribe to, so state is read back on a schedule. |

## Vendor documentation

<Columns cols={2}>
  <Card title="ORO Labs: Integrations" icon="external-link" href="https://www.orolabs.ai/platform/integrations" horizontal />

  <Card title="ORO Labs: Platform overview" icon="external-link" href="https://www.orolabs.ai/platform/overview" horizontal />

  <Card title="ORO Labs: Intake management" icon="external-link" href="https://www.orolabs.ai/solutions/intake-management" horizontal />

  <Card title="ORO Labs: Agentic AI" icon="external-link" href="https://www.orolabs.ai/platform/agentic-ai" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                         |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | SSO + role-based access control with encryption; SOC 1, SOC 2 and ISO 42001 (responsible AI) certified. API credentials are provisioned per customer: no public self-service developer portal. |
| Style          | Embedded iPaaS connectors (semantically rich: the platform understands suppliers, line items and contracts) rather than a single public REST surface; workflow triggers + real-time data sync. |
| Base URL       | Per-customer tenant, provisioned at onboarding. No public base URL.                                                                                                                            |
| Webhooks       | Real-time data sharing and activity triggering across systems via the embedded iPaaS; event-driven workflow triggers. Delivery specs provisioned per integration.                              |
| Events posture | Polling                                                                                                                                                                                        |
| Rate limits    | Not publicly documented; defined per integration.                                                                                                                                              |
| Objects        | Intake request, Approval, Supplier, Contract, Risk assessment, Purchase Order, Invoice (source-to-pay)                                                                                         |

## 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="Intake request" icon="arrow-right-left" description="Start the orchestration">
    | Mapping                  | Detail                                           |
    | ------------------------ | ------------------------------------------------ |
    | Canonical to destination | service\_category, sow\.summary, budget, dates   |
    | Target                   | Intake request (orchestrated workflow)           |
    | Requirement              | Required                                         |
    | Notes                    | Routes through the configured source-to-pay flow |
  </Accordion>

  <Accordion title="Supplier" icon="arrow-right-left" description="Resolve + risk">
    | Mapping                  | Detail                               |
    | ------------------------ | ------------------------------------ |
    | Canonical to destination | supplier\_name, tax\_id, risk\_flags |
    | Target                   | Supplier object + risk assessment    |
    | Requirement              | Tenant required                      |
    | Notes                    | Risk / onboarding gates progression  |
  </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                   | Intake workflow field (configured per customer)                                               |
    | Requirement              | Required                                                                                      |
    | Notes                    | No public API surface: linkage recorded on the composerID side, field write via ORO connector |
  </Accordion>

  <Accordion title="Contract / PO" icon="arrow-right-left" description="Back-sync">
    | Mapping                  | Detail                                      |
    | ------------------------ | ------------------------------------------- |
    | Canonical to destination | contract\_ref, po\_lines, amount, status    |
    | Target                   | Contract + PO via iPaaS connector           |
    | Requirement              | Read                                        |
    | Notes                    | Synced from the downstream ERP / P2P system |
  </Accordion>
</AccordionGroup>

<Note>
  ORO is an orchestration layer, not a transactional system of record: it federates to your ERP / P2P (SAP, Oracle, NetSuite, Coupa, Ariba, JAGGAER, GEP) through its embedded iPaaS. There is no public REST object catalogue; integration is delivered via ORO's connector framework and provisioned per customer. Public API, auth and webhook specifications are not published.
</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>