SAP REST Integration
REST/OData integration connects systems to SAP over HTTP with JSON, the modern, lightweight style used for cloud, web and mobile integration. In SAP this typically means calling or exposing OData services.
REST integration exchanges JSON over HTTP with standard verbs, either an external system calling SAP's OData or REST APIs or SAP calling out through CPI on BTP, secured with OAuth tokens and trimmed with query options. It suits real-time, lightweight web, mobile and cloud scenarios; asynchronous document exchange belongs on IDoc and SAP-to-SAP program calls on RFC and BAPI.
- OData/REST APIs as endpoints.
- JSON payloads and HTTP verbs.
- Watch out: REST carries no contract of its own, so both sides must agree the payload out of band.
What REST integration does
REST integration exchanges JSON over HTTP using standard verbs, either external systems calling SAP’s OData/REST APIs, or SAP (via CPI/BTP) calling external REST services. It is simple, widely supported, and ideal for real-time, request/response integration.
Key aspects
- OData/REST APIs as endpoints.
- JSON payloads and HTTP verbs.
- OAuth/token security.
- Query options for efficient data access.
When to use it
Use REST for real-time, lightweight, web/mobile and cloud integration. For robust async document exchange prefer IDoc; for SAP-to-SAP program calls, RFC/BAPI; REST/OData shines for modern, service-based scenarios.
Common pitfalls
- Wrong tool for the integration style.
- Ignoring monitoring/error handling.
- Point-to-point instead of governed integration.