Integrating SAP with Mobile Apps: OData, BAPI, BTP

Error 403 due to CSRF token or session timeout when integrating SAP with a mobile app is a typical problem even experienced teams face. Nearly every second project comes to us after a failed attempt to 'do it ourselves.' SAP mobile app integration, whether using SAP OData mobile, SAP BAPI mobile, or other protocols, requires understanding the SAP landscape: different versions (ECC 6.0, S/4HANA on-premise or Cloud), protocols (OData v2, v4, BAPI), and security requirements (OAuth 2.0, SAML). Over 10 years of experience and 30+ successful projects, we have developed an approach that is 3 times faster than building your own middleware. The key lesson: do not start coding without an API audit and proper middleware selection — a mistake that costs weeks of rework. A typical audit costs $2,000 and takes 3-5 days.

SAP Mobile Services is not just middleware but a full platform that accelerates integration by 3x thanks to built-in caching, authentication, and offline synchronization mechanisms. Unlike custom Spring Boot solutions, it eliminates manual CSRF token handling, session management, and conflict resolution. But proper configuration is essential: a common mistake is ignoring synchronization policies, which leads to data loss on connection drops. For push notifications, we use Firebase Cloud Messaging (FCM) on Android and Apple Push Notification Service (APNs) on iOS, integrated with SAP Mobile Services.

Three Generations of SAP API: Comparison

How to Set Up CSRF Handling in a Mobile App?

The standard workflow with CSRF token in SAP OData consists of four steps. First, perform a GET request to the service endpoint with the header X-CSRF-Token: Fetch. SAP returns the token in the response header X-CSRF-Token. For all modifying requests (POST, PUT, DELETE, PATCH), include the obtained token in the header X-CSRF-Token. Upon receiving a 403 CSRF token validation failed, repeat steps 1-3. We implement this algorithm in an Interceptor on Retrofit or Alamofire, automatically refreshing the token on error. The token is valid within a session, so after re-authentication, a new token must be fetched. This eliminates 90% of authorization errors.

Example using the SDK on Android:

val serviceManager = ServiceManager(
    applicationContext,
    SAPServiceManager.configUrl,
    object : ServiceManager.ServiceManagerListener {
        override fun onServiceManagerReady() {
            // Ready to work
            initializeODataService()
        }
    }
)

How to Implement Offline Synchronization with SAP?

Using the OData Offline Store from SAP BTP SDK reduces mobile data usage by 60-70% compared to a constant connection. According to official documentation of SAP BTP SDK, offline synchronization requires configuring conflict policies. Data is cached locally in SQLite, and when the network is available, bidirectional synchronization is performed. Conflicts are resolved via ETag — the server checks whether the data has changed since the last read. However, offline mode increases integration complexity: synchronization policies must be properly configured. We choose a first writer or server version strategy depending on the business logic.

Authentication Methods: SAML vs OAuth

We recommend adding an OAuth 2.0 proxy via SAP BTP or Keycloak: the mobile app uses standard OAuth, while SAP receives SAML requests. This reduces integration fragility.

Choosing an API for Integration

If the client has S/4HANA Cloud, OData v4 via CAP is the clear choice. If ECC or S/4HANA on-premise, check for SAP Gateway. Gateway provides SAP ECC OData v2 but with quirks: Edm.DateTime instead of ISO 8601, specific filtering, __deferred for navigation properties. For ECC without Gateway, BAPI via middleware (SAP JCo or NCo) remains. An abstraction layer in middleware is mandatory if support for both variants is needed. For a robust SAP mobile application, offline sync is essential. Enterprise resource planning (ERP) mobile integration, specifically SAP, is complex.

What's Included in the Work

• API and integration architecture documentation
• Access to SAP BTP or middleware (if needed)
• Training the customer's team on solution operation
• 3 months of warranty support after deployment

Process of Work

1. Audit of SAP landscape and available APIs — 3-5 days. Determine SAP version, check OData Gateway or BAPI availability, test performance.
2. Integration architecture design — 1-2 weeks. Select stack (BTP SDK, offline strategy, authentication method).
3. Prototype implementation — 1-2 weeks. Data reading, authentication setup, basic synchronization.
4. Full integration — 2-4 months. Add offline support, CSRF handling, conflict resolution, push notifications.
5. Documentation and team training — 1-2 weeks. Hand over API, configuration, and operation documentation.
6. Warranty support — 3 months after deployment. Fix errors, assist with modifications.

Cost is calculated individually after the audit. Order a prototype in 2 weeks — we'll show a working solution on your data. Contact us for an audit of your SAP landscape and get a detailed integration plan. We guarantee up to 50% reduction in integration costs compared to self-made solutions.

How to Start Integrating API into a Mobile App?

The request goes out, the response doesn't come, timeout — 30 seconds. The user stares at the spinner. No network — mobile card in the subway. Or the network is there, but the server returns 200 with an HTML error page instead of JSON — and the app crashes on JSONDecoder.decode(). We see such cases on every second project. So integrating API into a mobile app is not just calling an endpoint, but designing a reliable network layer: error handling, caching, offline mode, certificate pinning. Order an audit of your current network layer — we will evaluate the project in 1 day. Our team guarantees a thorough analysis and provides a detailed roadmap.

