Skip to main content

Migration from Infobip to Orbit

This guide walks you through migrating your SMS, WhatsApp, and lookup integration from Infobip to Orbit—not just the send endpoint, but the moments flows, Answers bots, and delivery-report handling that come with it. The migration can be completed incrementally.

Concept Mapping


Step 1: Create Your Orbit Account

  1. Sign up at orbit.devotel.io/signup
  2. Generate an API key at Settings > API Keys
  3. Replace your Infobip base URL + key with that single X-API-Key header — every request in this guide targets https://api.orbit.devotel.io.

Step 2: Port Your Numbers

Port your existing Infobip numbers to Orbit so SMS keep landing on the same sender ids. The process takes 7–14 business days. A port request must carry a Letter of Authorization (LoA). Orbit only accepts an LoA URL it issued itself, so upload the signed PDF to Orbit first and submit the returned URL. See the full walkthrough in Number Porting or use the interactive port form.
Alternative: purchase new numbers and cut traffic over gradually.

Step 3: Map Moments / scenario groupings to Messaging Services

Group the Infobip “scenario” or sender pool concept into an Orbit Messaging Service so opt-out handling, inbound webhooks, and sender selection live in one object you reference on every send. Create one in the dashboard under Messaging > Services and note its id—you will pass it as messaging_service_id below.

Step 4: Update the SMS payload

Infobip (before)

Orbit (after)


Step 5: Rewrite the delivery-report consumer (Infobip batched arrays → one event per outcome)

Infobip POSTs delivery reports as a batch — one HTTP request carries a results array with one entry per message outcome. Orbit instead sends one webhook event per outcome, so your handler iterates over one object instead of a list, and signature-verifies a header instead of parsing a batch envelope. Infobip (before) — one request, many results:
Orbit (after) — one request per outcome; verify the signature header:
See the full event catalogue in Webhook Events and the signature recipe in Webhook Signature Verification.

Step 6: Re-register your WhatsApp sender

WhatsApp Business senders must be re-registered under the Orbit WABA integration — you cannot carry the Infobip sender over silently. Follow WABA setup, then re-submit your templates and reload your 24-hour window policy. If you are moving the sender over an existing Meta account, the WABA migration playbook covers the swap without downtime.

Step 7: Replace Infobip Validate / Lookup with Number Intelligence

If you gate sends on Infobip’s “Validate” or “Lookup” services, switch those checks to Orbit’s lookup endpoint — same inputs, same HLR/MNP/risk signal, run inside your own tenant.
See Number lookup for the lookup formats and cached-result behaviour, and the dashboard view in Number Intelligence.

Step 8: Swap Verify/OTP (if applicable)

See Verify in 30 minutes for the full setup.

Step 9: Rebuild Moments flows and Answers bots in Orbit (optional)

  • Moments (customer flows)Flows. Recreate the visual flow in the drag-and-drop builder and point your campaign entry at the new flow id.
  • Answers (chatbot)Agents. Define the agent’s prompt + channels (SMS/WhatsApp/voice) and route inbound messages to it — the AI-agent rollout pipeline guide covers the safe rollout sequence.

Migration Checklist

  • Create Orbit account and generate API keys
  • Replace Infobip base-URL + API-key auth with the single X-API-Key header
  • Port numbers or purchase new ones
  • Create a Messaging Service and note its id
  • Install the Orbit SDK (npm install @devotel-orbit/node)
  • Swap the SMS payload to POST /api/v1/messages
  • Rewrite the DLR consumer from a batched-array handler to a single-event handler
  • Re-register the WhatsApp sender and templates under WABA
  • Swap number-validation calls to the lookup endpoint
  • Swap Verify/OTP if applicable
  • Rebuild Moments flows and Answers bots in Flows / Agents if applicable
  • Update monitoring and alerting on the new webhooks
  • Run parallel sends (Infobip and Orbit side by side)
  • Decommission the Infobip integration

Parallel Running Strategy

Run Infobip and Orbit in parallel while you cut over:
  1. Phase 1 (Week 1–2): send 10% of traffic through Orbit, 90% through Infobip
  2. Phase 2 (Week 3–4): split 50/50 and compare delivery rates and callback handling
  3. Phase 3 (Week 5): route 100% through Orbit, keep Infobip as a fallback webhook sink
  4. Phase 4 (Week 6+): decommission the Infobip integration and cancel the account
Need help with your migration? Our solutions team offers free migration support for customers moving from Infobip. Contact migrate@devotel.io.