Integrating Vonage (Nexmo) SDK for In-App Calls

We often encounter this situation: a client already uses Twilio but looks for an alternative with better coverage in Europe or more flexible terms. Or — an MVP needs voice calls but the budget doesn't allow Video API. Vonage (formerly Nexmo, after acquisition by Ericsson) is a direct competitor to Twilio, with its own nuances. Let's explore how we integrate the Vonage Client SDK and Video API, what pitfalls we've encountered, and what's important to consider.

Vonage provides several independent SDKs for mobile apps: Vonage Client SDK for in-app voice and messaging, Vonage Video API (ex-TokBox OpenTok) for video, and separate REST APIs for SMS/WhatsApp. It's important not to confuse these products — they have different billing, different SDKs, and different documentation. Choosing the wrong SDK is one of the most common problems at the start.

How to Set Up Push Notifications for Incoming Calls?

Without push, an incoming call won't arrive if the app is in the background. For iOS we use VoIP PushKit, for Android — FCM (Firebase Cloud Messaging). The setup requires:

1. Upload the APNs certificate (or key) in the Vonage Dashboard.
2. Specify the FCM key for Android.
3. In the SDK, enable the corresponding delivery channel during login.

// Android: enable push notifications
val config = VGClientConfig()
config.pushConfig = VGPushConfig.Builder(context)
    .setChannel(VGPushConfig.Channel.FCM)
    .build()

After that, incoming calls will arrive even in a killed state, and the system will display the native call UI (iOS — CallKit, Android — notification-based call).

Vonage Client SDK: Voice Calls

The Vonage Client SDK for voice is built on top of WebRTC, but provides a high-level API with JWT authentication and integration with the Vonage Voice API.

JWT generation on the backend is a key point. Vonage uses RSA-signed JWT, not HMAC. The private key is generated when creating a Vonage Application in the Dashboard — it's a .key file that must be stored on the server, not in the mobile app.

import jwt, time

payload = {
    "application_id": VONAGE_APP_ID,
    "iat": int(time.time()),
    "exp": int(time.time()) + 3600,
    "sub": user_id,
    "acl": {
        "paths": {
            "/*/users/**": {},
            "/*/conversations/**": {},
            "/*/legs/**": {}
        }
    }
}

token = jwt.encode(payload, private_key, algorithm="RS256")

Example initialization on Android:

// build.gradle
implementation 'com.vonage:client-sdk-android:8.x.x'

// Initialization
val client = VonageClient.Builder(context)
    .build()

client.setConnectionListener { connectionStatus, connectionStatusReason ->
    // CONNECTED, DISCONNECTED, etc.
}

// Login with JWT
client.login(jwt) { loginResult ->
    when (loginResult) {
        is LoginResult.Success -> { /* ready for calls */ }
        is LoginResult.Failure -> { /* handle error */ }
    }
}

Why Is Vonage Client SDK Harder Than Twilio?

The main practical drawback is documentation. client-sdk-android versions 7.x and 8.x have incompatible APIs, and the migration guide is incomplete. Several times we had to parse the SDK changelog to understand why callbacks stopped firing after a dependency update. Twilio does better here: examples are up-to-date, breaking changes are rare. However, Vonage wins on the cost of European numbers (up to 40% cheaper than Twilio for some routes) and the flexibility of Video API licensing.

Vonage Video API (OpenTok)

If the task is video calls or video conferences, the Vonage Video API (OpenTok) is a separate product with richer functionality: screen sharing, recording, broadcast, signaling via built-in channels.

// Android OpenTok SDK
implementation 'com.vonage:client-sdk-video:x.x.x'

val session = Session.Builder(context, API_KEY, sessionId).build()
session.setSessionListener(sessionListener)
session.connect(token)

val publisher = Publisher.Builder(context).build()
session.publish(publisher)

The session is created on the server via REST API; the client receives sessionId and token. The model is similar to Twilio Video, but OpenTok has been around longer, so it performs more stably on weak networks (up to 30% fewer dropped calls under 3G conditions).

Vonage SMS and WhatsApp Business

SMS via the Vonage REST API is the simplest scenario, no SDK needed:

POST https://rest.nexmo.com/sms/json
api_key=xxx&api_secret=yyy&from=Vonage&to=79001234567&text=Hello

WhatsApp Business via Vonage Messages API requires an approved template from Meta for the first outbound message; any user response opens a 24-hour window for free messaging.

Comparison with Twilio

Vonage wins in Europe for PSTN coverage but loses in documentation quality. According to our measurements, integrating the Client SDK on Android takes 20–30% longer than the equivalent on Twilio due to the need to decipher outdated examples.

What’s Included in the Work

We create and configure the Vonage Application, generate an RSA key pair, implement the backend for JWT, integrate the Client SDK or Video API on Android/iOS, set up push for incoming calls, and test on real devices. We have already completed over 15 Vonage integrations for clients from Europe and the CIS — all backed by 5+ years of experience with mobile SDKs.

Timeline: 1–3 weeks depending on required functionality (only calls or a full communication platform). Order Vonage SDK integration — we will assess your project and propose the optimal stack. Typical deliverables include:

• Backend JWT generation module (Python/Node/Java)
• SDK integration on Android and/or iOS with sample code
• Push notification configuration (APNs, FCM)
• End-to-end testing report with metrics (call setup time, drop rate)
• 1-month post-integration support and knowledge transfer

Source: Vonage Developer Documentation

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.