May 2023 Summaries

The Vonage Video API has introduced a new feature called Secure Callbacks, which is currently available in public beta and will be made generally available in June 2023. This feature provides an additional layer of security to protect against unauthorized callbacks and ensures compliance with specific industries' requirements. Developers can enable this feature by toggling the Secured Callback slider button on in their project settings, and then configure the callback URL and signature secret to verify the authenticity and payload integrity of incoming requests. Secure Callbacks includes a JWT in the Authorization header, which corresponds to the user-configured signature secret, and also allows developers to verify the request payload has not been tampered with during transit by comparing an SHA-256 hash of the payload to the `payload_hash` field found in the JWT claims.

CallKit is used to handle VoIP push notifications sent to an iOS device when using the Vonage Client SDK for iOS, allowing integration of the app into the system so that it can look like a native iOS phone call. The process involves setting up push certificates, adding push notification capability, generating a push certificate, uploading the certificate to Vonage's API dashboard, and registering a device for push notifications. Once registered, the client SDK handles incoming push notifications by implementing the CXProviderDelegate protocol. The ClientManager class is used to interface with the Client SDK and handle user actions on the CallKit UI.

This summary provides a concise overview of how to use Vonage's In-App Messaging API for notifications in a web application, specifically in the context of MongoDB Atlas. The API allows developers to send textual messages from one client device to another, and is part of a comprehensive set of API call conversations that include In-App Voice. The Web Client SDK for In-App Messaging can be used with modern web browsers, iOS, Android, and other platforms. To use the API, developers need to authenticate through their application using a JWT token generated by the Vonage Application, which is signed with a private key. Once authenticated, the developer can send notifications to logged-in admin users, who will receive a pop-up notification with a link to a meeting that has been requested. The API also includes methods for adding events to conversations and handling incoming messages. The example code demonstrates how to generate a JWT token, connect to the Vonage Application, and push an event into a conversation using the Conversations API.

With the release of Verify V2's General Availability, Silent Authentication is a channel in the Verify API that enables authentication without a 2FA code by using a mobile phone's Subscriber Identity Module (SIM) to prove a user's identity. To use Silent Authentication, an application must be running on a phone over a mobile network and have a cellular connection established. The Vonage SDKs provide tools for iOS and Android developers to integrate silent auth into their applications. A Silent Authentication Sandbox allows testing of successful verification without the need for a mobile network connection. When using the sandbox, a response containing a request ID and check URL is sent, which must be followed with a GET request to complete the verification process. If Silent Authentication fails due to various reasons such as lack of cellular coverage or Wi-Fi connection, fallback options like SMS can be configured in the workflow. The guide provides detailed information on implementing Silent Authentication and using the sandbox for testing purposes.

Verify, Two-Factor Authentication (2FA) API, has released Version 2 for General Availability, offering improved developer experience with Webhooks for asynchronous integrations and more options and flexibility. The new version introduces strengthened fraud protection, enhanced delivery methods, workflow control, custom PIN generation, and better use of HTTP response codes. This evolution aims to work better for developers, enabling them to integrate 2FA into their systems more effectively, and encourages users to share their projects built with the new API.

The text discusses Laravel, a popular PHP framework, and its integration with Vonage's cloud communication APIs to build various applications such as messaging systems, ticketing systems, payment confirmation systems, online classrooms, and chatbots. It highlights the benefits of using Laravel and Vonage together, including improved developer experience, ease of use, and versatility. The text also covers various tutorials and guides on how to integrate Vonage's APIs with Laravel, making it easier for developers to get started with building communication applications. Additionally, it mentions the importance of performance-driven development in PHP and provides resources for optimizing website speed and reducing server costs.

In this series, MongoDB Atlas is used to authenticate users and provide query access for an application built using various Vonage APIs. The administrative backend uses Atlas's user authentication system, which allows for secure management of users and multiple types of authentication. The system is configured through the Atlas web UI, where users can manage roles, permissions, and data access controls. A VueJS code example demonstrates how to use the MongoDB SDK to authenticate users and access the database directly from the front end. The application uses a Database Store to hold a connection to the MongoDB cluster and uses the logged-in user's credentials to perform data lookups. The Atlas App configuration includes rules-based data access controls, which can be used to restrict what documents are returned based on the authenticated user's role or permissions. This setup allows for a secure and efficient way to manage user authentication and query access in an application built with MongoDB Atlas and Vonage APIs.

Two-factor authentication (2FA) is an important security feature that adds an extra layer of protection to user accounts by requiring a second form of verification, in addition to a password or other identifying information. By using the Vonage Verify API, developers can easily integrate 2FA into their Laravel applications, providing users with an additional layer of security and peace of mind. The benefits of 2FA include reduced risk of account takeover, improved trust and confidence among users, and reduced fraudulent activity. By implementing 2FA in a user-friendly manner, developers can help protect their users' sensitive information and maintain the integrity of their applications. Additionally, 2FA provides flexibility for users to choose the channels they prefer to receive verification codes, and it allows developers to implement features such as friendly forwarding, re-verifying 2FA periodically, and providing backup options for users in emergency situations.

Vonage offers a variety of APIs for customer interactions, including the Messages API, which allows developers to send SMS messages through multiple channels such as SMS, MMS, WhatsApp, Facebook Messenger, and Viber. The Messages API is designed for more general usage and focuses on ease-of-use, while the SMS API is purpose-built for advanced SMS interactions like SMPP protocol. Vonage's Meetings API provides a quick way to set up a one-to-one video chat without building a video application, allowing developers to send a link to the customer and drop them into a pre-built interface with minimal code. The API uses WebRTC standard to work on almost any device. Vonage also offers user authentication capabilities through its server SDK package, which allows developers to offload their user authentication to Atlas for administrative backend. With these APIs, developers can easily add SMS and video conferencing capabilities to their applications with a single line of code, making it easy to enhance customer interactions and provide a better experience for customers.

The key to building a high-performance contact center with Vonage APIs is understanding how to optimize response times for webhooks and ensure proper call and conversation UUID association. A fast response time for webhooks, particularly those handling NCCO actions like "answer" and "connect," is crucial in providing the best customer experience. Additionally, correctly associating call UUIDs and conversation UUIDs in event webhooks is vital for implementing features like Queue, Transfer, and Record. Implementing error-catching and logging mechanisms can also help in debugging and identifying performance issues.

The text discusses the integration of MongoDB Atlas with Vonage APIs for authentication purposes, specifically using Vonage Verify for two-factor authentication. The author sets up a demo application to demonstrate how to use MongoDB Atlas and Vonage Verify together. They create a database with a collection to store user data, and then wire up the demo by adding configuration details and running the application. The author explains how the application uses JWT tokens to authenticate users and how the Vonage Verify API is used to send codes to users' mobile devices for verification. The text also discusses the flexibility of MongoDB's document-based storage and how it allows for minimal impact on the codebase.

The Vonage Client SDK has undergone a major version update with new features and fixes, now utilizing Kotlin Multiplatform for shared core functionality between native Android and iOS SDKs. To start using the SDK, developers must add the new package name to their app's build.gradle file or Podfile, and familiarize themselves with key concepts such as sessions, invites, calls, and legs. The SDK provides functions like createSession and serverCall to establish connections and make calls, while also offering push notifications as a default way to receive incoming calls. Developers can learn more about the SDK on developer.vonage.com, including a step-by-step tutorial on making outbound calls.