How to migrate from GatewayAPI to Infobip

GatewayAPI is a Danish SMS gateway and messaging platform (by ONLINECITY.IO) offering SMS, RCS and email on pay-as-you-go pricing with EU data hosting. Infobip is a global omnichannel communications platform covering SMS plus MMS, WhatsApp, Voice and more. On the messaging.dev Score, GatewayAPI rates 54/100 and Infobip 96/100 — this guide walks through moving an SMS integration from one to the other, presented as data rather than a recommendation.

What changes when you move

Channels. Both platforms send SMS, RCS and email, so those transfer directly — you lose no channels by migrating. Infobip additionally supports MMS, WhatsApp, Viber, Facebook Messenger, Telegram, Apple Messages for Business and Voice, none of which GatewayAPI offers.

Compliance. GatewayAPI is GDPR-aligned. Infobip adds ISO 27001, SOC 2 and HIPAA on top of GDPR.

Data residency. Both offer EU hosting and data-residency choice. GatewayAPI is EU-only with no US servers; Infobip adds US servers plus APAC, Latin America, Middle East and Africa regions.

Tooling and docs. GatewayAPI publishes no official SDKs and has no sandbox, with docs rated medium. Infobip ships SDKs for Java, C#, Python, PHP, Go and Node.js, provides a sandbox test environment, and its docs are rated high. Both expose REST and SMPP; GatewayAPI adds Email-to-SMS, Infobip adds SMTP.

Pricing. GatewayAPI uses transparent prepaid pay-as-you-go pricing from €0.0061 per SMS with no monthly fees. Infobip is primarily quote/contract-based (contact sales), with some pay-as-you-go options and no publicly listed SMS price. Both offer free developer/trial credit to start, though Infobip’s credit amount is not specified.

How the request format differs

GatewayAPI:

curl https://gatewayapi.com/rest/mtsms \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"sender": "ExampleSMS", "message": "Hello World", "recipients": [{"msisdn": 4512345678}]}'

Infobip:

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

Endpoint. GatewayAPI posts to a fixed host, https://gatewayapi.com/rest/mtsms (gatewayapi.eu for EU-hosted accounts). Infobip posts to a per-account personalized base URL, https://{base_url}.api.infobip.com/sms/2/text/advanced — read your {base_url} subdomain from the dashboard.

Authentication. Both use an Authorization header, but the scheme keyword changes: GatewayAPI expects Authorization: Token YOUR_API_TOKEN, Infobip expects Authorization: App YOUR_API_KEY. Infobip also wants an Accept: application/json header.

Payload. GatewayAPI sends a single flat object: sender, message, and a recipients array of {"msisdn": <number>} entries with numeric MSISDNs. Infobip wraps everything in a messages array; within each entry sender becomes from, message becomes text, and recipients[].msisdn becomes destinations[].to — a string rather than a number.

Migration checklist

1. Create an Infobip account — self-onboarding, no sales call needed — and generate an API key in the dashboard. Note your personalized {base_url}.
2. Map the request fields: sender → from, message → text, recipients[].msisdn → destinations[].to, wrap each message in the messages array, and convert numeric MSISDNs to strings.
3. Re-point your sending code to the new base URL, swap the auth header from Token to App, and add Accept: application/json.
4. Re-test in the sandbox. Infobip provides a sandbox test environment (GatewayAPI did not), so validate your integration before sending live traffic.
5. Update delivery callbacks. Re-configure your delivery-report webhooks to Infobip’s endpoints and payload format.
6. Run both in parallel, comparing delivery and reporting on a subset of traffic.
7. Cut over once results match, then retire your GatewayAPI credentials.

For a fuller walkthrough see how to start with Infobip, and for the full side-by-side see the GatewayAPI vs Infobip comparison.

Watch out for

• Pricing transparency. You move from a public price list (from €0.0061/SMS, no monthly fees) to a primarily quote/contract-based model. Infobip’s SMS price is not publicly listed, so budget via a sales quote.
• Trial credit is unspecified. Infobip includes free trial credit, but the amount is not published — confirm it before planning test volumes.
• Country coverage. Infobip lists 190 countries versus GatewayAPI’s 200; verify your specific destinations are covered.
• Account-specific base URL. The endpoint is not a shared host — forgetting your {base_url} subdomain is the most common first-call error.