Baasi inc.

Getting Started

The baasi API platform

Generating API Key and Token

Creating a meeting room

Creating participants

Creating a simple HTML document for the web

Initializing baasi TypeScript client SDK

Joining a meeting room

Signaling API

Baasi - Getting Started

Production

Sandbox

<p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Learn the basics of what Baasi Video API is and how it works.</strong></p><p class="slate-p" placeholder="Type / for widgets"></p>

Learn the basics of what Baasi Video API is and how it works.

<p class="slate-p" placeholder="Type / for widgets">The baasi API Platform makes it easy to create a real-time, high-quality interactive video, messaging, screen-sharing, whispering, bridging between different protocols, and more features.</p><p class="slate-p" placeholder="Type / for widgets">The platform includes libraries for various systems: Web, IOS, Android, Windows, macOS, Linux, and React Native, as well as server-side SDKs and a rest API. The Baasi Video API uses <a href="https://webrtc.org/" target="_self">WebRTC</a> for audio-video communications.</p><p class="slate-p" placeholder="Type / for widgets">The Baasi Video API Platform provides a user API key which is used on your web server application to authenticate with the Baasi Cloud and use Baasi Video API features. </p><div  data-type="error" style="background-color:#FFF1F1;color:#ff3030"><div ><svg width="18" height="18" viewBox="0 0 18 18" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M9.08366 9.9801C9.25033 9.9801 9.39269 9.92107 9.51074 9.80302C9.6288 9.68496 9.68783 9.53566 9.68783 9.3551V5.31344C9.68783 5.14677 9.62533 5.00441 9.50033 4.88635C9.37533 4.7683 9.22949 4.70927 9.06283 4.70927C8.88227 4.70927 8.73296 4.7683 8.61491 4.88635C8.49685 5.00441 8.43783 5.15371 8.43783 5.33427V9.37594C8.43783 9.5426 8.50033 9.68496 8.62533 9.80302C8.75033 9.92107 8.9031 9.9801 9.08366 9.9801ZM9.00033 13.1676C9.19477 13.1676 9.35796 13.1016 9.48991 12.9697C9.62185 12.8377 9.68783 12.6745 9.68783 12.4801C9.68783 12.2857 9.62185 12.1225 9.48991 11.9905C9.35796 11.8586 9.19477 11.7926 9.00033 11.7926C8.80588 11.7926 8.64269 11.8586 8.51074 11.9905C8.3788 12.1225 8.31283 12.2857 8.31283 12.4801C8.31283 12.6745 8.3788 12.8377 8.51074 12.9697C8.64269 13.1016 8.80588 13.1676 9.00033 13.1676ZM9.00033 17.3343C7.81977 17.3343 6.72255 17.1225 5.70866 16.6989C4.69477 16.2752 3.81283 15.6884 3.06283 14.9384C2.31283 14.1884 1.72602 13.3065 1.30241 12.2926C0.878798 11.2787 0.666992 10.1815 0.666992 9.00094C0.666992 7.83427 0.878798 6.74399 1.30241 5.7301C1.72602 4.71621 2.31283 3.83427 3.06283 3.08427C3.81283 2.33427 4.69477 1.74399 5.70866 1.31344C6.72255 0.88288 7.81977 0.667603 9.00033 0.667603C10.167 0.667603 11.2573 0.88288 12.2712 1.31344C13.285 1.74399 14.167 2.33427 14.917 3.08427C15.667 3.83427 16.2573 4.71621 16.6878 5.7301C17.1184 6.74399 17.3337 7.83427 17.3337 9.00094C17.3337 10.1815 17.1184 11.2787 16.6878 12.2926C16.2573 13.3065 15.667 14.1884 14.917 14.9384C14.167 15.6884 13.285 16.2752 12.2712 16.6989C11.2573 17.1225 10.167 17.3343 9.00033 17.3343ZM9.00033 16.0843C10.9448 16.0843 12.6114 15.3898 14.0003 14.0009C15.3892 12.612 16.0837 10.9454 16.0837 9.00094C16.0837 7.05649 15.3892 5.38982 14.0003 4.00094C12.6114 2.61205 10.9448 1.9176 9.00033 1.9176C7.05588 1.9176 5.38921 2.61205 4.00033 4.00094C2.61144 5.38982 1.91699 7.05649 1.91699 9.00094C1.91699 10.9454 2.61144 12.612 4.00033 14.0009C5.38921 15.3898 7.05588 16.0843 9.00033 16.0843Z" fill="#E90005"></path></svg></div><div ><p class="slate-p" placeholder="Type / for widgets"><span style="color:#4B85E8" class="slate-color"><strong style="color:#4B85E8" class="slate-bold">DANGER</strong></span><span style="color:#4B85E8" class="slate-color"> </span></p><p class="slate-p" placeholder="Type / for widgets"><span style="color:#4B85E8" class="slate-color">The API key provided is intended for exclusive use within the user&apos;s app server applications. Do not use the API key in client-side SDKs or publicly accessible code. Doing so may expose the key, leading to potential security risks, such as unauthorized access and misuse by malicious actors. To ensure the utmost security, only utilize the API key in your backend environment.</span></p></div></div><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">All applications built with the Baasi Video API platform require two primary components:</strong></p><ul class="slate-ul"><li class="slate-li"><div style="position:relative"><strong class="slate-bold">The client —</strong> client-side code runs in a browser or mobile app, set up by the developer using the Baasi Video API client-side libraries, which are available for Web, IOS, Android, Windows, macOS, Linux, and React Native. The client side handles the majority of Baasi Video API functionality.</div></li><li class="slate-li"><div style="position:relative"><strong class="slate-bold">The Server —</strong> server-side code is executed on a web server set up by the developer using the Baasi Video API server SDKs.</div></li></ul><h2 class="slate-h2">Functions of the client and server</h2><h3 class="slate-h3">Client</h3><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Utilizes the Client SDKs</div></li><li class="slate-li"><div style="position:relative">Gets vm-room IDs and participant ID from the backend server</div></li><li class="slate-li"><div style="position:relative">Connects to the vm-room using a participant ID</div></li><li class="slate-li"><div style="position:relative">Publishes audio-video streams</div></li><li class="slate-li"><div style="position:relative">Subscribes to audio-video streams</div></li><li class="slate-li"><div style="position:relative">Lets clients whisper to each other</div></li><li class="slate-li"><div style="position:relative">Listens for vm-room events</div></li><li class="slate-li"><div style="position:relative">Lets clients share their screens</div></li></ul><h3 class="slate-h3">App<strong class="slate-bold"> </strong>Server</h3><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Utilizes server SDKs (Rest-API)</div></li><li class="slate-li"><div style="position:relative">Creates vm-rooms in the Baasi Video API cloud</div></li><li class="slate-li"><div style="position:relative">Generates tokens for clients</div></li><li class="slate-li"><div style="position:relative">Sends vm-room IDs and tokens to clients</div></li></ul><h3 class="slate-h3">Vm-rooms</h3><ul class="slate-ul"><li class="slate-li"><div style="position:relative">“Chat room” in Baasi Video API cloud</div></li><li class="slate-li"><div style="position:relative">Connects clients to each other</div></li><li class="slate-li"><div style="position:relative">Sends events to clients</div></li><li class="slate-li"><div style="position:relative">Lets clients record the meeting room</div></li></ul><h2 class="slate-h2">Vm-rooms</h2><p class="slate-p" placeholder="Type / for widgets">Every Baasi Video API video chat occurs within a<strong class="slate-bold"> vm-room</strong>. vm-room is the same as a room where clients join and interact with each other in real-time. Vm-rooms are hosted on the Baasi Video API cloud and manage user connections, audio-video streams, vm-room recordings, and user events. Each vm-room is associated with a unique <strong class="slate-bold">vm-room ID</strong>. To allow multiple clients to chat with each other, you must connect them to the same vm-room (using the vm-room ID).</p><p class="slate-p" placeholder="Type / for widgets">The app server is responsible for creating new vm-rooms and generating unique authentication tokens (participant IDs) per client. The client then uses that token(Participant ID) to establish a connection to the vm-room. Clients connected to a vm-room can publish streams to the vm-room and subscribe to other clients&apos; streams. </p>

