How to migrate from Attentive to Infobip

Attentive is an AI-powered SMS, MMS, RCS, email, and push marketing platform for consumer brands, whose REST and GraphQL APIs handle subscriber management and event-triggered messaging rather than direct sends. Infobip is a global omnichannel communications platform for SMS, WhatsApp, voice, email, and more, with a direct-send REST API. On the messaging.dev Score, Attentive rates 40/100 and Infobip 96/100 — presented here as data to help you scope the move, not as an endorsement.

What changes when you move

Channels. Both platforms cover SMS, MMS, RCS, and email. Moving to Infobip you gain WhatsApp, Viber, Facebook Messenger, Telegram, Apple Messages for Business, and Voice. You lose no messaging channels in the switch.

Compliance. Both are GDPR- and SOC 2-aligned. Infobip additionally lists ISO 27001 and HIPAA, so you gain those two certifications.

Data residency. Attentive runs on US servers only, with no region choice. Infobip offers both US and EU servers plus a data-residency choice, and lists additional regions across APAC, Latin America, the Middle East, and Africa.

Onboarding and pricing. Attentive has no self-serve signup and prices as a custom-quoted, usage-based subscription with no free developer credit. Infobip supports self-onboarding, includes free trial credit, and is primarily quote/contract-based with some pay-as-you-go options.

SDKs, sandbox, and docs. Attentive ships mobile SDKs (iOS/Swift, Android/Kotlin, React Native); Infobip ships server-side SDKs (Java, C#, Python, PHP, Go, Node.js). Both provide a sandbox. Docs quality moves from medium (Attentive) to high (Infobip). On API surface, Attentive exposes REST and GraphQL, while Infobip exposes REST, SMPP, and SMTP.

How the request format differs

Attentive quickstart:

curl -X POST 'https://api.attentivemobile.com/v1/events/custom' \
  -H 'Authorization: Bearer <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
    "type": "Order Shipped",
    "user": { "phone": "+13115552368" },
    "properties": { "Order Id": "54321" }
  }'

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

Endpoint. Attentive posts to a fixed host, https://api.attentivemobile.com/v1, at the /events/custom path. Infobip posts to a per-account base URL, https://{base_url}.api.infobip.com/sms/2/text/advanced — the {base_url} subdomain is specific to your account, so read it from your dashboard rather than hardcoding a shared host.

Authentication. Attentive uses a Bearer API key (Authorization: Bearer <API_KEY>), with OAuth 2.0 available for public apps. Infobip uses an API-key scheme with a different keyword: Authorization: App {api_key}.

Payload mapping. This is the biggest conceptual shift. Attentive has no direct send-SMS endpoint — you emit an event (type plus properties) tied to a user.phone, and a configured journey composes and sends the actual message. Infobip sends directly: the recipient moves from user.phone to messages[].destinations[].to, you now supply a sender (messages[].from) that Attentive never required, and the message body itself lives in messages[].text instead of being assembled downstream by a journey.

Migration checklist

1. Create an Infobip account (self-onboarding, free trial credit) and generate an API key.
2. Record your account {base_url} subdomain from the dashboard.
3. Map your fields: recipient user.phone to destinations[].to, add a from sender, and move message copy into text instead of relying on journey composition.
4. Re-point sending code to the new endpoint and swap Authorization: Bearer for Authorization: App.
5. Re-test against Infobip’s sandbox before sending live traffic.
6. Update delivery callbacks/webhooks to consume Infobip’s delivery reports.
7. Run both integrations in parallel and reconcile delivery.
8. Cut over once the new path is verified.

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

Watch out for

• No GraphQL. Infobip exposes REST, SMPP, and SMTP but not GraphQL — any Attentive integration built on its GraphQL API must be rewritten as REST.
• No mobile SDKs. Infobip’s SDKs are server-side only (Java, C#, Python, PHP, Go, Node.js); Attentive’s iOS, Android, and React Native SDKs have no direct equivalent, so mobile-client code needs a different approach.
• You now own message composition. Attentive’s journey model built the message for you; on Infobip you must provide the from sender and full text on every send.
• Pricing still needs a quote. Neither provider publishes a starting SMS price; both are primarily quote-based, though Infobip adds some pay-as-you-go options.