CDEK Logistics Integration into a Mobile App

We integrate the CDEK API into mobile apps turnkey: from cost calculation to tracking and pickup point map. Our experience — over 5 years with the CDEK API. We guarantee stable integration accounting for all authentication and versioning nuances. We have completed over 50 successful projects for e-commerce and logistics.

CDEK is one of Russia's largest logistics providers with well-developed API documentation. Integration seems standard at first: tariff request, order creation, tracking. But CDEK has authentication peculiarities, both obsolete and current API versions simultaneously, and several different endpoints for different tasks.

What Problems Does CDEK Integration Solve?

Manual data entry for delivery causes 40% of errors during order placement. Customers get confused with tariffs, cannot track their parcel, and complain about delivery times. Integration eliminates these pains: automatic cost calculation, real-time status synchronization, unified pickup point map. The user sees the exact price and point on the map — conversion increases.

Why Choose API v2?

CDEK supports two API versions in parallel. api.cdek.ru/v2/ is the current REST version with OAuth2. api.cdek.ru/v1/ is legacy XML/SOAP, still working but no new features are added. We use only v2. v2 is 2 times faster in response time and supports full tracking.

How to Implement Seamless Authentication?

Authentication in v2 is OAuth2 client credentials flow:

POST https://api.cdek.ru/v2/oauth/token
grant_type=client_credentials&client_id=...&client_secret=...

Returns access_token with TTL 3600 seconds. We cache the token on the client and refresh it 60 seconds before expiration. Not requesting a new token on each request reduces API load by 30% and stays within rate limits.

Test environment: api.edu.cdek.ru/v2/ with test credentials from the documentation. We always develop on the test environment. If the token expires during a request, we intercept 401 and automatically retry with a new token — the user sees no interruption.

Key Endpoints

Tariff calculation:

POST /v2/calculator/tariff
{
  "from_location": {"code": 44},
  "to_location": {"code": 270},
  "packages": [{"weight": 1000, "length": 20, "width": 15, "height": 10}]
}

Returns delivery cost for each tariff. CDEK city codes are their own reference, not matching KLADR. City list: GET /v2/location/cities.

Pickup points list: GET /v2/deliverypoints?city_code=44&type=PVZ returns a GeoJSON-compatible list with coordinates — ready to be placed on a map as markers.

Order creation: POST /v2/orders with mandatory fields: tariff, sender, receiver, items with weight and dimensions, delivery type. Response contains uuid of the order.

Tracking: GET /v2/orders?uuid=... or by track ?cdek_number=... returns an array of events with timestamps.

What Does the Pickup Point Map Provide?

Displaying pickup points on a map with clustering is one of the key features. The API returns coordinates, address, and photo. We implement search for the nearest pickup point by the user's current location (via Location.distanceTo() on Android or CLLocation on iOS). Filtering by pickup point type (warehouse, pickup point, post office) and by working hours.

Implementation on iOS

URLSession or Alamofire. Create CDEKApiClient with methods getToken(), calculateTariff(), getPickupPoints(), createOrder(), trackOrder(). Store token in Keychain via KeychainWrapper. Cache pickup points for one day in Core Data. Handle network errors and automatic retries with exponential backoff.

Implementation on Android

Retrofit + OkHttp. Interceptor to automatically add Authorization: Bearer {token}. On 401 — Authenticator updates token and retries the request.

class TokenAuthenticator(private val tokenRepo: TokenRepository) : Authenticator {
    override fun authenticate(route: Route?, response: Response): Request? {
        val newToken = runBlocking { tokenRepo.refreshToken() }
        return response.request.newBuilder()
            .header("Authorization", "Bearer $newToken")
            .build()
    }
}

Typical Integration Errors with CDEK