The baasi API Platform makes it easy to create a real-time, high-quality interactive video, messaging, screen-sharing, whispering, bridging between different protocols, and more features.

The platform includes libraries for various systems: Web, IOS, Android, Windows, macOS, Linux, and React Native, as well as server-side SDKs and a rest API. The Baasi Video API uses 

The Baasi Video API Platform provides a user API key which is used on your web server application to authenticate with the Baasi Cloud and use Baasi Video API features. 

All applications built with the Baasi Video API platform require two primary components:

Every Baasi Video API video chat occurs within a

. vm-room is the same as a room where clients join and interact with each other in real-time. Vm-rooms are hosted on the Baasi Video API cloud and manage user connections, audio-video streams, vm-room recordings, and user events. Each vm-room is associated with a unique 

. To allow multiple clients to chat with each other, you must connect them to the same vm-room (using the vm-room ID).

The app server is responsible for creating new vm-rooms and generating unique authentication tokens (participant IDs) per client. The client then uses that token(Participant ID) to establish a connection to the vm-room. Clients connected to a vm-room can publish streams to the vm-room and subscribe to other clients' streams. 

<p class="slate-p" placeholder="Type / for widgets">Within Baasi cloud, the process begins by obtaining an API Key, a unique identifier granting access to the platform&apos;s functionalities. However, to bolster security, Baasi cloud employs an added layer of protection using tokens.</p><p class="slate-p" placeholder="Type / for widgets">These tokens are dynamically generated in response to user request and come with restricted permissions and a limited timeframe for validity. When users present the server token alongside their API Key, they gain access only to authorized actions and resources. </p><p class="slate-p" placeholder="Type / for widgets">By implementing this two-tier authentication approach, Baasi cloud ensures that even if a token is compromised, the potential risks are contained within the predefined scope. This fortified security approach instills confidence in users, as sensitive operations remain safeguarded from unauthorized access and potential threats within the system.</p><p class="slate-p" placeholder="Type / for widgets"></p><div  data-type="info" style="background-color:#eef1ff;color:#4a59af"><div ><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">HINT</strong></p><p class="slate-p" placeholder="Type / for widgets">To Generate API Key please see: <a href="https://docs.baasi.dev/baasi-getting-api-key" target="_self">getting api key</a>.</p></div></div><p class="slate-p" placeholder="Type / for widgets">To generate a token please see the illustrative HTTP sample request below:</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

