onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
ServiceServicetypeA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

API Composition

FormerlyGraphuntil

One API over the business data in a landscape: a business data graph queried with OData V4 or GraphQL, instead of each source system's own API.

API Composition unifies business APIs into a semantically connected data graph — SAP's name for it is a business data graph — and serves it as a single API, so a query navigates and expands relationships across systems rather than the application calling each source and joining the results itself. SAP's out-of-the-box graph of SAP-managed data is the baseline you extend into your own. Two protocol adapters sit on the same metadata: OData V4, and GraphQL, which SAP marks early general availability with limitations against the OData interface. It stores nothing — SAP describes a stateless multitenant service that breaks a navigation query up and calls the data sources' own APIs on the application's behalf. It is a capability of API Management inside SAP Integration Suite and is activated there. SAP renamed it from Graph on 2026-07-06; documentation, blog posts and code written before that date say Graph for the same thing.

Homepage
Docs

Where it sits

Lives in
BTP/BAIP
Part of
API ManagementAPI ManagementartifactAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer

What it declares

Every artifact

Type
Service
Origin
By SAP

As a service

Plans
2
Regions
22
Support component
BC-CP-IS-GRAPH

Tasks this contributes to1Beta

Serve your application over MCP1

Connections2

Download
API Composition connectionsAPI CompositionUSED BY← connected from1connected from derived Its one tool issues an HTTPS GET for sales orders against the sandbox host of SAP's business data graph, with the key in an apikey header and six fields named in the query. Through: inverted from its connects edge CostingGeek/sap-mcp — README, How It Works: https://github.com/CostingGeek/sap-mcp CostingGeek/sap-mcp — saptools.py: https://github.com/CostingGeek/sap-mcp/blob/main/saptools.pyCostingGeek/sap-mcpLINEAGE→ part of1part of stated What Is API Composition? — SAP Integration Suite documentation, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_API_Composition/what-is-api-composition-456fc54.md What's New for API Composition? — Graph is Now API Composition, SAP-docs/btp-integration-suite: https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_API_Composition/what-s-new-for-api-composition-361c04f.mdAPI Management

Learn more2

Readings
  1. Build a Supply Risk API with API CompositionShyam, SAP Developer Center
  2. API Composition: Seamless Enterprise Data Access for Developers and AI AgentsPalak, SAP Community
What changed

  1. SAP renamed the Graph capability of API Management to API Composition, and states in the same entry that all existing features and functionality remain unchanged. The documentation, the navigator and the help URLs moved to the new name; the older name survives in paths and in everything written earlier.

    Makes stale:

    Searching the current documentation for Graph, and reading a page that says Graph as a page about something else. Nothing about the behaviour moved, so a source using the old name is out of date on the name alone and predates 2026-07-06.

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
History in the atlas2
  1. An impact assessment of CostingGeek/sap-mcp found the API the whole entry rests on had no node: the prose named SAP Graph and nothing pointed at it. Written from SAP's own API Composition documentation in SAP-docs/btp-integration-suite, pinned at commit 33f3395. No provides edge yet — the capabilities the atlas holds for serving OData and GraphQL are scoped to the CAP and ABAP doors and describe serving your own model, which is a different concern from composing several systems' APIs; whether this answers an existing capability or needs one is an editorial call.
  2. First seen.
For your agent
Ref
artifact:btp-api-composition
JSON
/artifacts/btp-api-composition.json
MCP
Connecting an agent