SAP API overview
SAP exposes its data and logic through several API technologies, from the modern OData/REST interfaces used by Fiori and cloud integration, to classic BAPI, RFC and IDoc mechanisms. This hub maps them so you can choose the right one.
SAP exposes its data four ways: OData for Fiori and modern REST integration, SOAP for classic web services, BAPI and RFC for SAP-to-SAP and program-level access, and IDoc with ALE for asynchronous, high-volume document exchange. The released APIs for S/4HANA, the cloud products and BTP are documented on the SAP Business Accelerator Hub.
- Watch out: Wrong API for the job (e.g. synchronous where async is needed).
The API landscape
- OData (REST): the modern standard for web/mobile and Fiori.
- SOAP web services: XML-based, for enterprise SOA integration.
- BAPI/RFC: classic function-based access, still widely used.
- IDoc/ALE: document-based, asynchronous integration.
- SAP Graph / public APIs: unified, cloud-era access via the API Business Hub.
Choosing an API
Use OData for UIs and modern REST integration, SOAP for classic web-service SOA, BAPI/RFC for SAP-to-SAP and program-level access, and IDoc for robust, asynchronous, high-volume document exchange (EDI). The right choice depends on the consumer, the volume, and whether you need synchronous or asynchronous, guaranteed delivery.
The API Business Hub
SAP publishes its released APIs (for S/4HANA, cloud products and BTP) on the SAP Business Accelerator Hub, with documentation and try-it-out. Preferring released, public APIs keeps integrations stable and clean-core-compliant.
Common pitfalls
- Wrong API for the job (e.g. synchronous where async is needed).
- Using unreleased/internal interfaces.
- Ignoring the API Business Hub for released APIs.