Integrating Russian Post API into Mobile Apps: Expert Guide

A user enters an address in your app — the system returns 400 Bad Request. Russian Post rejects the request due to invalid data format. The Russian Post REST API seems simple, but developers face pitfalls: double Basic authorization, SOAP protocol for tracking instead of REST, mandatory address normalization via FIAS or Dadata. Let's break it down. For example, when calculating tariffs, weight must be in grams and response cost in kopecks. One mistake in units — and the price in the app differs by 100 times. In this article, we share real solutions: how to set up authorization without 401 errors, why tracking is better proxied through a backend, and how to normalize addresses via Dadata. We compare performance of direct SOAP calls and JSON proxy.

We are a mobile development team with 5 years of experience integrating transport APIs (Russian Post, CDEK, Boxberry). We've mastered each service's nuances and completed over 30 integrations. Our engineers adapt integration to any architecture — SwiftUI, Jetpack Compose, Flutter. Order a turnkey integration — from documentation analysis to store publication. Let's evaluate your project for free.

How to Properly Set Up Authorization?

1. Obtain login and password from your Russian Post personal account.
2. Form the Basic header: Authorization: Basic base64(login:password).
3. Get an API token for the specified contract in the "Integration" section.
4. Add a second header: X-User-Authorization: Basic base64(token).
5. Test the tariff method (POST /1.0/tariff).

Authorization via Basic Auth with two headers is the first pitfall. The token from the personal account is not the user password. We guarantee that after debugging you won't see a 401. In our practice, a client struggled with authorization for a month — we resolved it in one call.

Why Does Tracking Require a Backend Proxy?

Tracking is the most requested feature. Request to get statuses:

POST https://tracking.russianpost.ru/rtm34?wsdl

Tracking API works via SOAP, not REST. For mobile apps, we wrap it in a backend proxy — parsing SOAP on the device is cumbersome; it's easier to return clean JSON to the client. Direct SOAP calls from a mobile app are a bad idea: each status update requires parsing XML with 20+ operations. A proxy server on Node.js or Firebase Functions processes this data 3-5 times faster on a mobile device. The list of operations for one shipment can contain 20+ entries. On the screen, we show the latest status and a brief history. Decoding operation codes is in a separate directory on the developer portal. More about the protocol: SOAP.

Why Does the API Require Address Normalization?

The Russian Post API does not accept arbitrary strings. It requires an index from the official directory or FIAS. We integrate Dadata for normalization: the user enters part of the address, and suggestions return a structured response with the index and FIAS code. This reduces errors by 80% compared to manual input. According to official Russian Post documentation, the address must contain a valid postal index — otherwise, the request is rejected with error 400.

Integration Scenarios Comparison

Typical Errors and Their Solutions

How to Update Statuses in the Background?

We update tracking not on user request but in the background: on iOS — BGAppRefreshTask, on Android — WorkManager with PeriodicWorkRequest interval of at least 15 minutes. When status changes, send a local push notification. Cache the list of track numbers and last statuses — the user sees data even without internet. This is especially important for marketplaces where the courier may be in a poor coverage area.

Label Generation

If the app is used for sending parcels (e-commerce, marketplace), a full cycle is needed: order creation → batch formation → label request (PDF, format F7 or F7p). Labels can be printed on a thermal printer via Bluetooth — on iOS use UIPrintInteractionController, on Android PrintManager. Integration with Zebra or Honeywell printers via their SDK adds another 2-3 days to the timeline.

What's Included in the Work

• Integration documentation (proxy scheme, endpoint descriptions)
• Configured access to Russian Post test and production environments
• Source code module in Swift/Kotlin/Dart with comments
• Unit and integration tests for key scenarios
• Team training (2 hours online)
• 2 weeks of post-release support

Our Experience

We are a mobile development studio with 5 years of experience. We have completed 30+ integrations with delivery services (Russian Post, CDEK, Boxberry). We hold an App Development with Swift certification and Google Play Console authorization. Every project undergoes code review and load testing. Get a consultation — tell us about your app, and we'll propose the optimal integration architecture.

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.