Overview
Before starting to build a chat service, it's important to understand the core functionalities of your Sendbird application. By learning how to manage connections with the Sendbird server, authenticate users, and understand how rate limits work, you can build a chat in your app that ensures optimal performance and stability.
Functionalities by topic
The following is a list of basic functionalities for application management that our Chat SDK provides.
Authenticating a user
Functionality | Description | Open channel | Group channel |
---|---|---|---|
Initializes the Chat SDK by passing | |||
Authenticates a user using a unique user ID and connect to the Sendbird server. | |||
Authenticates a user using a unique user ID and a token and connect to the Sendbird server. | |||
Sets a session handler to automatically refresh a user's session token when it's expired. | |||
Disconnects a user from the Sendbird server when they no longer need to receive messages from an online state. | |||
Disconnects only the WebSocket, keeping all locally cached data. |
Understanding rate limits
Functionality | Description | Open Channel | Group channel |
---|---|---|---|
Sendbird applications have default limits on the number of messages per second that a user can send. | |||
Rate limits are applied to SDK methods that are associated with objects such as channel, user, and message. | |||
Some real-time events taking place in client apps are rate-limited. | |||
When a request is rate-limited, two types of errors are returned. |