DOCSEARCHbyAlgolia
Submit Docs

Vonage Developer Documentation

website·Indexed 51 days ago

https://developer.vonage.com/en/documentation

Developer guides and tutorials for integrating Vonage APIs, featuring implementation examples for Voice, SMS, and Video. Includes step-by-step tutorials for building Interactive Voice Response (IVR) menus, connecting to WebSockets, and receiving SMS messages using Node.js, .NET, Kotlin, and JavaScript.

Tokens
225.5K
Snippets
861
Records
1.6K
Agent score
70%

What's inside Vonage

  1. Overview of building a basic video chat with Vonage Video API

    The Vonage Video API allows developers to implement real-time communication features including video, voice, and messaging. To build a basic video chat application, developers need to utilize both the client-side SDK (for media handling and user interface) and the server-side SDK (typically for authentication and session management). Prerequisites for implementation include basic knowledge of client-side JavaScript, HTML, and general web application development.

  2. Overview of Vonage Network Features

    Vonage Network Features provide access to mobile operator capabilities beyond traditional SMS and Voice. Many of these features are based on CAMARA standards (a Linux Foundation initiative), ensuring a unified API solution that allows applications to work consistently across different operators and countries worldwide.

  3. Overview of Vonage SMS API

    Vonage's SMS API is a REST-based service that allows developers to programmatically send and receive text messages globally. Key capabilities include low-latency delivery, the ability to receive SMS using local numbers, and an auto-redact feature to protect user privacy.

  4. Overview of Vonage Silent Authentication in Laravel

    Vonage Silent Authentication removes the need for a One-Time Password (OTP) during two-factor authentication (2FA) by verifying the device's phone number and authenticity via network APIs. In a Laravel implementation, the system attempts Silent Authentication first; if the phone number is in an unsupported territory or on an unsupported network, it automatically defaults back to SMS authentication.

  5. Overview of Vonage Video API Reference Apps

    Vonage Video API Reference Apps are open-source, production-grade sample experiences used to validate meeting scenarios (such as lobbies, chat, reactions, screen sharing, and recordings) and benchmark architecture decisions before full implementation. They provide a ready-to-run UI, a thin backend/token strategy, and opinionated tooling. All reference apps use the same session/token strategy as production, allowing cross-platform participants in the same meeting.

  6. Overview of Vonage Cloud Runtime

    Vonage Cloud Runtime is a platform that eliminates the need for developers to host and maintain their own infrastructure when using Vonage APIs. It supports rapid production deployment via Code Hub or a CLI. Key features include:

    • Prebuilt templates for common use cases like IVRs, chatbots, and voice/messaging notifications.
    • Built-in queuing and scheduling to support high-volume deployments (thousands of requests per second).
    • Flexible deployment options via CLI or the platform's Code Hub.

  7. Overview of Vonage Silent Authentication

    Silent authentication allows for user verification via their mobile data connection without requiring user interaction, such as entering a code from an SMS or voice call. This method improves security and accelerates the onboarding experience. A common implementation pattern is to use silent authentication as the primary method with SMS as a fallback.

  8. Overview of Silent Authentication

    Silent Authentication verifies a user's identity by checking their phone number against carrier records using the mobile device's Subscriber Identity Module (SIM). This process happens in the background without requiring user input (no OTP codes), reducing friction and eliminating SMS phishing risks. Once verified, a user can remain authenticated until the request expires or is canceled.

  9. Overview of Vonage Identity Insights API

    The Vonage Identity Insights API provides real-time phone number intelligence sourced directly from mobile carrier infrastructure. Because the data is carrier-derived, it is passive, frictionless, and cannot be spoofed. It is used to assess risk for specific actions such as logins, onboarding, account recovery, and financial transactions to enable adaptive security.

  10. Overview of Vonage Video API Client SDK capabilities

    The Vonage Video Client SDKs provide the necessary tools to integrate real-time video and audio communication into applications. The core capabilities include connecting to a session, publishing media streams, and subscribing to other participants' streams.

  11. Overview of Vonage Voice API call models

    The Vonage Voice API manages voice calls using two complementary interaction models:

    1. Application-initiated: The developer triggers actions using REST API calls or SDKs.
    2. Vonage-initiated: Vonage requests instructions from the developer's application via webhooks and NCCO (Nexmo Call Control Object) JSON structures.

    Key capabilities include:

    • Controlling inbound and outbound call flows via JSON NCCOs.
    • Recording and storing call audio.
    • Creating conference calls.
    • Text-to-speech in 40 languages with various genders and accents.

  12. Overview of Vonage Voice API Webhooks

    The Vonage Voice API uses three types of webhook endpoints to enable application interaction during calls:

    • Answer webhook: Triggered when a call is answered (both incoming and outgoing).
    • Event webhook: Triggered for all status changes and events occurring during a call, including errors.
    • Fallback URL: Used as a backup when either the Answer or Event webhook fails or returns an HTTP error status.