Create a Group Chat imbot.v2.Chat.add
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
imbotWho can execute the method: owner of the registered bot
The method imbot.v2.Chat.add creates a new group chat on behalf of the bot. If the owner is not specified, the bot becomes the owner.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
botId* |
Bot ID |
|
botToken |
Unique authorization token for the bot. Required for webhook authorization, not needed for OAuth. Pass the same botToken that was specified during the chat bot registration |
|
fields |
Properties of the chat being created. The structure of the object is described below |
Parameter fields
|
Name |
Description |
|
title |
Chat title |
|
description |
Chat description |
|
color |
Chat color — available colors. If not specified or incorrect, it will be assigned automatically |
|
avatar |
Chat avatar in Base64 format |
|
userIds |
Array of participant IDs |
|
ownerId |
ID of the chat owner. If not specified, the bot becomes the owner |
|
message |
First message in the chat |
Available Colors
|
Code |
HEX |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"botId":456,"botToken":"my_bot_token","fields":{"title":"Support Chat","color":"mint","userIds":[1,2]}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.v2.Chat.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"botId":456,"fields":{"title":"Support Chat","color":"mint","userIds":[1,2]},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/imbot.v2.Chat.add
try {
const response = await $b24.callMethod('imbot.v2.Chat.add', {
botId: 456,
fields: {
title: 'Support Chat',
color: 'mint',
userIds: [1, 2],
},
});
const { result } = response.getData();
console.log('result:', result);
} catch (error) {
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'imbot.v2.Chat.add',
[
'botId' => 456,
'fields' => [
'title' => 'Support Chat',
'color' => 'mint',
'userIds' => [1, 2],
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'result: '. print_r($result, true);
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error: '. $exception->getMessage();
}
BX24.callMethod(
'imbot.v2.Chat.add',
{
botId: 456,
fields: {
title: 'Support Chat',
color: 'mint',
userIds: [1, 2],
},
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log('Chat ID:', result.data().chat.id);
}
}
);
require_once('crest.php');
$result = CRest::call(
'imbot.v2.Chat.add',
[
'botId' => 456,
'fields' => [
'title' => 'Support Chat',
'color' => 'mint',
'userIds' => [1, 2],
],
]
);
if (!empty($result['error'])) {
echo 'Error: '. $result['error_description'];
} else {
echo 'Chat ID: '. $result['result']['chat']['id'];
}
Response Handling
HTTP Code: 200
{
"result": {
"chat": {
"id": 5,
"dialogId": "chat5",
"name": "Support Chat",
"description": "",
"owner": 456,
"color": "#4ba984",
"avatar": "",
"type": "chat",
"role": "owner",
"dateCreate": "2025-01-15T10:00:00+01:00",
"lastMessageId": null,
"muteList": [],
"managerList": []
},
"users": [
{
"id": 1,
"active": true,
"name": "John Smith",
"type": "employee"
},
{
"id": 2,
"active": true,
"name": "Anna Davis",
"type": "employee"
}
]
},
"time": {
"start": 1728626400.123,
"finish": 1728626400.234,
"duration": 0.111,
"processing": 0.045,
"date_start": "2024-10-11T10:00:00+01:00",
"date_finish": "2024-10-11T10:00:00+01:00"
}
}
Returned Data
|
Name |
Description |
|
result |
Result of chat creation |
|
result.chat |
Object of the created chat (detailed description) |
|
result.users |
Array of chat participants (detailed description) |
|
time |
Information about the request execution time |
Fields of the Chat Object
|
Field |
Description |
|
id |
Chat identifier |
|
dialogId |
Dialog identifier |
|
name |
Chat name |
|
description |
Chat description |
|
owner |
Chat owner identifier |
|
color |
Chat color |
|
avatar |
Avatar URL |
|
type |
Chat type |
|
role |
Bot's role in the chat |
|
dateCreate |
Chat creation date |
|
lastMessageId |
Identifier of the last message |
|
muteList |
List of users with notifications turned off |
|
managerList |
List of chat administrators |
Fields of the User Object
|
Field |
Description |
|
id |
User identifier |
|
active |
User is active |
|
name |
User's first and last name |
|
type |
User type |
Complete description of all object fields can be found on the Objects and Fields page.
Error Handling
HTTP Status: 400, 403
{
"error": "BOT_NOT_FOUND",
"error_description": "Bot not found"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Description |
Value |
|
|
Bot token is not specified |
|
|
|
Bot ID is required |
|
|
|
Bot not found |
Bot not found |
|
|
Bot is registered by another application |
Bot is registered by another application |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- API Change Log for imbot.v2
- Get Information About the Chat imbot.v2.Chat.get
- Update Chat Properties imbot.v2.Chat.update
- Add Participants to Chat imbot.v2.Chat.User.add
- Leave Chat imbot.v2.Chat.leave