Vonage SMS API
Our SMS API helps you create customer journeys through conversations - even within the context of your app. [1]
Best for / Avoid if
Best for: Regulated or enterprise workloads - compliance attestations and an enterprise plan; AI agents and automation - an agent-ready surface (MCP / llms.txt); Cost-sensitive teams - low, transparent entry price
Avoid if: You want to try it free before paying
Scores
- 65 / 100Agent friendliness
- 85 / 100Pricing transparency
- 75 / 100Setup speed
- 55 / 100Docs quality
- 85 / 100Procurement ease
- 85 / 100Trust readiness
Pricing & procurement
- Pricing model
- Usage-based [2]
- Published pricing
- ✓ Yes [3]
- Free tier
- ✗ No [4]
- Free tier details
- Start developing now with free credit. No credit card required. [5]
- Self-serve signup
- ✓ Yes [6]
- Requires sales call
- ✗ No [7]
- Enterprise plan
- ✓ Yes [8]
| Item | Per | Amount | Source |
|---|---|---|---|
| Outbound SMS message | message | $0.0081 | source |
| Inbound SMS message | message | $0.0065 | source |
| Virtual phone number | month | $1.04 | source |
| Initial set up fee | $0 | source | |
| Toll free number | month | $1.75 | source |
| Random Dedicated Short code | month | $1000 | source |
| Vanity Dedicated Short code | month | $1500 | source |
| Audit API | month | $550 | source |
| Auto-redact | month | $1100 | source |
Capabilities
- Supported actions
- send_sms, receive_inbound_sms, search_message, delivery_receipt [9]
- Regions
- Global (Local numbers in 76 countries) [10]
- Input types
- JSON, plain text [11]
- Output types
- JSON, XML [12]
- Webhooks
- ✓ Yes [13]
- Sandbox / test mode
- ✓ Yes [14]
- SDK languages
- Node.js, Python, Java, .NET, Ruby, PHP [15]
- MCP server
- ✓ Yes [16]
Trust & compliance
- SOC 2
- SOC 2 Type II [17]
- HIPAA
- ✓ Yes [18]
- GDPR
- – Unknown [19]
- ISO 27001
- ✓ Yes [20]
- PCI DSS
- ✓ Yes [21]
- Published SLA
- ✓ Yes [22]
- Rate limits
- due to carrier restrictions, the rate limit for outbound SMS can be as low as one request per second; the Message API has a rate limit of 1 message per second when sending messages within the US [23]
- Known restrictions
- due to carrier restrictions, the rate limit for outbound SMS can be as low as one request per second, By default Vonage attempts delivery for 72 hours, however the maximum effective value depends on the operator and is typically 24 - 48 hours, country-specific requirements for Sender ID registrations, high-volume traffic queued automatically in accordance with each carrier's regulations, 10 DLC throughput limits vary by carrier (e.g. 600 TPM per number for some carriers) [24]
Developer surface
Integration
- API style
- rest
- Base URL
- https://rest.nexmo.com
- Versioning
- none
- Stability
- ga
- Auth methods
- api_key, basic
- Error format
- vendor-specific
- Webhook signing
- hmac_sha256
- Rate limit
- 30 / second
Adoption & maturity
- Notable customers
- Domino's Pizza, InTouch Health, Story Corps, The Princeton Review, Kickstarter, Doxy.me
Other SMS APIs
Twilio Programmable Messaging
One Messaging API to reliably reach 7B+ devices
Sinch SMS API
"Simple, secure SMS API for global reach"
Bird
The global SMS API that scales with you
Telnyx SMS API
Carrier-grade SMS API with direct routing. No aggregator markup, no middleman margin. Programmable messaging on infrastructure Telnyx owns end-to-end.
Infobip SMS API
Send business text messages with a leading SMS service provider
AWS End User Messaging
AWS End User Messaging empowers developers to integrate scalable and reliable messaging capabilities into their applications. AWS End User Messaging helps you engage your customers by sending them SMS, voice messages, WhatsApp, and push notifications.
References
- ↑Description: vonage.com
- ↑Pricing model: vonage.com · vonage.com
- ↑Published pricing: vonage.com · vonage.com
- ↑Free tier: vonage.com · apidog.com
- ↑Free tier details: vonage.com
- ↑Self-serve signup: github.com · vonage.com
- ↑Requires sales call: github.com · vonage.com
- ↑Enterprise plan: vonage.com
- ↑Supported actions: developer.vonage.com · developer.vonage.com · developer.vonage.com
- ↑Regions: vonage.com
- ↑Input types: developer.vonage.com
- ↑Output types: developer.vonage.com
- ↑Webhooks: developer.vonage.com · developer.vonage.com
- ↑Sandbox: api.support.vonage.com · developer.vonage.com
- ↑SDK languages: github.com · github.com · github.com
- ↑MCP server: developer.vonage.com · developer.vonage.com
- ↑SOC 2: vonage.com · prnewswire.com · vonage.com
- ↑HIPAA: vonage.com · vonage.com
- ↑GDPR: vonage.com · vonage.com
- ↑ISO 27001: vonage.com · vonage.com
- ↑PCI DSS: vonage.com · vonage.com
- ↑Published SLA: vonage.com · vonage.com
- ↑Rate limits: api.support.vonage.com · developer.vonage.com
- ↑Known restrictions: developer.vonage.com · api.support.vonage.com · developer.vonage.com
Change history
- 2026-06-15 Score Agent Friendliness: 55 → 65
- 2026-06-15 Score Docs Quality: 35 → 55
- 2026-06-15 API Reference URL: (none) → https://developer.vonage.com/en/reference
- 2026-06-15 Robots Allows Agents: (none) → Yes
- 2026-06-15 Has Structured Data: (none) → No
- 2026-06-14 Score Agent Friendliness: 40 → 55
- 2026-06-14 Score Docs Quality: 0 → 35
- 2026-06-14 Llms Txt URL: (none) → https://developer.vonage.com/llms.txt
- 2026-06-14 Changelog URL: (none) → https://developer.vonage.com/changelog
- 2026-06-14 Rendering: (none) → static
- 2026-06-14 Llms Txt Present: (none) → Yes
- 2026-06-14 Docs URL: (none) → https://developer.vonage.com
- 2026-06-10 Last Verified At: 2026-06-06T00:00:00.000Z → 2026-06-10T00:00:00.000Z
- 2026-06-10 Scoring Methodology: (none) → Scores are computed deterministically from this profile's published, sourced fi…
- 2026-06-10 Avoid If: (none) → You want to try it free before paying
- 2026-06-10 Best For: (none) → Regulated or enterprise workloads - compliance attestations and an enterprise p…
- 2026-06-10 Score Trust Readiness: (none) → 85
- 2026-06-10 Score Procurement Friction: (none) → 85
- 2026-06-10 Score Docs Quality: (none) → 0
- 2026-06-10 Score Setup Speed: (none) → 75
- 2026-06-10 Score Agent Friendliness: (none) → 40
- 2026-06-10 Score Pricing Transparency: (none) → 85
- 2026-06-10 Starting Price Usd: 0.0081 → 0.00809
- 2026-06-10 SDK Packages: Node.js, Python, Java, .NET, Ruby, PHP → Node.js, Python, Java, .NET, Ruby, PHP
- 2026-06-10 HIPAA: set to Yes
- 2026-06-10 ISO 27001: set to Yes
- 2026-06-10 PCI DSS: set to Yes
- 2026-06-10 SLA Published: set to Yes
- 2026-06-10 Data Retention Policy URL: set to https://api.support.vonage.com/hc/en-us/articles/360001183228-How-long-does-Von…
- 2026-06-10 Documented Rate Limits: set to due to carrier restrictions, the rate limit for outbound SMS can be as low as o…
- 2026-06-10 Rate Limit Requests: set to 30
- 2026-06-10 Rate Limit Window: set to second
- 2026-06-10 Known Restrictions: set to due to carrier restrictions, the rate limit for outbound SMS can be as low as o…
- 2026-06-10 Auth Methods: set to api_key, basic
- 2026-06-10 Auth Docs URL: set to https://developer.vonage.com/en/getting-started/concepts/authentication
- 2026-06-10 API Style: set to rest
- 2026-06-10 Base URL: set to https://rest.nexmo.com
- 2026-06-10 Versioning Scheme: set to none
- 2026-06-10 Stability: set to ga
- 2026-06-10 MCP URL: set to https://documentation-mcp.vonage.dev/mcp
- 2026-06-10 Quickstart URL: set to https://developer.vonage.com/en/messaging/sms/code-snippets/send-an-sms
- 2026-06-10 Error Format: set to vendor-specific
- 2026-06-10 Webhook Signing: set to hmac_sha256
- 2026-06-10 Webhook Events URL: set to https://developer.vonage.com/en/messaging/sms/guides/delivery-receipts
- 2026-06-10 Requires Verification: set to No
- 2026-06-10 Starting Price Usd: set to 0.0081
- 2026-06-10 Price Basis: set to message
- 2026-06-10 Free Tier Limit: set to €2 free credit
- 2026-06-10 Slug: set to vonage-sms
- 2026-06-10 Fields Not Found: set to gdpr, ga_date, launched_at, idempotency_supported, api_version, deprecation_pol…
Suggest an edit / leave a review
Leave a review or comment
curl -X POST https://apio.sh/api/feedback/vonage-sms \
-H 'Content-Type: application/json' \
-d '{"kind":"review","rating":5,"body":"Your experience with this API…"}'Suggest a correction to a field (cite a source)
curl -X POST https://apio.sh/api/suggest/vonage-sms/FIELD \
-H 'Content-Type: application/json' \
-d '{"value":"corrected value","citations":[{"url":"https://source.example/page","excerpt":"supporting quote"}],"note":"what changed and why"}'