SAP APIs · Lesson

API overview

Quick answer

SAP publishes its released APIs (for S/4HANA, cloud products and BTP) on the SAP Business Accelerator Hub, with documentation and try-it-out.

Key takeaways

Use OData for UIs and modern REST integration, SOAP for classic web-service SOA, BAPI/RFC for SAP-to-SAP and program-level access…
OData (REST): the modern standard for web/mobile and Fiori.
SOAP web services: XML-based, for enterprise SOA integration.
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.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

Which statement is true of API overview?
- A. Use OData for UIs and modern REST integration, SOAP for classic web-service SOA, BAPI/RFC for SAP-to-SAP and…
- B. SAP skills command strong, stable pay because the platform is mission-critical and skilled talent is scarce.
- C. MM03 is the SAP transaction code for Display Material (MM).
Show answer
A. Use OData for UIs and modern REST integration, SOAP for classic web-service SOA, BAPI/RFC for SAP-to-SAP and…
Covered in the “Choosing an API” section of this lesson.
Which of these also applies to API overview?
- A. Confusing embedded and hub setups.
- B. Using the wrong variant (e.g. create vs change vs display).
- C. The right choice depends on the consumer, the volume, and whether you need synchronous or asynchronous…
Show answer
C. The right choice depends on the consumer, the volume, and whether you need synchronous or asynchronous…
Covered in the “Choosing an API” section of this lesson.
Which part of the Learn SAP curriculum covers API overview?
- A. SAP labs
- B. SAP APIs
- C. SAP navigation
Show answer
B. SAP APIs
This lesson sits in the SAP APIs section of the Learn SAP course.

Frequently asked questions

What does the term API overview refer to in SAP?

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.

What is connected to API overview in an SAP 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.

What is another point to note about API overview?

SAP publishes its released APIs (for S/4HANA, cloud products and BTP) on the SAP Business Accelerator Hub, with documentation and try-it-out.

What tends to go wrong with API overview?

Wrong API for the job (e.g. synchronous where async is needed). Using unreleased/internal interfaces. Ignoring the API Business Hub for released APIs.