Assign or Revoke Chat Administrator Rights imbot.chat.setManager
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: chat owner
DEPRECATED
Development of this method has been halted. To assign or revoke administrator rights, use the methods imbot.v2.Chat.Manager.add and imbot.v2.Chat.Manager.delete.
The method imbot.chat.setManager assigns a chat administrator or revokes administrator rights from a chat participant.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CHAT_ID* |
The identifier of the chat. The identifier can be obtained using the method imbot.chat.get |
|
USER_ID* |
The identifier of the user for whom the administrator status is being changed. The user identifier can be obtained using the method imbot.chat.user.list |
|
IS_MANAGER |
Administrator status. Possible values:
Default is |
|
BOT_ID |
The identifier of the chat bot. The bot identifier can be obtained using the method imbot.bot.list. If this parameter is not provided, the method searches for the first bot registered by the current application |
|
CLIENT_ID |
This parameter is required only for webhooks. Pass the same CLIENT_ID that was specified during the chat bot registration |
Code Examples
How to Use Examples in Documentation
curl -X POST /
-H "Content-Type: application/json" /
-H "Accept: application/json" /
-d '{"CHAT_ID":2725,"USER_ID":1269,"IS_MANAGER":"Y","CLIENT_ID":"**put_your_client_id_here**"}' /
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.chat.setManager
curl -X POST /
-H "Content-Type: application/json" /
-H "Accept: application/json" /
-d '{"CHAT_ID":2725,"USER_ID":1269,"IS_MANAGER":"Y","auth":"**put_access_token_here**"}' /
https://**put_your_bitrix24_address**/rest/imbot.chat.setManager
try
{
const response = await $b24.callMethod(
'imbot.chat.setManager',
{
CHAT_ID: 2725,
USER_ID: 1269,
IS_MANAGER: 'Y'
}
);
const result = response.getData().result;
console.log(result);
processResult(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'imbot.chat.setManager',
[
'CHAT_ID' => 2725,
'USER_ID' => 1269,
'IS_MANAGER' => 'Y'
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error setting chat manager: ' . $e->getMessage();
}
BX24.callMethod(
'imbot.chat.setManager',
{
CHAT_ID: 2725,
USER_ID: 1269,
IS_MANAGER: 'Y'
},
function (result)
{
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'imbot.chat.setManager',
[
'CHAT_ID' => 2725,
'USER_ID' => 1269,
'IS_MANAGER' => 'Y'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "imbot.chat.setManager", b24.Params{
"CHAT_ID": 2725,
"USER_ID": 1269,
"IS_MANAGER": "Y",
"CLIENT_ID": "**put_your_client_id_here**",
})
if err != nil {
return fmt.Errorf("imbot.chat.setManager: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("done:", ok)
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1772543706,
"finish": 1772543706.871191,
"duration": 0.8711910247802734,
"processing": 0,
"date_start": "2026-03-03T16:15:06+01:00",
"date_finish": "2026-03-03T16:15:06+01:00",
"operating_reset_at": 1772544306,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
|
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "WRONG_REQUEST",
"error_description": "Change manager can only owner and user must be member in chat"
}
|
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 |
|
|
Chat ID can't be empty |
|
|
|
User ID can't be empty |
|
|
|
Change manager can only owner and user must be member in chat |
Only the chat owner can change administrator rights, and the user must be a member of the chat |
|
|
Bot not found |
Chat bot not found |
|
|
Bot was installed by another rest application |
Chat bot installed by another application |
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 |
|
|
|
The REST API is available only on commercial plans. 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 |
Continue Learning
- Create a chat on behalf of the chat bot imbot.chat.add
- Add Participants to Chat imbot.chat.user.add
- Change Chat Title imbot.chat.updateTitle
- Change Chat Avatar imbot.chat.updateAvatar
- Change Chat Color imbot.chat.updateColor
- Get Chat ID imbot.chat.get
- Get Data About Chat imbot.dialog.get
- Get the List of Chat Participants imbot.chat.user.list
- Exclude Participants from Chat imbot.chat.user.delete
- Chat Bot Exit from Specified Chat imbot.chat.leave