Documentation Communication channels Viber

Channels integration

Viber

Viber integration overview
  • CategoryChannels
  • AuthAPI key

Overview

Viber connects through Infobip as the Business Solution Provider. On /channels/viber in the dashboard you paste the Viber sender you registered with Infobip, the Infobip API key and the Infobip Base URL, then click Connect. MessageMind routes outbound Viber messages through Infobip's send API using that sender, and Infobip forwards inbound Viber messages to the MessageMind webhook URL shown on the same page. Viber Business Messages is the only supported path; MessageMind does not connect to Viber directly because Viber only registers senders through approved BSPs like Infobip.

What MessageMind can do with it

  • Send and receive Viber Business Messages inside the shared inbox using the Infobip-registered sender as the business identity.
  • Resolve one person as one contact across Viber, WhatsApp and SMS when the Infobip subscriber id is an MSISDN, so the AI picks up full history for returning customers.
  • Reach over a billion Viber users across 190+ countries once your Infobip sender is approved.
  • Store the Viber identifier on the contact so repeat messages on the same thread stay joined to the existing contact and history.

Requirements

  • An Infobip account with a Viber Business Messages sender registered and approved. Infobip handles Viber's commercial approval and the sender fee (about €100 per month at the time of writing).
  • The Infobip API key and Base URL (shown in Infobip under Developer Tools, API keys).
  • The Infobip inbound webhook configured to forward Viber messages to the webhook URL displayed on /channels/viber. Without it, replies never reach the inbox.

How to connect

  1. Register a Viber Business Messages sender with Infobip (they are a verified Viber partner and handle Viber's commercial approval and the recurring sender fee).
  2. In the Infobip portal, forward inbound Viber messages to the webhook URL shown on /channels/viber so replies land in the shared inbox.
  3. In Infobip, go to Developer Tools then API keys and copy your API key and the Base URL displayed on that page. Keys stay visible for about two days, so create a new one if you cannot see the key value any more.
  4. On /channels/viber in MessageMind, paste the Viber sender (as registered on Infobip), the API key and the Base URL, then click Connect. Optional: set a display name and avatar URL to override how the Viber identity appears in the inbox.

Authentication and permissions

Mechanism
Infobip API key against your Infobip account, scoped to the Viber Business Messages sender you registered.
Credentials
Viber sender (routing key), Infobip API key (stored securely, used in the Authorization header to Infobip's send API) and Infobip Base URL (your account's regional host, for example xxxxx.api.infobip.com). Display name and avatar URL are optional presentation fields.

Available data and actions

Reads

  • The inbound Viber delivery that Infobip posts to the MessageMind webhook, carrying the subscriber identifier and message body.
  • The Viber identifier on an existing contact, used to join a new Infobip delivery onto that contact instead of minting a new one.

Writes

  • Outbound Viber Business Messages posted to Infobip's send API using the stored sender, API key and Base URL.
  • The Viber identifier on the contact so repeat deliveries from the same subscriber join the existing thread.
  • A phone identifier on the contact when Infobip exposes the subscriber MSISDN, which is how a Viber contact and a WhatsApp or SMS contact for the same number collapse into one.

AI agent use cases

  • Serve customers in markets where Viber is the dominant messaging app (Eastern Europe, parts of Southeast Asia) without opening a separate inbox for it.
  • Reach the same customer who writes on WhatsApp and on Viber from one contact and one AI thread.
  • Send transactional updates (order shipped, booking confirmed) over Viber Business Messages while using the same AI persona that answers website chat and email.

Configuration

  • Infobip issues keys that are visible only for about two days. If you cannot see the key value when you come back to copy it, create a new one in Developer Tools then API keys.
  • The Base URL is per-region on Infobip (for example xxxxx.api.infobip.com). Use the host shown on your Infobip API keys page, not a generic infobip.com URL.
  • Display name and avatar URL on the connect form override how the Viber identity appears in the shared inbox, but do not change what Viber subscribers see; the Infobip-registered sender name governs that.

Example workflows

First-time Infobip-backed connect

  1. Create a Viber Business Messages sender in Infobip and wait for Viber's commercial approval.
  2. In Infobip, point the Viber inbound webhook at the URL shown on /channels/viber in MessageMind.
  3. In Infobip, go to Developer Tools, API keys and copy the API key value and the Base URL shown on that page.
  4. On /channels/viber, paste the Viber sender, API key and Base URL, add an optional display name and avatar URL, then click Connect.
  5. Send a test Viber message to the sender. It should appear in the shared inbox against the matching contact; the AI replies from the same sender.

Infobip API key rotation

  1. In Infobip, generate a new API key in Developer Tools, API keys. The previous key stops working as soon as you revoke it.
  2. Copy the new key value (it only stays visible briefly).
  3. On /channels/viber, paste the new key into the Infobip API key field and click Connect to save. MessageMind resumes sending with the new key immediately.

Limitations

  • There is no direct-to-Viber path. The connector only works through Infobip as the BSP; the Viber sender has to live on Infobip.
  • The Viber sender is set once per connection. Switching sender requires disconnecting and reconnecting with the new sender and credentials.
  • Infobip's sender fee (about €100 per month) is charged by Infobip, not by MessageMind. The fee applies even while the sender is only used for testing.
  • If Infobip's inbound webhook is not pointed at the MessageMind URL shown on /channels/viber, outbound sends still work but replies never reach the inbox.
  • Viber does not disclose the subscriber's email, and MessageMind does not infer one from the Viber thread.

Troubleshooting

The connect form shows 'Credentials not fully configured yet. Add your Infobip API key + Base URL (or set them on the server), then retry.'

The API key or Base URL field is blank or whitespace-only. Paste both values from Infobip Developer Tools, API keys and click Connect again.

A toast shows 'Could not connect Viber.'

Infobip rejected the credentials. Confirm the Viber sender matches the one approved on Infobip, that the Base URL is your account's host (for example xxxxx.api.infobip.com) and that the API key has not been revoked. Create a new API key in Infobip if the previous one is older than two days and you did not record it.

Outbound Viber messages succeed, but replies never show up in the inbox.

Infobip's inbound webhook is not pointed at MessageMind. In Infobip, forward inbound Viber messages to the webhook URL shown on /channels/viber.

A Viber customer writes a second time and a brand new contact is created instead of the existing one.

Infobip switched the subscriber identifier between deliveries (MSISDN on one, opaque id on the other). The two threads merge once a later delivery brings a shared identifier.

Disconnect and reconnect

  • On /channels/viber, click Disconnect on the top-right of the connected sender card. The confirmation toast reads 'Viber disconnected.' and the stored API key, Base URL and sender are cleared.
  • After disconnect, MessageMind stops sending Viber messages immediately. Infobip-side inbound webhooks still fire, but their payloads are discarded because no account claims the sender.
  • The Infobip sender itself keeps living under your Infobip account. If you want to stop the monthly sender fee, pause or delete it in Infobip, not in MessageMind.
  • To reconnect later, repaste the sender, API key and Base URL on /channels/viber.