Within Baasi cloud, the process begins by obtaining an API Key, a unique identifier granting access to the platform's functionalities. However, to bolster security, Baasi cloud employs an added layer of protection using tokens.

These tokens are dynamically generated in response to user request and come with restricted permissions and a limited timeframe for validity. When users present the server token alongside their API Key, they gain access only to authorized actions and resources. 

By implementing this two-tier authentication approach, Baasi cloud ensures that even if a token is compromised, the potential risks are contained within the predefined scope. This fortified security approach instills confidence in users, as sensitive operations remain safeguarded from unauthorized access and potential threats within the system.

To generate a token please see the illustrative HTTP sample request below:

The sid property corresponds to your sid which identifies your generated API key when interacting with the baasi API. It is a required field and must be a valid UUID.

The accountSid property corresponds to your account SID, which identifies your baasi account. It isrequired and must be a valid UUID.

accountSid

scopes

expiresIn

The key property is used for secure token generation. It should be your secret key associated with your API key and account. This key is essential for generating tokens securely.

Authorization

status

message

data

<p class="slate-p" placeholder="Type / for widgets">A meeting room is a virtual space where individuals or groups can convene and collaborate in real-time using audio, video, and other communication tools. In the context of the provided data and API, a meeting room is created dynamically to facilitate interactions between participants. It can be configured with specific parameters such as participant limits, room type (e.g., mesh or SFU), visibility (public or private), and other settings.</p><p class="slate-p" placeholder="Type / for widgets">Meeting rooms serve as a central hub for various communication activities, including video conferencing, screen sharing, and real-time collaboration. Participants can join these rooms to engage in discussions, share content, and work together on projects, making meeting rooms a versatile solution for a wide range of virtual communication needs. The API allows developers to create, manage, and customize these meeting rooms to suit specific use cases and requirements.</p><p class="slate-p" placeholder="Type / for widgets">Consequently, to establish a meeting room, the creation of a corresponding meeting room is necessary. Within the baasi Cloud environment, the backend server must utilize the baasi Server SDK to transmit requests to the baasi Cloud platform. Proper authentication requires the generation of an access token, as previously described. Following the successful creation of the meeting room, the server generates a response object containing detailed information about the room.</p><p class="slate-p" placeholder="Type / for widgets">The following example shows the request object sent through HTTP to the baasi cloud to create a meeting room:</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

