https://a.storyblok.com/f/270183/1368x665/05b03d1587/26jan_dev-blog_quarterly-release-q425.jpg

Vonage Q4 2025 Recap: Highlights and Insights

最終更新日 January 6, 2026

所要時間:7 分

In the last quarter of 2025, we focused on strengthening the core capabilities developers depend on when building with Vonage. Most of the work centered on security, identity, workflow efficiency, analytics, and real-time media, areas where small improvements have an outsized impact on day-to-day development.

You’ll see this in several updates, including unified U.S. network-level identity signals, deeper MCP integrations that support modern AI-driven workflows, a consolidated reporting interface through the Reports API, and a round of feature and stability improvements across the Video API ecosystem. We also introduced a dedicated LinkedIn page for developers.

The sections below walk through what we shipped this quarter and how these changes help you build more secure, reliable, and flexible communication experiences.

Network-Level Identity and Security

We strengthened our identity and security capabilities to give developers more reliable, network-verified signals they can use to protect users and reduce friction in authentication flows. These improvements make it easier to build secure, high-trust experiences while relying less on vulnerable, app-level checks.

Aggregated Network APIs in the U.S.

We launched our first aggregated Network APIs in the U.S., giving developers unified access to carrier-verified data from Verizon, AT&T, and T-Mobile. Rather than integrating separately with each mobile operator, you can now use a single integration to tap directly into network-level identity and security capabilities. This includes Silent Authentication via the Verify API and SIM Swap fraud detection via the Identity Insights API, both powered by open standards like CAMARA. With this release, we handle the complexity of carrier compliance and protocol fragmentation so you can focus on building. This makes it easier to create network-aware apps that identify risks, verify users, or optimize connectivity in real time.

Empowering Developers with Better Access and Control

In Q4 2025, we focused on giving developers both better access to information and new ways to take action. First, the Documentation MCP Server lets developers pull up-to-date docs directly in their IDEs or AI assistants. Building on that, the MCP Tooling Server enables AI-driven tools to perform real operations, from sending SMS to managing WhatsApp flows, all within the developer workflow.

Access Vonage Documentation from Your Tool

We introduced the Vonage Documentation MCP Server, which connects tools like VS Code, Cursor, or LLM-based assistants to our Developer Portal, letting developers query docs in real time. Setup is quick: just point the MCP extension to the server endpoint, or add it to your AI assistant configuration. This integration ensures reliable, official documentation is always at your fingertips.

Automating Operations with the MCP Tooling Server

To build on this, we launched the MCP Tooling Server, which expands how developers can automate actions across the Vonage platform using AI-driven tools. This open-source, MCP-compliant server enables agents such as Claude, Cursor, VS Code Copilot, and other MCP-enabled environments to perform real operations, like sending SMS, placing outbound voice messages, managing numbers, or handling WhatsApp and RCS flows, directly from within the development workflow. Instead of simply generating code samples, AI assistants can now execute tasks end-to-end, making it easier to prototype, run tests, or automate internal processes with minimal scaffolding.

The Tooling Server complements the Documentation MCP Server by moving from information retrieval to real operational capability, marking an important step toward more AI-native, agent-driven developer experiences.

Unified Reporting and Analytics

We also enhanced developers’ ability to access and analyze communications data. These updates provide more powerful insights and simplify reporting across Vonage products.

A Single API for Cross-Product Reporting

We launched the new Reports API, which provides a single endpoint to retrieve usage, delivery, billing, and event data across SMS, Voice, Video, and Verify, consolidating workflows that previously required multiple services. With support for both synchronous and asynchronous queries, as well as filtering by date, event ID, phone number, or sub-account, the API enables developers to build dashboards, monitor usage, track delivery outcomes, and manage sub-accounts more efficiently.

Unified Video Analytics Through the Reports API

We extended the Reports API to include Video API data, allowing usage, billing, and session information to be retrieved alongside other products through the same reporting interface. This simplifies centralized analytics and makes reporting more actionable. Currently, the Video reporting endpoint is REST-only and accessed via standard HTTP clients like cURL or Postman, with filters available for date ranges, accounts, and other parameters.

