Infobip and Lovable: how it works, and how to connect
Infobip is the communications platform that carries your messages, and Arino One is the layer inside your Lovable app that talks to it. Your app can't hold WhatsApp Business API and carrier relationships directly, so the instance sends and receives through Infobip on every channel — WhatsApp, SMS, and the rest — and you connect it with a single API key and base URL.
This page explains how the two fit together, then how to connect your own account.
How a message flows
When your Lovable app sends a message, it hands it to your Arino One instance. The instance calls Infobip over its API, Infobip delivers to the channel — Meta for WhatsApp, the carrier for SMS — and delivery receipts and inbound replies come back the same way, through Infobip to your instance and into your inbox. You work with one clean interface inside your own app; Infobip handles the messy, regulated last mile.
Why this split matters
Terminating channels yourself means direct WhatsApp Business API onboarding, carrier agreements, number provisioning, and ongoing compliance in every market you send to. That is a telecoms business, not an app feature. By using Infobip as the carrier layer and Arino One as the in-app layer, you get global reach without becoming an integrator — and because the instance is yours, you keep ownership of the data and the sender relationships. For the reasoning behind building this on Lovable, see why Arino One builds on Lovable.
Whose account the keys belong to
The keys are always yours. On the Remix route you create your own Infobip account during onboarding; on the BYO route you connect the account you already have. Senders and billing stay in your name and you pay Infobip directly. While you are on the $50/month Arino Core connection, Arino can help you set the connection up. Either way, the connection is the same two values: an API key and your account base URL.
Connect your Infobip account
In your Infobip account, copy your API key and your base URL — the personalised api host shown in your account. In your Arino One instance, open the Infobip connection settings under Channels, paste both values, and save. Run the built-in connection test to confirm the instance can reach Infobip before you register any senders. Once the test passes, you're ready to add a channel — start with adding WhatsApp.
Regions and data residency
Your instance runs in the region tied to your account — EU, North America or APAC — and Infobip routes through its own regional infrastructure. If data location matters for your compliance, review the data-residency resources before you go live.
Steps at a glance
- Get your Infobip credentialsIn your Infobip account, copy your API key and your account base URL (the personalised api host).
- Open Channels settings in your instanceIn your Arino One instance, go to the Infobip connection settings under Channels.
- Enter the key and base URLPaste your API key and base URL, then save. On the $50/month Arino Core connection, Arino can enter these with you.
- Run the connection testUse the built-in test to confirm the instance can reach Infobip before you register any senders.
Frequently asked
Why does a Lovable app need Infobip at all?
A Lovable app can't hold direct carrier and WhatsApp Business API relationships. Infobip is the communications platform that terminates those channels; Arino One is the layer inside your app that talks to Infobip, so you get messaging without becoming a telecoms integrator.
Whose Infobip account is used?
Always your own. On the Remix route you create your Infobip account during onboarding; on the BYO route you connect the account you already have. Either way senders and billing are yours and you pay Infobip directly.
Where is my messaging data processed?
Your instance runs in the region tied to your account — EU, North America or APAC — and Infobip routes through its own regional infrastructure. See the data-residency resources for detail.
Apply this to your own deployment
This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.