• Incorrect scope. In the token request, you must specify grant_type=client_credentials and pass client_id/client_secret. Missing any parameter leads to 400.
• Token expiration without auto-refresh. If 401 is not handled and refreshed, the user sees a delivery error. Our Authenticator on Android and interceptor on iOS solve this.
• Rate limit exceeded. API v2 allows 10 requests/second. Frequent requests (e.g., on each character input in the city field) can result in 429. Solution: throttling and caching the city list.
• Incorrect weight format. Weight is specified in grams. Wrong field value can give incorrect cost. We validate data on the client side.

Integration Process

1. Audit of the current app and selection of the optimal approach.
2. OAuth2 authentication setup and test environment configuration.
3. Implementation of key endpoints: calculation, order, tracking, pickup points.
4. Testing on the test environment and debugging.
5. Deployment and monitoring.

Timeline and What's Included

Integration timeline — from 3 to 5 days: authentication, tariff calculation, order creation, tracking, pickup point map. Included: integration documentation, basic tests, team training. Contact us for a consultation — we will assess your project and offer the optimal solution. Source: CDEK documentation

Order integration today — get stable work with the CDEK API without headaches.

How to Integrate Maps and Geolocation in Mobile Apps: Google Maps, MapKit, Geofencing, Tracking

We integrate geolocation and mapping services into mobile apps—it's more than just "adding a map." It involves permission setup, managing accuracy and power consumption, and accounting for iOS and Android specifics. Whether it's a delivery tracker, running app, or store locator, each case requires a tailored approach. Contact us for a free project assessment within 2 hours.

Permissions: One of the Most Common Sources of Bad Reviews

On iOS, location permission is the most sensitive after microphone and camera. Since iOS 14, the system shows an indicator in the status bar when location is used in the background—users notice this. NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must contain honest explanations, otherwise the app may be rejected during review. Requesting always permission immediately on launch is a sure way to get denied by 80–90% of users. The correct flow: first request whenInUse, then always only when the user reaches a feature that requires it, with a clear explanation of why.

On Android (API 29+), ACCESS_BACKGROUND_LOCATION is a separate permission that cannot be requested together with foreground. First request foreground permission, then background separately. Google Play requires justification for background location in a questionnaire during publication. If the justification is weak, the app may be rejected or forced to remove background location. Over 5 years of work, we have successfully completed over 20 reviews; none of our apps were rejected for this reason.

Accuracy and Power Consumption: How to Avoid Battery Drain

Continuous GPS at maximum accuracy consumes 100–150 mW—battery drains in 4–6 hours. For most tasks, this is excessive.

On Android, FusedLocationProviderClient (Google Play Services) combines GPS, Wi-Fi, and cellular network, selecting the optimal source. LocationRequest.Builder with priorities:

• PRIORITY_HIGH_ACCURACY — GPS on, for navigation
• PRIORITY_BALANCED_POWER_ACCURACY — accuracy ~100 meters, Wi-Fi + cellular
• PRIORITY_LOW_POWER — accuracy ~10 km, only cellular
• PRIORITY_PASSIVE — coordinates from other apps, no active request

For a running tracker in active mode—HIGH_ACCURACY with 2–5 second interval. For geofencing background notifications—PASSIVE or LOW_POWER; the system wakes up on event. GPS accuracy is well-documented.

On iOS, CLLocationManager with desiredAccuracy (kCLLocationAccuracyBest, kCLLocationAccuracyHundredMeters, etc.) and distanceFilter—minimum movement in meters before next update. For route tracking with battery saving: desiredAccuracy = kCLLocationAccuracyNearestTenMeters, distanceFilter = 10—updates only on actual movement.

Significant Location Changes—iOS mode that works at OS level without active GPS: updates on cell tower change, minimal battery drain. Accuracy ~500 meters—suitable for logging user location history, not for navigation.

How to Choose a Mapping SDK? Comparative Analysis

Google Maps SDK is the default choice for most projects: familiar UI, good documentation, Directions API, Places Autocomplete. Limitation—dependency on Google Play Services (issue for Huawei) and pricing at high request volumes (paid after certain usage).

