August 2025 Summaries

Vonage has announced the general availability of VP9 with Scalable Video Coding (SVC) for Routed Sessions in its Video API, offering enhanced video quality and efficiency for developers. VP9, an open-source codec developed by Google, improves compression and video quality at lower bandwidths compared to its predecessor, VP8. The introduction of SVC in VP9 provides additional versatility by allowing a single video stream to adapt to varying network conditions and device capabilities, thereby improving scalability and performance in large video calls. This update is particularly beneficial for users on constrained networks, ensuring smooth video experiences even in low-bandwidth situations, and is supported by major browsers like Chrome, Safari, and Edge. Developers can enable VP9 SVC through the Vonage Dashboard, seamlessly integrating it into existing systems without needing significant infrastructure changes, and are encouraged to explore further details through Vonage's documentation and community support channels.

The blog post discusses the use of API collections, created with tools like Postman, Bruno, or Insomnia, as effective onboarding artifacts for developers, emphasizing their role in promoting interactive learning and improving the developer experience. Unlike traditional API documentation like OpenAPI specs, which often lack narrative and context, API collections present organized, example-driven workflows that developers can experiment with in real-time, thereby reducing friction and accelerating productivity. These collections provide a structured environment for safe and repeatable testing, support cross-team communication by acting as living documentation, and build trust through transparency by showing exactly what is sent and received. The post further outlines steps to create and share API collections effectively, encouraging a product-thinking approach to API design that simplifies the learning curve for new developers and encourages seamless API adoption. Additionally, the article highlights the importance of integrating API collections into documentation and version control practices to foster an interactive learning environment where feedback is immediate.

The Identity Insights API, recently released in Beta by Vonage, offers developers the ability to enhance customer interactions through phone number intelligence, aiding in fraud prevention and personalized customer journeys. This API abstracts the complexities of data aggregation from hundreds of mobile operators and regulatory authorities worldwide, allowing brands to request various insights in a single API call. It supports use cases such as strengthening identity verification, validating phone numbers for reliable communication, and optimizing customer engagement by utilizing real-time intelligence on attributes like time zone and carrier. With plans for geographic expansion and new features, the API simplifies the integration process while ensuring compliance and data reliability.

The tutorial provides a comprehensive guide on sending Rich Communication Services (RCS) text messages using the Go programming language and the Vonage Messages API. It begins with setting up the necessary prerequisites, including a Vonage API account and a registered RCS Business Messaging agent, before guiding users through the process of initializing a Go project, installing dependencies, and configuring environment variables for authentication and API interaction. The tutorial details the implementation of the main function to construct and send an RCS message using HTTP requests, ensuring authentication via JWT tokens. It also explains how to create and configure a Vonage application with the required capabilities and webhooks, emphasizing the importance of securing the private key for API calls. The final section covers testing the application and encourages exploring advanced RCS features like suggested replies and rich media, while inviting developers to engage with the Vonage community for further support and innovation.

Kamila Banecka, a technical writer with a background in linguistics and IT, has joined the Vonage Developer Relations Team, bringing her expertise in making API and developer documentation clear and practical. Her journey from being frustrated by poor documentation as a test automation developer to becoming a dedicated documentation specialist was shaped by experiences at Intel, where she managed complex projects involving hardware and AI/ML tools. Her work involved creating detailed and accurate developer documentation that bridged the gap between engineers and developers, ensuring technical clarity and usability. At Vonage, she aims to leverage her experience to enhance documentation quality, while outside work, she enjoys relaxing with a Kindle and coffee at the beach.

The article provides a detailed tutorial on using the Vonage Video API to create a virtual green screen effect, allowing presenters to overlay themselves onto shared content during online presentations. It addresses challenges such as the lack of transparency support in WebRTC and video codecs, and explains how to use the API's Background Replacement feature with a small solid-color image to simulate transparency. The tutorial covers setting up the application environment, including prerequisites like JavaScript and HTML5 Canvas experience, and configuring a video application with the Vonage Video API key, Session ID, and Token. It describes the workflow for connecting the Vonage Video API session, sending and receiving media, and using the VideoRenderer class to process video frames, replacing backgrounds with a designated green screen effect. The tutorial concludes with instructions on running the sample application and offers potential enhancements such as video backgrounds for publishers and watch party applications, while encouraging engagement with the Vonage developer community for further support and updates.

