Connect the template to your instance

Connecting a self-built front end to your Arino One instance is a configuration task: provision the instance, add your own Infobip keys, point webhooks at the right endpoints, and verify both directions of messaging before disabling the bundled demo data.

This applies to Option 1 — Self-build, the free build option, on either the Remix route (you create your own Infobip account) or the BYO route (you connect an Infobip account you already have). If you chose Option 2 — We build it for you ($350 one-time), Arino performs these steps for you; this page is still useful as a reference for what was configured.

The $50/month Arino Core connection is optional and separate from this work. Add it after the instance is live if you want WebRTC in-browser calling at $0.009/minute, support, management and updates.

Step 1 — Confirm your route and Infobip account

On the Remix route, follow Infobip's signup flow and create the account in your own name before configuring anything. On the BYO route, have your existing Infobip API key and base URL to hand. In both cases the Infobip account is yours and Infobip bills you directly for usage; Meta fees are billed by Meta.

Step 2 — Give Arino access to your Lovable account

This step is optional for a pure self-build, but required if you want Arino to help configure the instance now or manage it later under the Arino Core connection.

An admin on the client's side must first create a Lovable account, then give Arino access so we can install and manage the instance in the client's workspace.

1. Create the client's Lovable account using this link: https://lovable.dev/invite/KCYVCL4.
2. (Recommended) Grant Arino access to the whole workspace: open Lovable, click the workspace name in the top-left, choose Settings, open the People or Members tab, click Invite, enter hello@arino.one, assign the Admin role so Arino can configure secrets, API keys and deploy, and send the invite.
3. Alternatively, share a single project only: open the project in the Lovable editor, click Share, enter hello@arino.one, and send.

Arino must accept the invite before access is active. Workspace-level Admin access is preferred because it lets Arino configure environment variables, secrets and deployment without asking for help on every change.

Step 3 — Provision the instance

Register on client.arino.one, confirm your account by OTP and email, and provision the instance your remixed front end will call. Note the API base URL and connection details — you will need them in step 5. If Arino built your instance, these are handed to you directly.

Step 4 — Add your Infobip keys

In Settings → Channels on the instance, add your own Infobip API key and base URL. This is always the client's own Infobip account.

Step 5 — Set environment variables in the front end

In your remixed Lovable project, set the instance API base URL and public key as environment variables in your deployment configuration. The front end reads these to know which instance to call; without them it falls back to the bundled demo dataset.

Step 6 — Configure and verify webhooks

Point your Infobip webhook configuration at your instance's inbound endpoints for messages, delivery receipts and status updates. Send a test message through the console, confirm it is delivered, then send an inbound test message and confirm both the message and its delivery receipt arrive correctly. If webhooks do not arrive, check the endpoint URL and any firewall or allow-list rules on your deployment.

Step 7 — Go live

Once both directions verify, disable the bundled demo dataset so the front end reads only live data, and switch your Infobip sender and webhook URLs from any staging configuration to production. From this point, Infobip and Meta bill you directly for usage. If you want WebRTC calling, support and managed updates, add the optional $50/month Arino Core connection — otherwise your instance simply runs independently.

Steps at a glance

1. Confirm your route and Infobip accountOn the Remix route, create your own Infobip account first. On the BYO route, have your existing Infobip account and keys ready. Either way the Infobip account is yours and you pay Infobip directly.
2. Give Arino access to your Lovable account (optional but recommended)If you want Arino to help configure or later manage your remixed instance, an admin on the client's side creates a Lovable account, then gives Arino access. 1. Create the account using this link: [https://lovable.dev/invite/KCYVCL4](https://lovable.dev/invite/KCYVCL4). 2. (Recommended) Grant Arino workspace access: open Lovable, click the workspace name in the top-left, choose Settings, open the People or Members tab, click Invite, enter `hello@arino.one`, assign the Admin role so Arino can configure secrets, API keys and deploy, and send the invite. 3. Alternatively, share a single project: open the project in the Lovable editor, click Share, enter `hello@arino.one`, and send. Arino must accept the invite before access is active. Workspace-level Admin access is preferred because it lets Arino configure environment variables, secrets and deployment without asking for help on every change.
3. Provision the instanceRegister on client.arino.one and provision the instance your remixed front end will talk to. If you took the We build it for you option, Arino provisions it for you; if you self-built, provision it yourself and note the API base URL.
4. Add your Infobip keysIn Settings → Channels, add your own Infobip API key and base URL. Every Arino One instance uses the client's own Infobip account.
5. Set environment variables in the front endIn your remixed project, set the instance API base URL and public key as environment variables in your Lovable deployment so the front end talks to the correct instance.
6. Configure webhook endpointsPoint your Infobip webhook configuration at your instance's inbound endpoints for messages, delivery receipts and status updates.
7. Verify the connectionSend a test message end to end and confirm it appears in the console, then confirm an inbound reply and a delivery receipt both arrive correctly.
8. Disable demo data and go liveTurn off the bundled sample dataset in the front end so it reads only live data, then switch your sender and webhook URLs to production. Add the optional $50/month Arino Core connection if you want WebRTC calling, support and managed updates.

Frequently asked