How to migrate from LINK Mobility to Telnyx

LINK Mobility is a European communications-platform-as-a-service (CPaaS) provider that sends SMS and several chat channels through REST, SMPP, and SOAP APIs. Telnyx is a licensed telecom carrier that runs its own private global IP network and exposes a CPaaS platform over REST and SMPP. On the messaging.dev Score, LINK Mobility rates 36/100 and Telnyx 78/100. This guide covers what changes at the product and API level when you move between them.

What you gain and what you lose

Both providers cover SMS, MMS, RCS, WhatsApp, voice, and email, so your core traffic carries over unchanged. The concrete loss is on the chat side: LINK Mobility supports Viber, Facebook Messenger, and Telegram, and Telnyx supports none of the three. If you send on any of those channels today, plan a replacement or a second vendor. Neither provider offers Apple Messages for Business, so there is no channel you gain by switching.

On compliance you move up. Both hold GDPR and ISO 27001, and Telnyx additionally lists SOC 2 and HIPAA, which LINK Mobility does not. Data residency also broadens: LINK Mobility runs EU servers only with no region choice, while Telnyx offers both EU and US servers, explicit data-residency choice, and Asia-Pacific and South America regions.

Pricing and onboarding differ in kind. LINK Mobility uses volume-based enterprise pricing negotiated through sales, with no published per-message rate and no self-onboarding. Telnyx is self-service with published pay-as-you-go pricing from $0.004 per outbound SMS message part (US, plus carrier fees). Neither offers a free developer credit. Telnyx documentation is rated high against LINK Mobility’s medium, and Telnyx ships official SDKs for Node.js, Python, Ruby, Go, Java, .NET, and PHP, where LINK Mobility lists none. One API-surface loss: LINK Mobility exposes REST, SMPP, and SOAP, while Telnyx exposes REST and SMPP, so any SOAP integration must be rebuilt.

How the request format differs

LINK Mobility quickstart:

curl -X POST https://n-eu.linkmobility.io/sms/send \
  -u "USERNAME:PASSWORD" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "LINK",
    "destination": "+4799999999",
    "userData": "Hello world",
    "platformId": "0",
    "platformPartnerId": "0",
    "useDeliveryReport": false
  }'

Telnyx quickstart:

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 a regional base URL (https://n-eu.linkmobility.io/sms/send) to https://api.telnyx.com/v2/messages. Authentication moves from HTTP Basic (-u "USERNAME:PASSWORD", an Authorization: Basic header) to a Bearer API key (Authorization: Bearer YOUR_API_KEY). The JSON payload flattens: source maps to from, destination maps to to, and userData maps to text. Note that LINK Mobility’s source accepts an alphanumeric sender ID ("LINK"), while Telnyx’s from expects an E.164 number. The platformId, platformPartnerId, and useDeliveryReport fields have no equivalent in the basic Telnyx request and are dropped.

Migration checklist

1. Create a Telnyx account (onboarding is self-service) and generate an API key in the dashboard.
2. Map each request field: source→from, destination→to, userData→text; drop the platform fields; convert senders to E.164 format.
3. Swap the auth mechanism from HTTP Basic to a Bearer token, and update the base URL to https://api.telnyx.com/v2/messages.
4. Re-point your sending code, or adopt an official Telnyx SDK for retries and error handling.
5. Re-test. Telnyx has no sandbox, so validate with low-volume live sends to numbers you control.
6. Update webhooks and delivery-report callbacks to Telnyx’s format, replacing LINK Mobility’s useDeliveryReport/DLR flow.
7. Run both providers in parallel on a slice of traffic, compare delivery, then cut over fully.

Watch out for

• No Viber, Facebook Messenger, or Telegram on Telnyx — you lose all three if you use them.
• No sandbox, so your first tests are live and billable.
• No free developer credit; you pay from the first message.
• No SOAP API — any SOAP integration must be rebuilt on REST or SMPP.

For a field-by-field breakdown, see the LINK Mobility vs Telnyx comparison, and for setup details the Telnyx quickstart.