A meeting room is a virtual space where individuals or groups can convene and collaborate in real-time using audio, video, and other communication tools. In the context of the provided data and API, a meeting room is created dynamically to facilitate interactions between participants. It can be configured with specific parameters such as participant limits, room type (e.g., mesh or SFU), visibility (public or private), and other settings.

Meeting rooms serve as a central hub for various communication activities, including video conferencing, screen sharing, and real-time collaboration. Participants can join these rooms to engage in discussions, share content, and work together on projects, making meeting rooms a versatile solution for a wide range of virtual communication needs. The API allows developers to create, manage, and customize these meeting rooms to suit specific use cases and requirements.

Consequently, to establish a meeting room, the creation of a corresponding meeting room is necessary. Within the baasi Cloud environment, the backend server must utilize the baasi Server SDK to transmit requests to the baasi Cloud platform. Proper authentication requires the generation of an access token, as previously described. Following the successful creation of the meeting room, the server generates a response object containing detailed information about the room.

The following example shows the request object sent through HTTP to the baasi cloud to create a meeting room:

The maxP2PSize property specifies the maximum number of participants allowed in the meeting room before it's automatically upgraded to an SFU (Selective Forwarding Unit). It determines the participant threshold for transitioning from a peer-to-peer (P2P) connection mode to an SFU mode.

maxP2PSize

The forceTurnServer property is a boolean flag that indicates whether participants in a mesh room should be shifted to use a TURN (Traversal Using Relays around NAT) server. When set to true, participants in the room will be directed to use a TURN server for network traversal.

foreceTurnServer

The forceSFU property is a boolean flag that, when set to true, specifies that the created room should be automatically of the SFU (Selective Forwarding Unit) type. SFU enables media streams to be selectively forwarded to participants. If set to false, the room will default to a mesh type.

forceSFU

The appData property is an optional object that allows you to include additional metadata or custom data associated with the meeting room. This metadata can be used to store information relevant to your application or business logic.

appData

The visibility property specifies the visibility of the VM (Virtual Meeting) room. It is an enum property with two possible values: "PUBLIC" and "PRIVATE." A "PUBLIC" room is accessible to all participants, while a "PRIVATE" room restricts access to authorized participants.

visibility

<p class="slate-p" placeholder="Type / for widgets">A participant represents an active entity engaged in virtual meetings or communication sessions hosted within a meeting room. Participants can contribute to the collaborative environment of the meeting space. They have distinct identities, statuses, and roles within the meeting, making them integral to the communication dynamics. Participants can vary in type, permissions, and signaling protocols, and they play a pivotal role in enabling real-time interactions, content sharing, and collaboration among users within the virtual meeting room. The API provides functionalities to manage participants, ensuring smooth and controlled engagement within these virtual environments.</p><p class="slate-p" placeholder="Type / for widgets">To facilitate the creation of participants within a meeting room, the backend server must initiate an HTTP request to the baasi Cloud and complete the authentication process using the provided token, as previously elucidated. Following the successful creation of the participant, the server generates and transmits a response object containing comprehensive details concerning the newly added participant.
Below is an illustrative example of the HTTP request object sent to the baasi Cloud for participant creation in the room:</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

A participant represents an active entity engaged in virtual meetings or communication sessions hosted within a meeting room. Participants can contribute to the collaborative environment of the meeting space. They have distinct identities, statuses, and roles within the meeting, making them integral to the communication dynamics. Participants can vary in type, permissions, and signaling protocols, and they play a pivotal role in enabling real-time interactions, content sharing, and collaboration among users within the virtual meeting room. The API provides functionalities to manage participants, ensuring smooth and controlled engagement within these virtual environments.

