Sign In

Latest Version version_js

Mesibo Javascript SDK for Chat, Video and Voice Calls, and Conferencing

Install Mesibo Javascript SDK

The easiest way to install mesibo Javascript SDK is to include following in <HEAD> section of your HTML file:

<script src="https://cdn.mesibo.com/api/mesibo-version_js.js"></script>

or, to always use the latest version,

<script src="https://cdn.mesibo.com/api/mesibo.js"></script>

You can also use async and defer attributes inside script tag if requires.

Alternatively, you may also use DOM method to load the mesibo JS on demand when it is not possible to use the script tag.

const script = document.createElement("script");
script.src = "https://cdn.mesibo.com/api/mesibo.js";
document.body.appendChild(script);

IMPORTANT - Secure https website is required

  • You MUST use a secure website (https) to use mesibo javascript. It may NOT work from http:// or file:// sites due to browser security restrictions.
  • You MUST also use a valid certificate with recognized authority, the self-signed certificate will NOT work.

The browser will not grant the camera and microphone permissions unless your app meets the above requirements. If permissions are not granted, calls and conferencing will not work.

These restrictions are by the browsers and NOT by the mesibo. Refer Security section in the Mozilla documentationopen_in_new for more information.

Please ensure you are not using a private or incognito browser window when using mesibo. mesibo JavaScript API utilizes IndexedDB for local storage of messages, which does not function in private/incognito browsing modes. For the best experience, use a regular browser window so mesibo can fully leverage browser storage capabilities.

Sample code

You can download sample code for Messaging, Voice and Video Call using mesibo Javascript SDK from our GitHub Repositoryopen_in_new

Important Notes for Mobile Usage

For mobile applications, we recommend using mesibo native SDKs which provide superior performance for real-time applications on mobile devices compared to JavaScript. Research shows that WebSockets on mobile can disconnect after just 20-60 seconds in background mode due to aggressive battery optimization. Also, a 2019 Hindawi study demonstrated that WebSockets consume more power than optimized native solutions, which may result in mobile OS disconnecting connections sooner. Native SDKs are specifically engineered to work with platform-specific power management features, use efficient battery-friendly background processing, maintain reliable connections through network changes, and properly handle device sleep states—critical capabilities that JavaScript-based WebSocket implementations simply cannot match due to browser and OS restrictions designed to conserve battery life.