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

# SAP BTP

> SAP BTP (Systems Integrations): the API posture, publish target and field mapping composerID publishes a decision reference through.

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

SAP Business Technology Platform is a generic integration platform, not a single API. composerID treats it as a connectivity fabric: fronting backend systems via API Management, resolving targets via Destinations, authenticating with XSUAA, and receiving callbacks via Event Mesh.

<Info>
  Category: Systems Integrations. Coverage status: Specification mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                            |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Authentication       | OAuth 2.0 via XSUAA.                                                                                              |
| composerID publishes | Destination (resolve): /destination-configuration/v1/destinations/\{name}                                         |
| Intent ID lands on   | `integration_flow` `headers.intentId`, held by composerID against the destination record                          |
| Back-sync            | Webhooks: the destination pushes events; composerID verifies each delivery and lands it on the intent's timeline. |

## Vendor documentation

<Columns cols={2}>
  <Card title="SAP BTP platform docs" icon="external-link" href="https://help.sap.com/docs/btp/sap-business-technology-platform" horizontal />

  <Card title="Integration Suite: OData API" icon="external-link" href="https://help.sap.com/docs/integration-suite/sap-integration-suite/odata-api" horizontal />

  <Card title="Destination service REST API" icon="external-link" href="https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/calling-destination-service-rest-api" horizontal />

  <Card title="Event Mesh: messaging protocols" icon="external-link" href="https://help.sap.com/docs/event-mesh/event-mesh/messaging-protocols-and-libraries" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                              |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | OAuth 2.0 via XSUAA. A service key yields clientid / clientsecret / url, then \{url}/oauth/token with client\_credentials.                          |
| Style          | Mixed: OData V2 (Cloud Integration management), REST/JSON (Destination), REST/OData/SOAP proxies (API Management), AMQP/MQTT/REST (Event Mesh)      |
| Base URL       | https\://\{subaccount}-tmn.\{region}.hana.ondemand.com/api/v1/...  (tenant + region specific)                                                       |
| Webhooks       | Yes: Event Mesh (AMQP 1.0 / MQTT 3.1.1 / HTTP-REST) supports webhook delivery; Advanced Event Mesh for high-throughput streaming. Push + poll.      |
| Events posture | Webhooks                                                                                                                                            |
| Rate limits    | No platform-wide figure; API Management is itself the rate-limiter (Quota / Spike Arrest policies you configure). Per service plan.                 |
| Objects        | Integration iFlows (IntegrationDesigntimeArtifacts / RuntimeArtifacts), API Proxies / Products, Destinations, Event Mesh queues / topics / webhooks |

## 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="Destination (resolve)" icon="arrow-right-left" description="Find the backend">
    | Mapping                  | Detail                                             |
    | ------------------------ | -------------------------------------------------- |
    | Canonical to destination | target\_system\_name                               |
    | Target                   | /destination-configuration/v1/destinations/\{name} |
    | Requirement              | Required                                           |
    | Notes                    | Resolves URL + auth at runtime                     |
  </Accordion>

  <Accordion title="iFlow (publish)" icon="arrow-right-left" description="Map + deliver">
    | Mapping                  | Detail                                 |
    | ------------------------ | -------------------------------------- |
    | Canonical to destination | canonical payload                      |
    | Target                   | Cloud Integration iFlow endpoint       |
    | Requirement              | Tenant build                           |
    | Notes                    | Field mapping happens inside the iFlow |
  </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                   | Propagated as a header/property through the integration flow                             |
    | Requirement              | Required                                                                                 |
    | Notes                    | BTP is transit, not a system of record: the durable carrier is the target system's field |
  </Accordion>

  <Accordion title="Event subscription" icon="arrow-right-left" description="Back-sync">
    | Mapping                  | Detail                            |
    | ------------------------ | --------------------------------- |
    | Canonical to destination | topic / queue                     |
    | Target                   | Event Mesh webhook                |
    | Requirement              | Optional                          |
    | Notes                    | Receives backend status callbacks |
  </Accordion>
</AccordionGroup>

<Note>
  Public docs, account-gated provisioning (global account to subaccount to service instances + keys). Hostnames embed tenant + region. A free / trial tier and the Business Accelerator Hub sandbox are available. For VMS use, front each backend behind API Management + Destinations + Event Mesh.
</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>