Video API Enhancements: More Control, Flexibility, and Reliability

We shipped updates across the Video ecosystem to improve developer experience, enhance flexibility, and strengthen platform stability. These include improvements to the React Video Reference App and enhancements to the core Video API SDKs.

New Features in the Video Reference App for React

We launched Version 1.3.0 of the Video Reference App for React, which introduces background effects (blur and custom images), a configuration file that enables or disables UI features without modifying code, and built-in localization with English, Spanish, and Italian support. Screen-sharing interactions were improved, allowing subscribers to scroll and zoom within shared content. The update also resolves several issues, such as ghost participants, incorrect camera LED behavior, and inconsistent mute icon display, resulting in a more reliable and flexible reference implementation.

More Reliable Real-Time Video with Video API v2.32.0

The new Video API Client SDK 2.32.0 brings significant enhancements to developer control and monitoring, empowering you with a more flexible video experience.

Developers can now configure preferred video codec priorities, tailoring sessions to application needs and device constraints. Downlink statistics provide real-time insight into subscriber bandwidth and stream quality, helping applications adjust resolutions or stream counts to maintain performance. Official WebViews support on Android and iOS allows embedding existing Video API JavaScript applications into native apps, maximizing code reuse. Together, these updates give developers greater flexibility and control in building and optimizing real-time video experiences.


Real-time AI Integration

The Video Engineering team has released four new Python-based tools in private beta to support real-time AI workflows (voice bots, video bots, transcriptions, translations, patient monitoring, etc.) into Vonage video sessions:

  1. Audio Connector SDK - An event-driven SDK that simplifies setting up a WebSocket server to send and receive audio through AudioConnector Websockets.

  2. Pipecat Serializer - Bridges the Vonage Video Session Audio Connector with Pipecat, a framework for building real-time AI workflows that process audio and video.

  3. Video Connector SDK - Exposes functions for a Python application to join Vonage Video sessions via WebRTC and send, receive, and process audio and video. Built on top of the Linux C++ SDK.  

  4. Pipecat Transport - Integrates Vonage Video Session WebRTC with Pipecat, enabling Pipecat workflows to send and receive both audio and video. 

For access to the private beta, please contact Michael Vernick, Customer Solutions Architect at Vonage (michael.vernick@vonage.com).

Platform Security and Reliability

We continued to strengthen the security and reliability of our platform so developers can safely and consistently connect to our APIs. These updates focus on modernizing encryption standards, improving compatibility across client environments, and supporting regional compliance requirements.

Improved Certificate Handling for API Clients

We expanded SSL/TLS support across all API domains by adding secure ECDSA certificates (P-256/P-384) alongside existing RSA-2048 certificates. Load balancers now automatically serve the best certificate based on each client’s capabilities. This upgrade aligns with modern cryptographic standards and enhances overall platform resilience. Most developers won’t need to take action, but older systems without ECDSA or SNI support may require validation using our dedicated test endpoint.

Developer Community and Connections

We launched the Vonage Developer LinkedIn page, a dedicated space for developers to connect with our team, explore products, and learn from community stories. It’s also a place to get behind-the-scenes insights from industry events and see what we’re building next. Following the page is the easiest way to stay up to date with updates, tutorials, and the initiatives we have planned for 2026.

Conclusion

The improvements delivered in Q4 2025 were shaped by developer feedback and a focus on reducing friction at every stage of the build process. From identity security and analytics to documentation access and real-time media, we’ve strengthened the tools you rely on daily. We’re excited to continue expanding these capabilities as we head into 2026.

Have a question or something to share? Join the conversation on the Vonage Community Slack, stay up to date with the Developer Newsletter, follow us on X (formerly Twitter), subscribe to our YouTube channel for video tutorials, and follow the Vonage Developer page on LinkedIn, a space for developers to learn and connect with the community. Stay connected, share your progress, and keep up with the latest developer news, tips, and events!


シェア:

https://a.storyblok.com/f/270183/400x400/c062dd93d5/daniela-facchinetti.png
Daniela FacchinettiDeveloper Relations Content Manager