Create a Group Chat imbot.v2.Chat.add
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
imbotWho can execute the method: owner of the registered bot
The method imbot.v2.Chat.add creates a group chat on behalf of the bot and adds the bot as a participant.
To send messages to the created chat, pass result.chat.dialogId from the response to the dialogId parameter of the Messages group methods.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
botId* |
Bot ID |
|
botToken |
Bot token. Required for webhook authorization, not needed for OAuth. Pass the same |
|
fields |
Properties of the chat being created (detailed description) |
Parameter fields
|
Name |
Description |
|
type |
Chat type:
With any other value, the method creates a private chat |
|
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. You do not need to pass the bot — it is added to the chat automatically |
|
ownerId |
ID of the chat owner, the bot by default. The owner is automatically added to the chat as a participant and a manager. The method does not check whether the user exists: with a non-existent ID, the chat is created without an error and is left without an owner |
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);
}
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.imbot.v2.chat.add(
bot_id=456,
fields={
"title": "Support Chat",
"color": "mint",
"userIds": [
1,
2,
],
},
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected 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'];
}
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "imbot.v2.Chat.add", b24.Params{
"botId": 456,
"botToken": "my_bot_token",
"fields": b24.Params{
"title": "Support Chat",
"color": "mint",
"userIds": []int{1, 2},
},
})
if err != nil {
return fmt.Errorf("imbot.v2.Chat.add: %w", err)
}
// The response shape is shown below on this page.
fmt.Printf("%s\n", res.Result)
Response Handling
HTTP Status: 200
{
"result": {
"chat": {
"id": 5,
"dialogId": "chat5",
"name": "Support Chat",
"description": "",
"type": "chat",
"messageType": "C",
"owner": 456,
"color": "#4ba984",
"avatar": "",
"extranet": false,
"containsCollaber": false,
"entityType": "",
"entityId": "",
"entityData1": "",
"entityData2": "",
"entityData3": "",
"entityLink": {
"type": "",
"url": "",
"id": ""
},
"diskFolderId": null,
"role": "owner",
"permissions": {
"manageUsersAdd": "member",
"manageUsersDelete": "manager",
"manageUi": "member",
"manageSettings": "owner",
"manageMessages": "member",
"manageMessagesAutoDelete": "manager",
"manageGuestInvites": "manager",
"manageDelete": "member",
"canPost": "member"
},
"hasManageCapability": false,
"canHaveThreads": true,
"muteList": [],
"parentChatId": null,
"parentMessageId": null,
"isNew": false,
"textFieldEnabled": true,
"backgroundId": null,
"dateCreate": "2025-01-15T10:00:00+02:00",
"lastMessageId": 789,
"lastMessageViews": {
"messageId": 789,
"firstViewers": [],
"countOfViewers": 0
},
"lastId": 0,
"managerList": [456],
"markedId": 0,
"messageCount": 1,
"public": "",
"unreadId": 0,
"userCounter": 3,
"guestCount": 0
},
"users": [
{
"id": 456,
"active": true,
"name": "Support Bot",
"firstName": "Support Bot",
"lastName": "",
"workPosition": "",
"color": "#4ba984",
"avatar": "",
"gender": "M",
"birthday": "",
"extranet": false,
"bot": true,
"connector": false,
"externalAuthId": "bot",
"status": "online",
"idle": false,
"lastActivityDate": false,
"mobileLastDate": false,
"desktopLastDate": false,
"absent": false,
"departments": [],
"phones": false,
"type": "bot",
"website": "",
"email": ""
}
]
},
"time": {
"start": 1728626400.123,
"finish": 1728626400.234,
"duration": 0.111,
"processing": 0.045,
"date_start": "2024-10-11T10:00:00+02:00",
"date_finish": "2024-10-11T10:00:00+02:00"
}
}
Returned Data
|
Name |
Description |
|
result |
Result of chat creation |
|
result.chat |
Object of the created chat (detailed description) |
|
result.users |
An array with a single element — the data of the bot on whose behalf the request was made. Chat participants are returned by imbot.v2.Chat.User.list. Field descriptions — User |
|
time |
Information about the request execution time |
In addition to chat and users, the response contains service keys of the messenger interface: recentConfig, parentChat, copilot, messagesAutoDeleteConfigs, and callInfo. A bot does not need them, so they are omitted from the response example.
Fields of the Chat Object
|
Name |
Description |
|
id |
Chat identifier |
|
dialogId |
Dialog identifier. For a group chat — |
|
name |
Chat title |
|
description |
Chat description. An empty string if not set |
|
type |
Type of chat: |
|
messageType |
Internal single-letter chat type, for example |
|
owner |
ID of the chat owner |
|
color |
Chat color in HEX format |
|
avatar |
URL of the chat avatar. An empty string if not set |
|
extranet |
Whether the chat has extranet users |
|
containsCollaber |
Whether the chat has collabers |
|
entityType |
Type of the linked object, for example |
|
entityId |
Identifier of the linked object |
|
entityData1 |
Additional data of the linked object, field 1 |
|
entityData2 |
Additional data of the linked object, field 2 |
|
entityData3 |
Additional data of the linked object, field 3 |
|
entityLink |
Link to the linked object — an object with the keys |
|
diskFolderId |
ID of the Drive folder that stores the chat files |
|
role |
Role of the bot in the chat: |
|
permissions |
Minimum role for actions in the chat. Keys: |
|
canHaveThreads |
Whether threads can be created in the chat |
|
hasManageCapability |
Service flag of extended access to chat management |
|
muteList |
Contains the bot ID if the bot has turned off notifications in the chat, otherwise an empty array |
|
parentChatId |
ID of the parent chat if this is a thread |
|
parentMessageId |
ID of the parent message if this is a thread |
|
isNew |
|
|
textFieldEnabled |
Whether the message input field is enabled |
|
backgroundId |
Chat background ID |
|
dateCreate |
Date of chat creation in ISO 8601 format |
|
lastMessageId |
ID of the last message |
|
lastMessageViews |
Views of the last message: |
|
lastId |
ID of the last message read by the bot |
|
managerList |
IDs of the chat managers |
|
markedId |
ID of the message the bot marked as unread. |
|
messageCount |
Number of messages in the chat |
|
public |
Public link to the chat — an object with the fields |
|
unreadId |
ID of the first message unread by the bot. |
|
userCounter |
Number of chat participants |
|
guestCount |
Number of guests in the chat |
Which of these fields are included in event data is described on the page Objects and Fields — Chat.
Error Handling
HTTP Status: 400
{
"error": "BOT_NOT_FOUND",
"error_description": "Bot not found"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
Value |
|
|
Bot token not specified (botToken is required for webhook auth) |
|
|
|
botId is required |
|
|
|
Bot not found |
Bot not found |
|
|
Bot was installed by another rest application |
The bot is registered by another application |
|
|
ACCESS_DENIED |
No permission to create chats |
|
|
Error creating chat |
Failed to create the chat |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |