Kraken API Integration for Mobile Crypto Apps

We've seen teams get stuck on the request signing phase: HMAC-SHA512 with double hashing scares even experienced developers. Kraken's algorithm is one of the strictest among public crypto exchanges. But in practice, integration on mobile platforms takes half a day if you know the nuances. With over 10 years of experience and 40+ completed exchange API integrations, our team ensures stable operation without lockouts.

Problems We Solve

HMAC-SHA512 is the core of the signature, but errors arise from incorrect private key decoding. The private key is a Base64 binary secret, not an ASCII string. On iOS, a typical mistake is passing Data(privateKey.utf8) instead of Data(base64Encoded: privateKey)!. On Android, forgetting to decode Base64 before using Mac.getInstance("HmacSHA512"). Result: signature formed, but server returns authentication error.

Non-standard asset names: The REST API uses XBT instead of BTC, XDG instead of DOGE. Pairs look like XBTZUSD. WebSocket v2 normalizes (BTC/USD), but REST and historical data do not. Without a mapping table, users won't recognize their assets. We implement an alias map from AssetPairs.

Rate limiting without hints: Kraken does not return headers with remaining limit. Exceeding it results in an IP block for several minutes. We implement adaptive intervals: balance every 10 seconds, orders every 30 seconds, all market data via WebSocket.

How Kraken Request Signing Works

1. Generate a nonce — Unix timestamp in milliseconds.
2. Compute SHA256 of nonce + postData (URL-encoded string).
3. Create HMAC-SHA512 of urlPath + the resulting hash, using the Base64-decoded private key.

Result — API-Sign. If nonce is not first in postData, Kraken returns EAPI:Invalid nonce. An incorrect signature can cost time and money: one mistaken order can lead to $100 loss. Our approach eliminates such errors. We use CryptoKit on iOS (available since iOS 13) and javax.crypto.Mac on Android. More details in the Kraken API documentation.

Why Kraken Asset Names Differ from Standard

Historically, Kraken used ISO codes with prefixes: X for base, Z for quote currency. XBT = Bitcoin, XDG = Dogecoin. Inside pairs, prefixes double: XXBTZUSD. WebSocket v2 switched to readable format (BTC/USD), but REST remained old. We build a table from AssetPairs and display convenient names while using originals in requests.

WebSocket API v2: Updates

With the transition to v2, the message format changed: from {"event":"subscribe"} to {"method":"subscribe","params":{...}}. Authorization for private channels: get a token via REST /0/private/GetWebSocketToken, pass it in params.token when subscribing to executions (orders) or balances. The token lives 15 minutes — a refresh mechanism is required. Without it, the session silently dies, and the user stops seeing order updates.

Example signing code in Swift:

import CryptoKit

func generateSignature(urlPath: String, body: Data, secret: String) -> String {
    let secretData = Data(base64Encoded: secret)!
    let nonce = "\(Date().timeIntervalSince1970 * 1000)"
    var postData = "nonce=\(nonce)"
    if let additionalData = String(data: body, encoding: .utf8) {
        postData += "&\(additionalData)"
    }
    let sha256 = SHA256.hash(data: postData.data(using: .utf8)!)
    let hmac = HMAC<SHA512>.authenticationCode(for: urlPath.data(using: .utf8)! + sha256.data, using: SymmetricKey(data: secretData))
    return hmac.compactMap { String(format: "%02x", $0) }.joined()
}

What's Included

• Analysis of your app's current architecture and selection of the appropriate stack (iOS: URLSession + Combine, Android: OkHttp + Coroutines).
• Implementation of signature and error handling (including WebSocket reconnection).
• Setup of push notifications (APNs/FCM) for order confirmations.
• Testing with real trading data simulating rate limits.
• Documentation — endpoint descriptions, request examples, operation instructions.
• Warranty — 30 days of free support after launch.

Want to avoid these issues? Order Kraken integration from us and get a free analysis of your app. We'll evaluate your project in one business day. Contact us for a consultation.

Stack and Timeline

For native iOS: CryptoKit (HMAC-SHA512), URLSessionWebSocketTask, Combine Publisher. For Android: Mac with HmacSHA512, OkHttp WebSocket, Kotlin Coroutines + Flow. Spot integration (no margin) — 3-4 weeks. Futures API — separate, with different authentication. If you want to estimate the timeline for your project, contact us.

We'll evaluate your project in one business day. Get a consultation on Kraken integration for your app — free of charge.

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.