How to migrate from Clickatell to Telnyx

Clickatell is a cloud messaging and chat-commerce platform offering SMS, WhatsApp, RCS and Apple Messages for Business APIs. Telnyx is a licensed telecom carrier running a CPaaS platform with APIs for SMS, MMS, RCS, WhatsApp, voice and email over its own private global IP network. On the messaging.dev Score, Clickatell rates 61/100 and Telnyx 78/100 — this guide covers what actually changes at the code and account level when you switch.

What you gain and lose

Channels. Both providers cover SMS, RCS and WhatsApp, so those integrations carry over. Moving to Telnyx adds MMS, voice and email. The one channel you lose is Apple Messages for Business, which Clickatell supports and Telnyx does not — if you rely on it, keep a Clickatell path or plan a replacement. Neither provider offers Viber, Facebook Messenger or Telegram.

Compliance and data residency. Both hold GDPR, ISO 27001 and SOC 2. Telnyx additionally holds HIPAA, which Clickatell lacks. On residency, Clickatell offers EU servers only with no region choice; Telnyx runs both US and EU servers, lets you choose data residency, and also lists Asia-Pacific and South America.

Pricing and credit. Both are self-service and pay-as-you-go. Clickatell uses prepaid credits (with quote-based enterprise tiers) at a published $0.008 per US SMS; Telnyx bills per message part with volume discounts at $0.004 per US outbound part, plus carrier fees. Neither provider offers a free developer credit.

Tooling. Docs quality is high on both, and both expose REST and SMPP. SDK coverage overlaps on Python, PHP, Java and Node.js; Telnyx adds Ruby, Go and .NET, while Clickatell ships C#. The notable regression is testing: Clickatell provides a sandbox, Telnyx does not.

How the request format differs

Clickatell:

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"}]}'

Telnyx:

curl -X POST https://api.telnyx.com/v2/messages \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "from": "+15551234567",
    "to": "+15559876543",
    "text": "Hello, world!"
  }'

Three things change. The endpoint moves from https://platform.clickatell.com/v1/message to https://api.telnyx.com/v2/messages. Authentication changes prefix: Clickatell passes the raw API key in the Authorization header with no prefix, while Telnyx expects Authorization: Bearer YOUR_API_KEY. The payload flattens: Clickatell wraps one or more messages in a messages array, each object carrying channel, to and content, whereas Telnyx sends a single flat object with from, to and text. In practice content becomes text, to moves to the top level, and you add an explicit from sender that the Clickatell example omits; the channel field disappears because the Telnyx messages endpoint is SMS/MMS-specific.

Migration checklist

1. Create a Telnyx account and generate an API key from the dashboard. See how to start with Telnyx.
2. Map request fields: rename content to text, lift to out of the messages array, add a from sender, and drop the channel wrapper.
3. Re-point sending code to https://api.telnyx.com/v2/messages and switch the auth header to the Bearer scheme.
4. Swap in an official SDK if you use one — Node.js is the Telnyx quickstart language.
5. Re-test. Telnyx has no sandbox, so validate against the live endpoint using a test number and low volume.
6. Update delivery/status webhooks and callback URLs to consume Telnyx’s payloads instead of Clickatell’s.
7. Run both providers in parallel, compare delivery, then cut over once traffic looks clean.

Watch out for

• No sandbox on Telnyx — you can no longer dry-run against an isolated test environment; testing happens on live endpoints.
• You lose Apple Messages for Business — Telnyx does not offer this channel.
• No free developer credit — the same as Clickatell, so budget for paid testing.
• Fewer countries listed — Telnyx reports 130 versus Clickatell’s 190; confirm your destinations are covered.
• Auth prefix trap — omitting Bearer will fail authentication against Telnyx.

For a full side-by-side, see Clickatell vs Telnyx.