Web Chatbot SDK — Release Notes
Version history for the EnableX Dialogs Web Chatbot SDK — a plain-JavaScript client for building a custom web chat UI against the Dialogs chatbot engine. Releases are shown in reverse chronological order — latest first.
This is the first published release of the Web Chatbot SDK. Download: dialogs-chatbot-web-v1.0.js
v1.0.0 is a first-milestone plain-script SDK that wraps the channel-web REST API and guest Socket.IO connection described in Chat Bots, so you don't have to implement session handling, reconnects, and event parsing yourself.
What's included
- Connect to the Dialogs backend via the guest Socket.IO namespace, with a persisted
visitorIdinlocalStorageand automaticwebSessionIdtracking - Auto-reconnect with configurable attempts/delay (
reconnect: { autoReconnect, maxAttempts, delayMs }), plus manualreconnect()/disconnect()/disableAutoReconnect() - Optional client-side host validation via
validateHost(), matching the check the official embed performs before showing its widget - Create a new conversation (
createConversation()) and track the "current" conversation for later calls - List conversations (
listConversations()) and load full history for one conversation (getConversation()) - Reset a conversation (
resetConversation()) - Send and receive text messages, with a typing indicator
- Upload files via
sendFile() - Fetch bot metadata via
getBotInfo()(no connection required)
Not included in this release
The following channel-web capabilities exist on the backend but are not yet wrapped by this SDK version. You can still reach them with direct REST calls as documented in Chat Bots:
- Sending the
visitevent / other raw events - Quick-reply and postback UI helpers (the payload can be sent manually, but the SDK does not parse or expose it)
- Startup form submission and language preferences
- Agent handoff status (
payload.handoverStatusis not surfaced as a dedicated event) - Click-to-call signalling (
payload.clickToCallEventis not surfaced as a dedicated event)
This SDK does not add authentication or domain validation beyond the optional
validateHost() check — see the Security section
of the SDK reference before exposing a bot publicly.