Mobile SDKs

Native SDKs for Android, iOS, Flutter, and React Native that embed the full Conferbot chat experience in your app - no WebView required. All four SDKs render the complete flow-builder node set, apply your dashboard theming automatically, and ship the same floating chat bubble as the web widget.

💡

Embedding, not automating

These SDKs embed the chat experience in your app and only need your bot ID. To automate Conferbot from your backend - manage chatbots, pull responses, configure webhooks - see the Management API.
Full Flow Support

Every flow-builder node type renders natively - choices, ratings, dates, cards, file uploads, and more

Server-Driven Theming

Colors, avatar, bot name, and widget placement from the dashboard apply automatically - no code

Floating Chat Bubble

The same bottom-corner FAB as the web widget, with unread badge and server-configured CTA tooltip

Live Agent Handover

Seamless bot-to-human transitions with agent join/leave events and typing indicators

Offline Queueing

Messages sent while offline are queued locally and retried automatically when connectivity returns

Push Notification Hooks

FCM (Android, RN, Flutter) and APNs (iOS) token registration for background message delivery

Pick Your Platform

Each SDK has its own in-depth guide covering installation, initialization, the floating widget, theming, live agent handover, offline behavior, push notifications, and troubleshooting:

SDK Overview

PlatformLanguagePackageRegistryMinimum Version
AndroidKotlin (Java compatible)com.conferbot:android-sdkMaven CentralAndroid 5.0 (API 21), Kotlin 1.9
iOSSwift 5.7+ConferbotSPM + CocoaPodsiOS 14.0, Xcode 14
FlutterDart 3conferbot_flutterpub.devFlutter 3.10, Dart 3.0
React NativeTypeScript@conferbot/react-nativenpmReact Native 0.70, iOS 12+, Android API 21+

Credentials

The mobile SDKs need a bot ID - the 24-character hex ID from Bot Settings > General in the Conferbot Dashboard. The bot ID is what actually selects and loads your bot. The apiKey parameter is only validated locally by the SDKs - any placeholder in the conf_ format works (for example conf_test_key). It is not your management REST API key; do not paste that here. Make sure the bot is published - draft flows are not served to the SDKs.

Try it without an account

The public demo bot ID 691c970890527a0468f9b2c9 works without a Conferbot account - drop it into any snippet in the per-SDK guides (with a placeholder API key such as conf_test_key) to evaluate the SDKs immediately.

💡

Separate from the REST API

The mobile SDKs talk to the widget delivery service at https://wdt.conferbot.com (REST + Socket.IO). This is a different product from the management REST API at api-v2.conferbot.com - mobile SDKs do not use x-api-key headers or consume API quota.

⚠️

Bot not appearing?

The three usual causes: the bot is not published (draft flows are not served), the botId is wrong (a bad ID fails silently with an empty chat), or the device cannot reach https://wdt.conferbot.com (corporate proxies that block WebSockets). Sanity-check with the demo bot 691c970890527a0468f9b2c9 - if it loads, your integration code is fine. Each per-SDK guide has a full troubleshooting section.