Add Participants to Chat imbot.v2.Chat.User.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.User.add adds participants to the chat. The bot must be a participant of the chat: by default, any participant can add new users. If this permission is restricted in the chat settings, the bot needs the corresponding role — see Chat Roles.
In a personal chat, the method adds no one but returns true. You cannot use this method to add participants to the general chat or to workgroup, comment, and call chats.
The method skips non-existent and inactive users, as well as users who are already chat participants, without an error. If userIds is empty or not passed, the method returns true.
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 |
|
dialogId* |
ID of the group chat in the dialogId format: |
|
userIds |
Array of user IDs to add |
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","dialogId":"chat5","userIds":[1,2,3]}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.v2.Chat.User.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"botId":456,"dialogId":"chat5","userIds":[1,2,3],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/imbot.v2.Chat.User.add
try {
const response = await $b24.callMethod('imbot.v2.Chat.User.add', {
botId: 456,
dialogId: 'chat5',
userIds: [1, 2, 3],
});
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.user.add(
bot_id=456,
dialog_id="chat5",
user_ids=[
1,
2,
3,
],
).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.User.add',
[
'botId' => 456,
'dialogId' => 'chat5',
'userIds' => [1, 2, 3],
]
);
$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.User.add',
{
botId: 456,
dialogId: 'chat5',
userIds: [1, 2, 3],
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imbot.v2.Chat.User.add',
[
'botId' => 456,
'dialogId' => 'chat5',
'userIds' => [1, 2, 3],
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Users added';
}
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "imbot.v2.Chat.User.add", b24.Params{
"botId": 456,
"botToken": "my_bot_token",
"dialogId": "chat5",
"userIds": []int{1, 2, 3},
})
if err != nil {
return fmt.Errorf("imbot.v2.Chat.User.add: %w", err)
}
var item struct {
Result bool `json:"result"`
}
if err := json.Unmarshal(res.Result, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.Result)
Response Handling
HTTP Status: 200
{
"result": {
"result": true
},
"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 the operation |
|
result.result |
|
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "ACCESS_DENIED",
"error_description": "ACCESS_DENIED"
}
|
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 |
|
|
CHAT_NOT_FOUND |
No chat found with the specified |
|
|
ACCESS_DENIED |
The bot is not a participant of the chat, has no permission to add participants, or participants cannot be added to chats of this type |
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 |