This page explains the key functions of group call consisting of how to create a room and how a user can participate in a group call by entering and exiting a room.
Note: Right now, the Rooms API for group call supports retrieving rooms and participants in rooms. Other actions should be done from Sendbird Calls SDK.
The type of a room. A type indicates the room type as audio or video and the capacity of a room. Valid values are large_room_for_audio_only which can hold up to 100 participants and small_room_for_video which can hold up to 6 participants.
The timestamp of when the room information was updated, in Unix milliseconds.
state
string
The state of the room. Valid values are the following: - Open: Indicates that users can enter the room to participate in a group call. - Deleted: Indicates that users can't enter the room and the room can't be reopened.
created_by
string
The user ID of the user who created the room. If the room is created with the Platform API, an empty string will be returned.
deleted_by
string
The user ID of the user who deleted the room. If the room is deleted with the Platform API, an empty string will be returned.
current_participants[]
list
The users who are currently in the room.
custom_items
nested object
Specifies a JSON object that has custom key-value items to add. The key and value must be a string and its length is limited to 128 characters. This parameter can have up to 10 custom items.
The timestamp of when the participant entered the room, in Unix milliseconds.
updated_at
long
The timestamp of when the participant information was updated within the room, in Unix milliseconds.
exited_at
Nullable[long]
The timestamp of when the participant exited the room, in Unix milliseconds.
* This value is null until the participant leaves the room.
duration
Nullable[long]
The period from the time when the participant entered the room to the time the participant left the room, measured in seconds.
* This value is null until the participant leaves the room.
connected_at
Nullable[long]
The timestamp of when the participant was connected and streaming media in the room, in Unix milliseconds.
* This value is null until the participant leaves the room.
client_id
string
The unique ID of the client.
state
string
The state of the participant. Valid values are the following: - entered: Indicates that a participant entered the room. - connected: Indicates that a participant is connected and streaming media. - exited: Indicates that a participant exited the room.
user
User
The user who can access all features of the room.
is_audio_on
bool
Indicates whether the participant has turned on their audio.
is_video_on
bool
Indicates whether the participant has turned on their video.
API endpoints are relative to the base URL allocated to your application. In this page, the /rooms endpoint refers to https://api-{application_id}.calls.sendbird.com/v1/rooms.
Note: If you want to know your application ID, sign in to your dashboard, go to the Settings > Application > General, and then check the Application ID.
It's recommended that the parameter values in API URLs be urlencoded, such as {user_id}.
The following table lists the properties of an HTTP request that this action supports.
Parameters
Required
Type
Description
type
string
Specifies the type of the room. Acceptable values are the following: - small_room_for_video: type of a room that supports audio and video, can have up to 6 participants. - large_room_for_audio_only: type of a room that only supports audio, can have up to 100 participants.
Optional
Type
Description
custom_items
nested object
Specifies a JSON object that has key-value custom items to add. The key and value must be a string and its length is limited to 128 characters. This parameter can have up to 10 custom items.
Deletes a specific room. Once a room is deleted, the current participants are removed from the room and the room can't be reopened. Users can retrieve a deleted room, but can't enter it. Also, the custom items of the deleted room can be retrieved, but can't be updated or deleted.
Retrieves all rooms within the application. The retrieved list of rooms are sorted in reverse order, meaning the newest room appears first and the oldest last.
The following table lists the properties of an HTTP request that this action supports.
Optional
Parameter name
Type
Description
limit
string
Specifies the number of results to return per page. Acceptable values are 1 to 100, inclusive. (Default: 10)
next
string
Specifies the value of the next property in the response to retrieve the next page in the result set.
type
type
Restricts the search scope to only retrieve rooms of which the type matches any of the specified values. Acceptable values are all, large_room_for_audio_only, and small_room_for_video. (Default: all)
room_ids
string
Searches for rooms which the specified room IDs are included in the parameter value. The string should consist of multiple URL encoded room IDs separated by commas. Example: ?room_ids=urlencoded_id_1, urlencoded_id_2
* The room_id can be used interchangeably with this parameter, but can only specify one room ID. When both room_id and room_ids are specified, an error will be returned. * The maximum number of room IDs in a single request is 10.
state
string
Restricts the search scope to only retrieve rooms of which state matches any of the specified value. Acceptable values are open and deleted.
created_at_start_date
int
Specifies the value of time period to restrict the search scope to only retrieve rooms of which the room's created_at is equal to or greater than the specified value, in Unix milliseconds. The search scope may be specified in conjunction with the created_at_end_date parameter. When both the start date and end date aren't provided, the start date will be set to 2 weeks prior to the date which the request was made by default.
created_at_end_date
int
Specifies the value of time period to restrict the search scope to only retrieve rooms of which the room's created_at is less than the specified value, in Unix milliseconds. The search scope may be specified in conjunction with the created_at_start_date parameter.
current_participant_range_gte
int
Specifies the number of current participants to restrict the search scope to only retrieve rooms which the number of participants is equal to or greater than the specified value. The search scope may be specified in conjunction with the current_participant_range_lte parameter.
current_participant_range_lte
int
Specifies the number of current participants to restrict the search scope to only retrieve rooms which the number of participants is equal to or less than the specified value. The search scope may be specified in conjunction with the current_participant_range_gte parameter.
created_by_user_ids
string
Searches for rooms which the specified user IDs of users who created rooms are included in the parameter value. The string should consist of multiple URL encoded user IDs separated by commas. Example: ?created_by_user_ids=urlencoded_id_1, urlencoded_id_2
* The created_by_user_id can be used interchangeably with this parameter, but can only specify one user ID. When both created_by_user_id and created_by_user_ids are specified, an error will be returned. * The maximum number of user IDs in a single request is 10.
The custom items including the updated or newly added ones.
affected_at
long
The time of when the specified custom items have been updated, in Unix milliseconds. If custom items do not exist in the target room, affected_at is excluded in the response.
The following table lists the properties of an HTTP request that this action supports.
Properties
Required
Type
Description
custom_items
nested object
Specifies a JSON object that has key-value custom items to update. The key and value must be a string and its length is limited to 128 characters. This parameter can have up to 10 custom items.
Optional
Type
Description
mode
string
Determines whether to update the existing custom items or add new custom items. Acceptable values are the following: - upsert (default): The existing items are updated with new values when there are already custom items with the same keys. - insert: New key-value custom items are added when the keys don't exist on the list of custom items.
Retrieves all participants that were created in the room. The retrieved list of participants are sorted in reverse order, meaning the newest participant appears first and the oldest last.