To facilitate the creation of participants within a meeting room, the backend server must initiate an HTTP request to the baasi Cloud and complete the authentication process using the provided token, as previously elucidated. Following the successful creation of the participant, the server generates and transmits a response object containing comprehensive details concerning the newly added participant.
Below is an illustrative example of the HTTP request object sent to the baasi Cloud for participant creation in the room:

The name property represents the name of the participant being added to the meeting room. It typically contains the participant's full name or display name.

name

The email property specifies the email address of the participant. It is used to uniquely identify participants and can be used for communication or identification purposes.

email

The permission property is an array that defines the permissions or roles assigned to the participant within the meeting room. Each element in the array represents a specific permission granted to the participant. Permissions can control actions such as muting, kicking other participants, sharing screens, and more.

permission

The signalingProtocol property indicates the signaling protocol used by the participant to connect to the meeting room. It can be one of the following enum values: "SIP," "H.323," "RestAPI," "Email invitation," or "webRTC."

signalingProtocol

The type property specifies the type or role of the participant within the meeting room. It can be one of the following enum values: "guest," "registered," "operator," "supervisor," "thirdPartyGuest," "thirdPartyOperator," "host," or "recorder." Different participant types may have different privileges and roles.

type

The forceTurnServer property is a boolean flag that determines whether the participant should join the meeting room using a TURN (Traversal Using Relays around NAT) server for network traversal. When set to true, the participant connects via a TURN server.

forceTurnServer

The monitoringOnly property is a boolean flag that indicates whether the participant is in a "listen-in" mode. If set to true, the participant is in a monitoring-only mode and does not actively participate in calls but can listen to them.

monitoringOnly

The appData property allows you to include optional additional data associated with the participant. This data can be custom metadata or any information relevant to your application.

The unique identifier (roomId) of the meeting room to which you want to add a participant.

<p class="slate-p" placeholder="Type / for widgets">Given that the server setup is complete, the remaining step involves a client that connects to your backend server to acquire a token and subsequently join the call using said token. Client connections and events are managed through the baasi Client SDK, which exclusively necessitates the token, a participant ID for client identification, and a room ID for establishing the connection to the VM-room.
The ensuing example demonstrates the creation of a straightforward HTML document:</p>

Given that the server setup is complete, the remaining step involves a client that connects to your backend server to acquire a token and subsequently join the call using said token. Client connections and events are managed through the baasi Client SDK, which exclusively necessitates the token, a participant ID for client identification, and a room ID for establishing the connection to the VM-room.
The ensuing example demonstrates the creation of a straightforward HTML document:

<p class="slate-p" placeholder="Type / for widgets">The HTML document has been pre-configured, and the next step involves initializing the TypeScript client SDK to enable users to execute various actions, including joining meeting rooms, leaving meeting rooms, and subscribing to relevant events, among others.</p><p class="slate-p" placeholder="Type / for widgets">The following example demonstrates how to initialize the baasi client Typescript SDK:</p><div  data-type="info" style="background-color:#eef1ff;color:#4a59af"><div ><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">HINT</strong></p><p class="slate-p" placeholder="Type / for widgets">For more information about baasi TypeScript Client SDK please refer to: <a href="https://docs.baasi.dev/baasi-client-sdk-typescript-sdk" target="_self">baasi client SDK</a></p></div></div><p class="slate-p" placeholder="Type / for widgets"></p>

The HTML document has been pre-configured, and the next step involves initializing the TypeScript client SDK to enable users to execute various actions, including joining meeting rooms, leaving meeting rooms, and subscribing to relevant events, among others.

The following example demonstrates how to initialize the baasi client Typescript SDK:

<p class="slate-p" placeholder="Type / for widgets">With the existing setup in place, the next task is to facilitate clients&apos; participation in the meeting call and enable them to interact with one another. To achieve this, we need to develop a TypeScript code that takes the client&apos;s parameters and the designated room ID as input to establish the connection.
The following code snippet demonstrates the utilization of the TypeScript SDK to initiate the connection to the room:</p>

With the existing setup in place, the next task is to facilitate clients' participation in the meeting call and enable them to interact with one another. To achieve this, we need to develop a TypeScript code that takes the client's parameters and the designated room ID as input to establish the connection.
The following code snippet demonstrates the utilization of the TypeScript SDK to initiate the connection to the room:

Sections