Q1 2026: Vonage Developer Recap

The first quarter of 2026 has been focused on turning powerful ideas into production-ready capabilities. Over the past few months, we’ve moved several key technologies from beta into general availability. We’ve also improved the Vonage platform so that it is easier to observe, test, and integrate.

This quarter introduced:

• major progress in identity verification and fraud prevention

• deeper observability for video applications

• a smoother developer experience for exploring APIs and tooling

Whether you’re already building with Vonage or planning your next integration, here are our highlights from Q1.

Postman and Developer Workflow Improvements

In addition to platform features, Q1 also brought several improvements to developer workflows. We’ve made it easier than ever to explore and test our APIs.

A Fully Revamped Vonage Postman Collection

The public Vonage Postman Collection has been fully redesigned to make it easier for developers to discover and interact with Vonage APIs.

The updated collection organizes requests by capability and includes improved documentation directly within each request. Developers can quickly configure credentials, explore endpoints, and run example calls to better understand how each API behaves. 

The collection is also now maintained as a verified publisher workspace, ensuring it stays aligned with the latest platform capabilities.

Vonage MCP Servers Now Available on Postman

Developers can now access the Vonage Documentation MCP Server and Tooling MCP Server directly through Postman.

These Model Context Protocol (MCP) servers provide programmatic access to documentation, SDK information, and platform tooling. Developers can query documentation, retrieve SDK guidance, or interact with account tools such as balance checks or messaging endpoints.

This integration opens the door to more automated and AI-assisted developer workflows, helping teams build and troubleshoot integrations more efficiently.

Stronger Identity and Verification Flows

Identity verification continues to evolve quickly, and this quarter brought several important upgrades across the Vonage identity stack. With two APIs entering GA and new fraud-detection capabilities, developers now have more tools to build secure onboarding and authentication workflows.

Identity Insights API Now Generally Available

The Identity Insights API is now generally available, providing production-ready phone number intelligence for identity verification, fraud detection, and customer data enrichment. Following a successful beta period, the API now delivers improved latency, stronger error handling, and expanded documentation, along with official SDK support.

Developers can use Identity Insights to retrieve signals like number-format validation, SIM swap status, and carrier information. These insights help strengthen onboarding flows, detect suspicious activity, and enrich customer data with real-time network intelligence.

Silent Authentication in Verify API Reaches General Availability

Silent Authentication in the Verify API is also now generally available, enabling user verification without requiring annoying manual OTPs. Instead of asking users to enter a code, the system verifies the phone number by analyzing carrier traffic in the background.

For developers, this means authentication flows that are faster and more seamless for users while maintaining strong security. Silent Authentication is particularly useful for mobile applications where minimizing friction during sign-in or onboarding can significantly improve conversion rates.

Improvements to Silent Authentication Workflows

Alongside its GA release, Silent Authentication also received several important updates designed to improve operational control and testing.

A new coverage_check parameter allows developers to determine whether network validation should occur synchronously or asynchronously. Network registration is also becoming mandatory for production traffic, helping ensure more reliable carrier integrations. Also, the legacy sandbox parameter is being retired in favor of the Network Registry Playground, which provides a more realistic environment for testing network APIs.

Together, these changes give developers clearer visibility into supported networks and more predictable authentication workflows.

Subscriber Match Arrives in Beta

The Subscriber Match insight is now available in beta as part of the Identity Insights API. This capability allows businesses to compare user-provided information, such as name, address, or birthdate, with records held by the user’s mobile network operator.

By validating identity attributes against operator-verified data, Subscriber Match adds a powerful new signal for fraud prevention and identity verification. Developers can combine it with other insights, such as SIM swap detection or location verification, to build stronger trust models for onboarding and high-value transactions.

Silent Auth SDKs Being Retired from GitHub

As part of efforts to simplify the SDK ecosystem, the legacy Silent Auth Android and iOS SDK repositories will be archived from the Vonage GitHub organization.

The functionality previously provided by these SDKs is now available through the fully supported Vonage client libraries. Developers using the deprecated repositories should migrate to the newer client libraries, which consolidate mobile network capabilities into a single, actively maintained SDK.

This change helps streamline the developer experience and reduces fragmentation across authentication integrations.

Video Platform Improvements

Video developers also saw several important platform improvements this quarter, particularly around observability and performance control.

Video API 2.33: Observability and Platform Updates

Version 2.33 of the Vonage Video API introduces major improvements to client observability and video quality management. Developers now have access to richer performance metrics that reveal how network conditions, device constraints, and encoding layers affect real-time video quality.

The release also introduces dynamic video controls for adjusting resolution and frame rate, enabling applications to better adapt to bandwidth changes. Additional updates include support for Apple Silicon Macs through the iOS SDK and compatibility with Debian 13 environments.

These improvements make it easier to diagnose performance issues and build adaptive video experiences that respond to real-world network conditions.

Vonage Video API Native Reference Apps 1.0 GA

The Vonage Video API Native Reference Apps are now generally available, giving developers production-quality examples of how to build video applications across supported platforms.

These reference applications demonstrate common patterns such as session management, publishing and subscribing to streams, and handling connection events. For teams getting started with video development—or evaluating best practices—they provide a clear, working blueprint for building real-time communication features.

WEB VERA 1.4.0 Release

The latest WEB VERA 1.4.0 release introduces a set of improvements to the Vonage Video Reference Application for React, making it easier to build and test WebRTC-based video experiences.

One of the most notable additions is pre-call network testing, which allows users to validate connection quality, bandwidth, and device readiness before joining a session. Combined with a redesigned interface, Push-to-Talk controls, and participant list filtering, these updates help developers deliver more reliable and user-friendly video applications—especially in larger or more dynamic meeting environments.

In addition, updates to the underlying architecture and stability improvements in version 1.4.1 provide a stronger foundation for building and customizing production-ready video applications.

Looking Ahead

The momentum from Q1 shows no signs of slowing down. With stronger identity signals, better observability for video applications, and improved developer tooling, the Vonage platform continues to evolve to support modern communication workflows.