Skip to main content

API Managed Integration with SAP Integration Suite


Application Programming Interfaces (APIs) enable integration, interoperability, and data sharing between software systems. With the help of an API management solution like the API Management capability within SAP Integration Suite, you can provide omni-channel and secure access to solutions. Furthermore, it allows you to enforce usage policies for APIs, control API access, analyze API consumption, and more.

This reference architecture is based on the concepts of the SAP Integration Solution Advisory Methodology. API-managed integration is defined as a cross-use case pattern that complements other integration use case patterns.

Architecture​

image of solution diagram
Copy to clipboard
Solution Diagram Resources
You can download the Solution Diagram as a .drawio file for offline use. Alternatively, you may view and edit the Solution Diagram directly on draw.io.
Please note that any changes made online will need to be saved locally if you wish to keep them.

Flow​

The reference architecture diagram illustrates the runtime perspective for API-managed integration across Cloud2Cloud, Cloud2OnPremise, and OnPremise2OnPremise domains. Detailed steps include:

  1. API Gateway Protection: A client application sends an API call intercepted by the API Management capability within SAP Integration Suite, which acts as a protection layer. APIs are exposed as API proxies that abstract endpoint properties and enforce security measures, transformations, governance, and insights.

  2. Predefined API Resources: SAP Business Accelerator Hub provides API policy templates, APIs, predefined integration flows, and more to enable interoperability between API providers and consumers securely.

  3. Managed API Use Case: API requests are forwarded to a data source acting as an API provider. This use case is suited for scenarios requiring simple transformations and protocol adaptations supported by API Management.

  4. Business Data Graph Use Case: The API Composition capability (formerly Graph) of API Management exposes business data as a semantically connected graph. It simplifies consumption across multiple data sources via a unified API.

  5. Cloud Integration Use Case: For advanced mediation and transformation requirements, Cloud Integration capability is used to handle scenarios beyond the scope of API Management.

  6. On-Premise Connectivity: For Cloud2OnPremise scenarios, use SAP Connectivity service with a cloud connector and SAP Destination service to establish secure connections.

  7. Edge Integration Cell: For local data processing (e.g., compliance requirements), edge integration cell runtime allows managing APIs and running integration scenarios within private landscapes. It is deployed in customer-managed Kubernetes environments.

  8. SAP S/4HANA or SAP ECC Integration: Use SAP Application Interface Framework for monitoring and error handling in SAP S/4HANA or SAP ECC integration scenarios.

  9. AI Agents as API Consumers: AI agents, such as Joule agents or third-party MCP clients, call the same governed APIs through the MCP Gateway in SAP Integration Suite. APIs and integration flows are exposed as MCP tools behind the same authentication, traffic, and analytics policies as any other client application. See AI Agents as API Consumers.

Characteristics​

An architecture for API-managed integration is characterized by:

  • Governed API Consumption: Govern the full lifecycle of APIs, enforce policies, ensure compliance, and control the integration process.
  • Decoupled Integration: Abstract APIs from their implementation using API façades, enabling independent evolution of systems without mutual interference.
  • Advanced Protection: Ensure API security through policies, traffic protection, and compliance measures.
  • Visibility and Analytical Insights: Centrally collect and analyze API metrics, with options for monetizing API consumption.
  • Interoperability: Perform transformations and mediations to enable seamless interoperability between API providers and consumers, including simplified consumption via data graphs.
  • Agent-Ready Consumption: Treat AI agents as first-class, governed API consumers rather than bolt-on microservices, using the same policies, identities, and analytics as other client applications.

API Composition and Authentication Choices​

API Composition is the current name of the former Graph capability. It exposes a semantically connected Business Data Graph through a unified API. Distinguish this capability from integration logic composed inside an API-centric artifact. See API Composition release information.

For APIs authenticated by an external OAuth/OIDC provider, define the trusted issuer, intended audiences, and authorization requirements for the target runtime and policy. The external OAuth Authentication Policy supports optional or multiple audience values; optional configuration does not remove the need to decide which consumers should be accepted. Test rejected tokens and insufficient permissions as well as successful calls. See API Management authentication updates.

AI Agents as API Consumers​

AI agents are now direct consumers of enterprise APIs. In an API-managed architecture, they should be treated as first-class integration participants, governed with the same rigor as any other client application, not as bolt-on microservices that call back-end systems directly.

The MCP Gateway in SAP Integration Suite is the agent-facing entry point. It exposes SAP and non-SAP APIs, integration flows, and remote MCP servers as governed, MCP-compliant tools. For the architecture of the gateway itself and the supported MCP server creation paths, see A2A and MCP. For connecting external agent platforms, see Third-Party MCP Access.

When adding agents as API consumers, apply the following principles:

  • One governance plane: Expose agent tools from the same API proxies and integration flows that serve other channels, so authentication, rate limiting, payload protection, and analytics are enforced once. Avoid separate point-to-point paths created only for agents.
  • Zero Trust by default: Authenticate every agent call with OIDC, validate the token issuer and audience at the gateway, and propagate the user's identity where the back end needs to apply its own authorizations. Grant agents least-privilege access to the specific operations a business task needs. See AI Agent Identity.
  • Curated tool surface: Select only the operations an agent needs, and review tool names, descriptions, and input schemas, because agents choose tools based on this metadata.
  • Observability: Monitor tool usage, errors, and latency through API and MCP analytics to support compliance and adoption governance.

API Composition and SAP Knowledge Graph​

API Composition (formerly Graph) and SAP Knowledge Graph serve different purposes and should not be confused:

  • API Composition exposes a semantically connected Business Data Graph through a unified API at runtime. As an API, it can be governed and exposed to agents like any other API in this architecture.
  • SAP Knowledge Graph provides the ontology and semantic layer over SAP data products that grounds Joule and AI agents in business meaning.

Examples in an SAP Context​

SAP does not deliver predefined integration scenarios for API-managed integration. Customers and partners typically implement API management solutions for reasons such as:

  • Achieving a consistent and harmonized omni-channel experience.
  • Managing and protecting business-critical API assets.
  • Simplifying integration with SAP and other API providers.
  • Realizing revenue in the cloud-native economy.

Services and Components​

Resources​