How to migrate from SmsManager to Telnyx

SmsManager is a Czech bulk-messaging platform that sends SMS, WhatsApp, Viber and RCS from a single JSON API with direct connections to local mobile operators. Telnyx is a licensed telecom carrier running a CPaaS platform for SMS, MMS, RCS, WhatsApp, voice and email over its own private global IP network. On the messaging.dev Score, SmsManager rates 51/100 and Telnyx 78/100 — this guide covers what actually changes when you re-point your sending code from one to the other.

What changes at a glance

Channels. SMS, RCS and WhatsApp exist on both platforms, so those integrations carry over. Moving to Telnyx you gain MMS, voice and email. You lose Viber and Apple Messages for Business, both of which SmsManager supports and Telnyx does not. Neither provider offers Facebook Messenger or Telegram, so nothing changes there.

Compliance. Both are GDPR-aligned. Telnyx additionally holds ISO 27001, SOC 2 and HIPAA, none of which are listed for SmsManager — relevant if you have audit or healthcare requirements.

Data residency. SmsManager runs on EU servers only, with no region choice. Telnyx offers both EU and US servers, adds Asia-Pacific and South America, and supports a data-residency choice. You keep an EU option and gain the ability to pick a region.

Pricing and free credit. Both bill pay-as-you-go: SmsManager on prepaid, non-expiring credit charged per message; Telnyx per message part with volume discounts. Note that SmsManager includes free developer credit for testing, whereas Telnyx does not.

SDKs, sandbox and docs. SmsManager ships SDKs for JavaScript/TypeScript and PHP; Telnyx covers Node.js, Python, Ruby, Go, Java, .NET and PHP. Both expose a REST API (Telnyx also supports SMPP) and both have high-quality docs. One regression: SmsManager provides a test sandbox; Telnyx does not.

How the request format differs

Source — SmsManager:

curl -X POST https://api.smsmngr.com/v2/message \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body": "Hello from SmsManager!", "to": [{"phone_number": "420777123456"}]}'

Target — 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:

• Endpoint. The base URL moves from https://api.smsmngr.com/v2/message to https://api.telnyx.com/v2/messages.
• Authentication. SmsManager passes the API key in an x-api-key request header. Telnyx uses a Bearer token: Authorization: Bearer YOUR_API_KEY.
• Payload mapping. The message body key changes from body to text. The recipient changes from an array of objects ("to": [{"phone_number": "..."}]) to a single E.164 string ("to": "+15559876543"). And Telnyx requires an explicit sender: the from field is mandatory, whereas the SmsManager quickstart sends without one.

Migration checklist

1. Create a Telnyx account and generate an API key from the dashboard. Provision or port a sending number, since Telnyx requires a from value.
2. Map the request fields: body → text, to: [{phone_number}] → to: "<E.164>", and add the required from.
3. Re-point your sending code to https://api.telnyx.com/v2/messages and swap the x-api-key header for Authorization: Bearer.
4. Re-test. Telnyx has no sandbox, so validate against a live number at low volume rather than a test environment. See how to start with Telnyx for the full quickstart.
5. Update webhooks and delivery callbacks to point at your Telnyx configuration and re-parse status payloads in the new format.
6. Run both in parallel for a period, comparing delivery results side by side.
7. Cut over once the Telnyx path is stable, then retire the SmsManager credentials.

Watch out for

• Viber and Apple Messages for Business disappear. If you send on either channel today, there is no Telnyx equivalent — plan a fallback.
• No sandbox. You cannot dry-run integrations in a test environment; budget for live-traffic testing.
• No free developer credit. Expect to fund the account before sending.
• Structural payload change. to becomes a single string (not an array of objects) and from is now required — a common source of first-request errors.

For a full attribute-by-attribute breakdown, see the SmsManager vs Telnyx comparison.