November 2026 Summaries

7 posts from Vonage

Filter
Month: Year:
Post Summaries Back to Blog
No summary generated yet.
Nov 16, 2026 1,268 words in the original blog post.
Vonage’s Email API is now generally available as a channel in the Messages API, allowing developers to send email alongside SMS, WhatsApp, Viber, and other channels using the same authentication and webhook infrastructure. Setup requires authenticating a sending domain through DNS and creating a Vonage application with a securely stored private key; the Node.js SDK can then send plain-text, HTML, or combined-format messages. Webhooks report statuses such as delivered, rejected, and undeliverable, and the Vonage CLI can simplify local webhook testing with an ngrok tunnel. The email channel supports uses including marketing campaigns, order and delivery notifications, account verification, password resets, and fallback delivery when another channel fails. Planned additions include dynamic templates, contact management, advanced analytics, campaign tools, and marketing automation.
Nov 13, 2026 1,706 words in the original blog post.
Vonage has added six startups to its Startup Program, highlighting companies that use its communications APIs to build AI-enabled services across recruitment, customer operations, collectibles, small-business management, healthcare, and telephony. Brazil-based Kolab supports large-scale hiring through WhatsApp recruiting and AI interviews, while Tunk.ai deploys no-code AI voice agents for customer calls and AgentGrail lets collectors receive AI trading-card evaluations by text message. DavidAI enables East African businesses to manage sales, inventory, and payments through multilingual WhatsApp, voice, and SMS interactions, and Medigize combines virtual consultations, identity verification, and patient navigation for healthcare users in Africa and the Middle East. Kollie AI uses voice automation for inbound, outbound, and emergency calls in the Netherlands, Belgium, and Germany. Vonage positions its program as offering startups API access, dedicated support, and a founder community for communications-powered products.
Nov 12, 2026 1,082 words in the original blog post.
Vonage has released version 1.4.0 of its Video Reference App (VERA) for iOS and Android, providing production-oriented examples for applications built with the Vonage Video API. Both platforms gain a shared authentication foundation with Okta support and expanded configuration and theming tools, while Android adds runtime-configurable meeting-room controls, picture-in-picture settings, layouts, speaker-test content, and default audio and video states. A new schema-driven terminal interface supports editing and validating app and theme configurations. On iOS, the release refactors calls to support potential future multi-session use, adopts Swift’s @Observable framework to reduce unnecessary UI rendering, and raises the minimum supported operating system version from iOS 16 to iOS 17. The update also includes bug fixes, with source code and detailed release notes available through the relevant GitHub repositories and Vonage Developer Portal.
Nov 11, 2026 630 words in the original blog post.
James Seconde explores three less widely known PHP frameworks—TempestPHP, Phalcon, and LeafPHP—by building a basic RCS messaging form with the Vonage PHP SDK in each one. TempestPHP is presented as a modern, flexible framework built from scratch around PHP features such as attributes, property hooks, discovery, and dependency injection, though it remains early in maturity. Phalcon takes a distinct performance-oriented approach as a C extension, offering low memory use and high speed but requiring more manual installation, bootstrapping, and operational setup. LeafPHP provides a lightweight, modular framework with an AI-first development focus, familiar features such as service containers and Blade templates, and tooling intended to support rapid prototyping. The comparison concludes that Tempest may suit custom SaaS dashboards, Phalcon high-throughput APIs or microservices, and LeafPHP MVPs or hackathon projects, while emphasizing that established frameworks such as Laravel and Symfony remain strong choices depending on project requirements.
Nov 10, 2026 4,357 words in the original blog post.
Login two-factor authentication requires an additional factor before creating an authenticated session, primarily protecting accounts against stolen passwords, while step-up authentication requests fresh verification only before high-risk actions such as fund transfers, API key rotation, or recovery-code access, helping limit misuse of an already valid session. The appropriate approach depends on whether most application activity is sensitive or only a small subset of operations carries elevated risk, and both methods can be combined to protect both account access and critical in-session actions. Step-up verification should be time-limited or single-use rather than stored as a permanent session Boolean, with the duration tailored to the action’s risk. Using the Vonage Verify API, applications should initiate and manage verification requests on the backend, store request identifiers in server-controlled state bound to the user, session, and where relevant the transaction, and never accept those identifiers from clients. SMS one-time passwords can support either pattern, while Silent Authentication may reduce friction by verifying phone-number possession through the mobile network and falling back to SMS when needed; production implementations should also address rate limits, CSRF protection, safe redirects, and session security.
Nov 05, 2026 2,339 words in the original blog post.
Vonage’s tutorial explains how to create QR-code-based smart links that open branded RCS Business Messaging conversations and automatically fall back to SMS when RCS is unavailable. It describes RCS as a richer successor to SMS, supporting verified business identities, logos, media, suggested replies, read receipts, and interactive features through the Vonage Messages API, while RBM adds the verified sender layer intended to reduce anonymous or fraudulent messaging. Using PHP 8.4, Symfony Console, the chillerlan/php-qrcode library, and Vonage’s Channel Manager API, developers build a command-line tool that requests a deep link with an RCS sender agent, country, prefilled message, and fallback phone number, then generate a QR image from that link through a simple PHP endpoint. The approach is positioned for event and trade-show use cases, where tailored QR codes can start branded conversations without directing visitors to forms, and associated webhooks and dashboard logs can measure scans, responses, drop-offs, read receipts, and SMS fallback rates. The tutorial also notes prerequisites such as an activated RBM agent, enabled Channel Manager access, and a registered fallback number, and highlights that RCS capability varies by device, carrier, territory, and settings, with iPhone support available through iOS 18.
Nov 03, 2026 3,039 words in the original blog post.