How to migrate from Clickatell to Vonage

Clickatell is a cloud messaging and chat-commerce platform offering SMS, WhatsApp, RCS and Apple Messages for Business APIs. Vonage, part of Ericsson, provides communications APIs spanning SMS, voice, video and messaging. On the messaging.dev Score, Clickatell rates 61/100 and Vonage 89/100; this guide covers what actually changes when you move a sending integration from one to the other.

Channels you gain and lose

Both providers cover SMS, RCS and WhatsApp, and neither offers Telegram or email. Moving to Vonage adds four channels: MMS, Viber, Facebook Messenger and voice. The one channel you lose is Apple Messages for Business, which Clickatell supports and Vonage does not. If your integration depends on Apple Messages for Business, plan around that gap before cutting over.

Compliance, residency, pricing and tooling

Both platforms are GDPR, ISO 27001 and SOC 2 aligned; Vonage additionally lists HIPAA. On data residency, Clickatell runs EU servers only with no region choice, while Vonage offers both EU and US servers, a data-residency choice, and APAC/Australia regions.

Pricing stays pay-as-you-go on both sides. Clickatell uses self-service prepaid credits (published from $0.008 per US SMS) with quote-based enterprise plans; Vonage is pay-as-you-go per message/minute with volume discounts (approximately $0.0072 per US SMS segment, plus carrier fees). Vonage also includes €2 free trial credit, which Clickatell does not offer.

Both ship high-quality docs and a sandbox, so your testing workflow carries over. Vonage’s SDK list (Node.js, Python, PHP, Java, C#, Ruby, Kotlin) adds Ruby and Kotlin over Clickatell’s five (Python, PHP, Java, Node.js, C#). One reduction to note: Clickatell exposes both REST and SMPP, whereas Vonage in our data is REST-only. If you rely on an SMPP bind today, you will need to re-architect around REST.

How the request format differs

Clickatell quickstart:

curl -X POST https://platform.clickatell.com/v1/message \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"messages":[{"channel":"sms","to":"27123456789","content":"Hello World"}]}'

Vonage quickstart:

curl -X POST 'https://rest.nexmo.com/sms/json' \
  -d 'api_key=YOUR_API_KEY' \
  -d 'api_secret=YOUR_API_SECRET' \
  -d 'from=Vonage' \
  -d 'to=15551234567' \
  -d 'text=Hello from Vonage'

Three things change:

• Endpoint / base URL moves from https://platform.clickatell.com/v1/message to https://rest.nexmo.com/sms/json (legacy SMS API) or https://api.nexmo.com/v1/messages (Messages API).
• Authentication moves from a raw API key in the Authorization header (no Bearer prefix) to an api_key + api_secret pair sent as form fields — or JWT auth if you adopt the Messages API.
• Payload moves from a JSON body with a nested messages array to flat, form-encoded parameters. Field mapping: recipient to stays to; message body content becomes text; and you now supply an explicit sender via from, which the Clickatell example omits. Clickatell’s per-message channel field disappears on the legacy SMS endpoint, where the channel is implied by the URL.

Migration checklist

1. Create a Vonage account and generate your API Key + API Secret (or set up a JWT application for the Messages API). New accounts include €2 trial credit.
2. Map request fields: rename content to text, keep to, add from, and drop the messages array wrapper and the channel field.
3. Re-point your sending code to the new base URL and switch from a JSON body to form-encoded parameters (or JSON on the Messages API).
4. Re-test in Vonage’s sandbox before sending live traffic — both providers offer one, so your test harness translates over.
5. Update delivery receipts and webhooks to Vonage’s callback format.
6. Run both integrations in parallel and reconcile delivery results.
7. Cut over once volumes and delivery rates match.

See how to start with Vonage for the full quickstart, and the Clickatell vs Vonage comparison for a side-by-side of every dimension.

Watch out for

• Apple Messages for Business is not available on Vonage — the one channel you lose in this move.
• No SMPP: Vonage is REST-only in our data, so any SMPP bind must be reworked to REST.

Otherwise Vonage matches or exceeds Clickatell on channels, compliance (adds HIPAA), residency (adds US servers and region choice), free trial credit and SDK breadth.