Standard libraries like URLSession and OkHttp provide basic HTTP clients, but for production you need retries with exponential backoff, status code validation, typed deserialization, and network state monitoring. Without this, the app loses data and users. We have been doing mobile development for 5 years and implemented more than 30 projects with API integration on iOS, Android, and Flutter — from startups to enterprise solutions.

How to Choose a Protocol for API Integration?

REST remains the standard for most projects. But when a profile screen needs 5 fields out of 40, GraphQL eliminates over-fetching and reduces traffic by 30–60%. gRPC is justified for thousands of requests per minute (trading, IoT) — binary serialization is 3–5 times faster than JSON. WebSocket is the only choice for real-time without polling (messages, notifications).

Practical example: For a fintech app, we replaced REST (40 fields) with GraphQL — response size dropped from 12 KB to 2.5 KB, screen render time decreased by 70%. Traffic savings were significant. Our certified iOS and Android developers have deep experience with all these protocols — you can rely on proven solutions.

How to Ensure Reliable Connection and Offline-First?

Users lose network in the subway, elevator, tunnel. A mobile app must work without internet — at least in read-only mode. We implement the offline-first pattern:

1. On screen open, first show data from the local cache (Core Data / Room).
2. Simultaneously perform a network request, update UI after response.
3. If network is unavailable — show cached data and a 'no connection' label.
4. When network is restored, automatically synchronize changes.

For HTTP response caching we use URLCache (iOS) and OkHttp Cache (Android) with Cache-Control support. For structured data — SwiftData / Room. NWPathMonitor / ConnectivityManager.NetworkCallback monitor network state and trigger updates.

REST and Client Library Selection

Alamofire (iOS) — de facto standard for Swift projects. On top of URLSession it adds request chaining, response validation, automatic retry, certificate pinning via ServerTrustManager. AF.request() with .validate() returns an error for any status code outside 200–299. Without .validate(), Alamofire considers 404 and 500 as successful responses. With Swift Concurrency — async version via serializingDecodable.

Retrofit (Android) — annotation-based HTTP client on top of OkHttp. An interface with annotations compiles into implementation. @GET, @POST, @Path, @Query, @Body — declarative API description. OkHttp under the hood: connection pooling, transparent gzip, HTTP/2 multiplex. HttpLoggingInterceptor — logging in debug builds. Authenticator — automatic token refresh on 401.

Ktor (KMM/Flutter) — multiplatform HTTP client. On iOS it works via Darwin engine (URLSession), on Android — via OkHttp. Single code for both platforms with KMM architecture.

GraphQL: When REST Falls Short

REST returns a fixed structure. A profile screen needs name, avatar, email — the server sends 40 fields. Over-fetching. GraphQL solves this: the client requests exactly the needed fields. This is critical for mobile where traffic and parsing time are real constraints. Apollo iOS and Apollo Kotlin generate typed classes from schema: schema.graphql + query files → strict types at compile time. Subscriptions via WebSocket — real-time without polling. Limitation: GraphQL is harder to cache at the HTTP level. Apollo uses a normalized in-memory cache InMemoryNormalizedCache — requests with overlapping data update the cache without duplication.

WebSocket: Real-Time Without Extra Traffic

Polling (setInterval every 5 seconds) — battery and traffic waste. WebSocket is a persistent bidirectional connection. iOS: URLSessionWebSocketTask (native, iOS 13+). Android: OkHttp WebSocket. Mandatory reconnect handling: on onFailure — exponential backoff (1s → 2s → 4s → 8s → max 60s). Socket.IO is an overlay with automatic reconnect, but for new projects native WebSocket is preferable (fewer dependencies).

gRPC: For High-Load Services

gRPC with protobuf — binary serialization: smaller size, faster parsing. grpc-swift for iOS, grpc-kotlin for Android. The protobuf schema compiles to typed classes. Streaming (server-side, client-side, bidirectional) is a native feature. Application threshold: high request frequency (trading, IoT) or critical latency. For regular CRUD, REST is simpler to debug and monitor.

Certificate Pinning and Security

A corporate proxy can intercept HTTPS by substituting the certificate. Certificate pinning prevents this: the app accepts only a specific certificate or public key. Alamofire: ServerTrustManager with PinnedCertificatesTrustEvaluator. OkHttp: CertificatePinner with SHA-256 hash. Apple's App Transport Security documentation recommends pinning certificates for sensitive data. Operational complexity: on certificate rotation, older app versions stop working. Solution — pinning to the CA public key or support multiple pins with a grace period.

What Is Included in the Work

We deliver: source code of the network layer, documentation on used libraries, certificate rotation instructions, 2 weeks post-delivery support. Our experience guarantees that the solution will be stable and maintainable.

Timeline and Cost

Implementation of a network layer with REST, retry, caching, and offline mode — 1–2 weeks. Adding GraphQL or WebSocket — another 1–2 weeks. gRPC — 2–3 weeks, including code generation. The cost is calculated individually after analyzing the API and offline behavior requirements. We will evaluate the project in 1 day — contact us for a consultation. Get a reliable API integration with guaranteed quality.