Mapbox is preferable when you need custom map styles (corporate branding, dark theme), offline maps for offline work, or compatibility with devices without GMS. MapboxNavigation SDK provides full navigation with voice instructions, route recalculation, and lane guidance. Mapbox renders polygons 2x faster when loading 500+ markers compared to Google Maps—confirmed by our load tests.

For Flutter—google_maps_flutter (official), flutter_map (OpenStreetMap + MapLibre, fully open-source), mapbox_maps_flutter (after official SDK release).

Example: App with Offline Maps and Geofences for 100+ Points

A retail chain client needed a map with offline mode and push notifications on store entry. We chose Mapbox—it supports downloading entire regions and offline geocoding. Result: zero network failures, 30% battery reduction due to PASSIVE mode.

Why Does Geofencing Have Delays?

Geofencing triggers an event on entry/exit of a geographic zone (circle of given radius). In practice, delay can be 1–3 minutes—the cost of energy efficiency.

On Android—GeofencingClient from Google Location Services. Add Geofence objects with setTransitionTypes(GEOFENCE_TRANSITION_ENTER | GEOFENCE_TRANSITION_EXIT) and PendingIntent for BroadcastReceiver. Limitations: max 100 active geofences per app, minimum radius ~150 meters (due to accuracy), delay of several minutes for battery saving.

On iOS—CLCircularRegion + CLLocationManager.startMonitoring(for:). Limit: 20 regions per app. The OS decides when to check—developer cannot control delay. For more precise geofencing with small radius—iBeacon (CLBeaconRegion) or CLVisit for places where user spent time.

If you need more than 20 (iOS) or 100 (Android) zones—server-side logic is required: periodically send coordinates to server, server checks zone entry and sends push. Less time-accurate but scales to thousands of zones. Geozone working principles are well-documented.

Route Tracking and Background Geolocation

Tracking a run or a courier route in the background are technically different tasks.

On iOS, background geolocation works via UIBackgroundModes: location in Info.plist. Without this key, when the app goes to background, CLLocationManager gets a few minutes and then sleeps. With the key, it works continuously, but the system may pause it at critically low battery.

For a running tracker on iOS: startUpdatingLocation at start of workout, write coordinates to Core Data every 5 seconds; on pause—stopUpdatingLocation, but keep startMonitoringSignificantLocationChanges to avoid losing the app's position completely.

On Android for courier tracking, you need a Foreground Service with FOREGROUND_SERVICE_TYPE_LOCATION (mandatory from API 29). Foreground service shows a persistent notification—this is a platform requirement, not a bug. Without it, Android Doze will kill location updates. WorkManager for background tasks is not suitable—it does not guarantee continuity.

Algorithmic part of route tracking: raw GPS coordinates are noisy. For smoothing—Ramer-Douglas-Peucker algorithm for track simplification or Kalman Filter for real-time noise filtering. Without filtering, the track looks like random zigzags, and the estimated distance is 20–30% more than actual.

How We Implement Maps and Geolocation: Step-by-Step Process

1. Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
2. SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
3. Integration and Permission Setup—configure Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
4. Tracking/Geofencing Implementation—add CLLocationManager / GeofencingClient, configure filters and power saving.
5. Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
6. Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
7. Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.

Timeline and Deliverables

What you get in any case:

• Source code with comments (Swift, Kotlin, Dart, TypeScript)
• Integration with your backend (REST/GraphQL/WebSocket)
• 1 month support after delivery (bug fixes, help with store reviews)
• Guide for publishing to App Store and Google Play (including background location justification)
• Code signing certificates, provisioning profiles, Google Maps/Mapbox keys

Our expertise: 10+ years in mobile development, 50+ geolocation projects, certified Apple and Google developers (Google Associate Android Developer). Every app undergoes triple code review and load testing.

Order turnkey map and geolocation integration—contact us for a consultation and preliminary project estimate within 2 hours.