Vonage has introduced a message failover feature in its Messages API, designed to enhance message delivery resilience by automatically sending fallback messages if the initial message is rejected. The Messages API supports multi-channel communication, allowing businesses to send and receive messages across various platforms such as SMS, MMS, RCS, and WhatsApp. The failover feature simplifies the process of implementing message resilience by enabling users to include a failover array in the JSON payload of a message request, which specifies alternative message objects to be sent automatically in case of rejection. This capability can be particularly useful when delivering messages across channels with varying device support and network coverage, such as transitioning from RCS to SMS if a device does not support RCS. The API provides tracking through unique message UUIDs and workflow IDs, allowing users to monitor the status progression of each message and its failover attempts. This innovation streamlines the development of robust messaging applications by integrating failover logic directly into the API request structure.

Vonage CodeConnect is offering a series of webinars focused on enhancing security in the banking and finance sector using Vonage Network APIs. These sessions aim to equip developers with the tools needed to improve fraud detection, secure user verification, and strengthen mobile banking systems. Key topics include detecting SIM swap fraud, building fraud-resistant mobile banking systems, and implementing advanced security measures such as multi-factor authentication (2FA) and real-time identity insights. The webinars provide practical examples and best practices for integrating Vonage APIs to create safer, seamless user experiences while protecting sensitive transactions. Participants are encouraged to join the live sessions for interactive learning and to explore upcoming webinars for further engagement in the Vonage developer community.

Rich Communication Services (RCS) represents the evolution of traditional SMS and MMS by introducing interactive, branded messaging experiences that align with shifting customer expectations for smart, conversational interactions. Businesses transitioning from SMS to RCS should adopt a value-led approach focused on achieving specific outcomes, such as increased engagement or reduced no-show rates, through outcome-focused Proof of Concepts (PoCs). This strategy allows businesses to validate the impact of RCS, measure success through metrics like conversion rates and cost-per-engagement, and align teams around shared objectives. For example, a UK retail chain's A/B test showed that RCS messages led to a 10x higher click-through rate than SMS, highlighting the potential for richer media and interactive features to drive engagement and revenue. Similarly, enhancements in last-mile logistics, cart recovery, security alert authenticity, and healthcare appointment management underscore RCS's capability to transform customer interactions into value-driven conversations. By gradually implementing RCS where it outperforms SMS and aligning with industry standards, businesses can leverage RCS as a robust tool for enhancing customer communications and achieving measurable outcomes.

The tutorial provides a comprehensive guide on using Vonage's Messages API to implement Rich Communication Services (RCS) with Suggested Replies in an ASP.NET Core Web API. It walks through setting up the development environment, including necessary tools like .NET 9.0 SDK, Visual Studio, and ngrok, and details the creation of a web API that can send and receive RCS messages using Vonage's .NET SDK. The tutorial covers configuring application settings, setting up secure webhooks, and testing the application using an RCS-enabled device. The guide further explains creating endpoints for sending RCS messages with suggested replies, handling inbound messages with webhook verification, and sending confirmation messages. Additionally, it emphasizes the importance of authentication and security, such as JWT validation, to ensure messages' authenticity. The tutorial concludes by suggesting further enhancements and engaging with the Vonage community for support and inspiration.

Vonage has introduced a new feature called Post-Call Text Insights, an enhancement to the Post-Call Transcription feature of its Video API, which provides AI-generated summaries of recorded video sessions to offer concise overviews of conversations. This feature is designed to streamline the review process for users in industries like telehealth, education, and recruiting by highlighting important points and enabling follow-up actions without scanning full transcripts. To utilize this feature, developers need to include a transcriptionProperties object with the hasSummary property set to true when initiating an archive session. The enhancement is now available for all Vonage Video API accounts, and the company encourages user feedback to guide further development.