How to migrate from 46elks to Infobip

46elks is a Swedish telecom API platform for sending SMS and MMS, making voice calls, and managing virtual numbers. Infobip is a global omnichannel communications platform that spans SMS, the major chat apps, voice, and email. On the messaging.dev Score, 46elks rates 33/100 and Infobip 96/100 — a gap driven mostly by channel breadth, certifications, and SDK coverage. This guide covers what actually changes at the API level when you move.

What you gain and lose

Channels. You keep SMS, MMS, and voice — both platforms support all three, so no channel is lost in the move. You gain RCS, WhatsApp, Viber, Facebook Messenger, Telegram, Apple Messages for Business, and email.

Compliance. Both providers are GDPR-aligned. Infobip additionally lists ISO 27001, SOC 2, and HIPAA, none of which 46elks lists.

Data residency. 46elks stores data on EU servers only, with no region choice. Infobip offers both EU and US servers plus APAC, Latin America, Middle East, and Africa, and lets you choose your data residency region.

Tooling. 46elks ships no official SDKs (REST only) and rates medium on docs quality. Infobip provides SDKs for Java, C#, Python, PHP, Go, and Node.js, supports REST, SMPP, and SMTP, and rates high on docs. Both offer a sandbox.

Pricing. Here you trade transparency for scale. 46elks is prepaid pay-as-you-go with a published starting price (€0.047 per SMS part to Sweden, ex VAT), no startup fees, and no minimums. Infobip is primarily quote/contract-based (contact sales), with some pay-as-you-go options and no publicly listed SMS price — but new accounts include free trial credit, which 46elks does not offer.

How the request format differs

46elks quickstart:

curl https://api.46elks.com/a1/sms \
    -u <api_username>:<api_password> \
    -d from=CurlyElk \
    -d to=+46700000000 \
    -d message="Bring a sweater, it's cold outside"

Infobip quickstart:

curl -X POST 'https://xxxxxx.api.infobip.com/sms/2/text/advanced' \
  -H 'Authorization: App YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"messages":[{"from":"InfoSMS","destinations":[{"to":"15551234567"}],"text":"Hello from Infobip"}]}'

The endpoint changes from a fixed host to an account-specific one: 46elks posts to https://api.46elks.com/a1/sms, while Infobip posts to https://{base_url}.api.infobip.com/sms/2/text/advanced, where {base_url} is unique to your account.

Authentication changes from HTTP Basic (the -u username:password pair from your dashboard) to an API key sent in an Authorization: App {api_key} header.

The payload also changes shape. 46elks sends form-encoded fields; Infobip sends a JSON body. The sender from maps to from in both. The recipient to becomes an entry in a destinations array (destinations[].to). The body field message becomes text, and Infobip wraps everything in a messages array so you can batch multiple messages in one call.

Migration checklist

1. Create an Infobip account and generate an API key from the dashboard; new accounts include free trial credit. See how to start with Infobip.
2. Note your account-specific {base_url} from the dashboard — it prefixes every endpoint.
3. Map the request fields: from → from, to → destinations[].to, message → text, all wrapped in a messages array.
4. Swap authentication: replace HTTP Basic (-u) with the Authorization: App {api_key} header, and set Content-Type: application/json.
5. Re-point your sending code to the new endpoint, optionally adopting one of Infobip’s SDKs (Java, C#, Python, PHP, Go, Node.js).
6. Re-test in Infobip’s sandbox before sending live traffic — both providers offer one.
7. Update your delivery-report webhooks and callbacks to Infobip’s payload structure.
8. Run both integrations in parallel, verify delivery and reporting, then cut over.

Watch out for

• Pricing moves to contact-sales. Infobip’s SMS price is not publicly listed and is primarily quote/contract-based, versus 46elks’ published pay-as-you-go rate. Budget for a sales conversation before you commit volume.
• Fewer countries listed. Infobip lists 190 countries covered against 46elks’ 215 — confirm your destinations are supported.
• Account-specific base URL. Don’t hardcode a single host as you did with 46elks; the {base_url} prefix is unique to your account.

For a full side-by-side, see the 46elks vs Infobip comparison.