SAP BTP

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.

Category: Systems Integrations. Coverage status: Specification mapped. Vendor documentation: public developer portal.

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

SAP BTP platform docs

Integration Suite: OData API

Destination service REST API

Event Mesh: messaging protocols

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.

Destination (resolve)

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

iFlow (publish)

Map + deliver

Mapping	Detail
Canonical to destination	canonical payload
Target	Cloud Integration iFlow endpoint
Requirement	Tenant build
Notes	Field mapping happens inside the iFlow

Intent ID correlation

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

Event subscription

Back-sync

Mapping	Detail
Canonical to destination	topic / queue
Target	Event Mesh webhook
Requirement	Optional
Notes	Receives backend status callbacks

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.

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.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

SAP BTP platform docs

Integration Suite: OData API

Destination service REST API

Event Mesh: messaging protocols

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

SAP BTP platform docs

Integration Suite: OData API

Destination service REST API

Event Mesh: messaging protocols

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps