verapli
Sign inJoin free
Menu

Guides · messaging · Verification-gated

Vonage Messages API

One API for SMS, MMS, RCS, WhatsApp, Messenger, Viber and email. New accounts start in demo mode with restricted destinations; adding credit lifts it. US SMS from long codes needs 10DLC brand and campaign registration.

Researched · not yet run liveLast researched 25 October 2026 · Vonage · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

A Vonage API account (API key + secret) holds Applications. Each Application has an Application ID and a private key, Messages capability and webhook URLs; numbers are linked to an Application. Subaccounts are available.

  • Vonage API account organisation owned by the person or the companyStarts in demo mode until credit is added.
  • Application project · under Vonage API accountNeeded for JWT auth, webhooks and linked numbers.
  • Subaccount projectoptional · under Vonage API account

Have ready

  • Email address and mobile phone for sign-up and test-number PINs
  • A card to add credit · Adding credit is what moves the account out of demo mode. [4]Needed for: Add credit
  • Your own mobile number · Test numbers are verified with a PIN by SMS or voice. [to verify] [6]Needed for: Create a Vonage API account
  • Public HTTPS endpoint for inbound and status webhooks · Webhook URLs are set on the Application; Basic auth does not support webhooks. [2]Needed for: Create an Application with Messages capability
  • US business details (legal name, EIN) if texting US numbers from a long code · 10DLC brand registration. [field list to verify] [5]Needed for: Register 10DLC brand and campaign (US only)

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Create a Vonage API account

    Sign up yourself on the Vonage developer site. The account starts in demo mode.

    • Guided by hand
    • Human step: You press submit
    If something goes wrong (1)
    • SMS fails with "Non White-listed Destination - rejected (29)": In demo mode you can only send to test numbers; add the number as a test number or add credit. [to verify] [6]

    Where: https://developer.vonage.com/

  2. Add credit

    Add credit with your card to leave demo mode and send to any number within local rules.

    • Guided by hand
    • Human step: You add payment details
    • After: Create a Vonage API account

  3. Copy API key and secret

    Open Settings > API settings in the dashboard (arrow next to your username) and capture the API key and secret into your vault.

    • Guided by hand
    • After: Create a Vonage API account

    verapli captures VONAGE_API_SECRET here by plain code: encrypted in your browser, never shown to AI.

  4. Create an Application with Messages capability

    Create an Application, switch on Messages, set inbound and status webhook URLs, and generate the key pair. The private key file downloads to your machine; keep it in your vault, never in the repo.

    • Guided by hand
    • Human step: You press submit
    • After: Create a Vonage API account

  5. Register 10DLC brand and campaign (US only)optional

    Register the brand, get it verified or vetted, register a campaign per use case, then link numbers.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Buy and link a number
    The provider says
    Manual reviews by Vonage, vetting providers and carriers; allow several days or even weeks. [5]

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

10DLC carries separate fees (brand registration €4.50, vetting and campaign charges), and fines can be applied for 10DLC violations. [7]

Worth knowingThe rules say

Demo-mode messages carry a demo notice and reach only a small set of test numbers. [4]

Worth knowingThe rules say

A Low Volume Mixed campaign is the only option for a brand without external vetting. [5]

What you end up with

Env varSecretFormatWhat it is
VONAGE_API_KEYnot secretVonage API key
VONAGE_API_SECRETsecretVonage API secret
VONAGE_APPLICATION_IDnot secretxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxApplication ID (UUID)
VONAGE_APPLICATION_PRIVATE_KEY_PATHnot secret./private.keyPath to the downloaded private.key for JWT signing (the key itself is secret)
VONAGE_NUMBERnot secret447700900000Linked sending number in E.164 without +

Renewals

  • Rotate the API secret (two secrets can be active during the switch): every as needed [3]

Pricing

  • Free tier: Small free trial credit (€2 per Vonage support) in demo mode [to verify].
  • Costs: Pay as you go from account credit; per-message rates by channel and country.

Source [6]

For agents

The same entry as JSON: /api/v1/entries/vonage/messages-api · requirements /api/v1/requirements/vonage/messages-api · terms /api/v1/terms/vonage/messages-api.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Vonage Messages API, and how long will it take?"
  → tools/call requirements { "provider_id": "vonage/messages-api" }

Sources

  1. Vonage docs – Messages API overview Channels (SMS, MMS, RCS, WhatsApp, Messenger, Viber, Email); JWT auth; Messages API Sandbox in dashboard; 10DLC APIs for brand, vetting, campaign and number linking · accessed 25 October 2026 · official
  2. Vonage docs – Messages API, before you begin Need a Vonage API account and Application; Application ID + private.key generate JWT; inbound and status webhook URLs set on the Application; env names VONAGE_API_KEY, VONAGE_API_SECRET, VONAGE_APPLICATION_ID, VONAGE_APPLICATION_PRIVATE_KEY_PATH, VONAGE_NUMBER · accessed 25 October 2026 · official
  3. Vonage docs – Authentication Messages supports Basic (key+secret) and JWT; Basic does not support webhooks or advanced features; private key generated from the application dashboard or vonage apps create; two API secrets can be active for rotation · accessed 25 October 2026 · official
  4. Vonage docs – Using the Vonage Dashboard for account management Demo mode sends to up to 10 destination numbers with a demo notice; API key and secret under Settings > API settings; adding credit moves the account out of demo mode · accessed 25 October 2026 · official
  5. Vonage docs – Brands and Campaigns (10DLC) US 10DLC SMS/MMS requires registration; steps brand, verify/vet, campaign, link numbers; Low Volume Mixed only without vetting; sole proprietor OTP; brand registration €4.50; allow several days or weeks · accessed 25 October 2026 · official
  6. Vonage API Support – How do I add test numbers during my Vonage API trial €2 free trial credit; only primary users add test numbers by PIN; "[FREE SMS DEMO, TEST MESSAGE]" appended; error "Non White-listed Destination - rejected (29)"; trial credit cannot buy numbers (read via search snippet, page blocked to fetch) [to verify] · accessed 25 October 2026 · official
  7. Vonage API Support – 10 DLC pricing and fees Standard vetting about 41.50, campaign vetting 15 per event, appeal 11, plus possible fines for violations (read via search snippet, page blocked to fetch) [to verify] · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Vonage is not affiliated with verapli.