Exclude Participants from Chat imbot.chat.user.delete

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: imbot

Who can execute the method: an authorized user of the application that registered the chat bot.

DEPRECATED

The development of this method has been halted. Please use imbot.v2.Chat.User.delete.

The method imbot.chat.user.delete removes a user from the chat.

Method Parameters

Required parameters are marked with *

Name
type

Description

CHAT_ID*
integer

The identifier of the chat.

The identifier can be obtained using the method imbot.chat.get

USER_ID*
integer

The identifier of the user to be removed from the chat.

You can get the user ID using the method imbot.chat.user.list

BOT_ID
integer

The identifier of the chat bot. You can obtain the bot ID 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
string

This parameter is required only for webhooks. Pass the same CLIENT_ID that was specified during the registration of the chat bot

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,"CLIENT_ID":"**put_your_client_id_here**"}' /
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.chat.user.delete
        
curl -X POST /
        -H "Content-Type: application/json" /
        -H "Accept: application/json" /
        -d '{"CHAT_ID":2725,"USER_ID":1269,"auth":"**put_access_token_here**"}' /
        https://**put_your_bitrix24_address**/rest/imbot.chat.user.delete
        
try
        {
            const response = await $b24.callMethod(
                'imbot.chat.user.delete',
                {
                    CHAT_ID: 2725,
                    USER_ID: 1269,
                }
            );
            
            const result = response.getData().result;
            console.log('User deleted from chat:', result);
            
            processResult(result);
        }
        catch( error )
        {
            console.error('Error:', error);
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'imbot.chat.user.delete',
                    [
                        'CHAT_ID' => 2725,
                        'USER_ID' => 1269
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error deleting chat user: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'imbot.chat.user.delete',
            {
                CHAT_ID: 2725,
                USER_ID: 1269,
            },
            function (result)
            {
                if (result.error())
                    console.error(result.error());
                else
                    console.dir(result.data());
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'imbot.chat.user.delete',
            [
                'CHAT_ID' => 2725,
                'USER_ID' => 1269
            ]
        );
        
        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.user.delete", b24.Params{
        	"CHAT_ID":   2725,
        	"USER_ID":   1269,
        	"CLIENT_ID": "**put_your_client_id_here**",
        })
        if err != nil {
        	return fmt.Errorf("imbot.chat.user.delete: %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": 1771936672,
                "finish": 1771936672.409352,
                "duration": 0.40935206413269043,
                "processing": 0,
                "date_start": "2026-02-24T15:37:52+01:00",
                "date_finish": "2026-02-24T15:37:52+01:00",
                "operating_reset_at": 1771937272,
                "operating": 0.23420310020446777
            }
        }
        

Returned Data

Name
type

Description

result
boolean

true if the user has been removed from the chat

time
time

Information about the request execution time

Error Handling

HTTP Status: 400, 403

{
            "error": "USER_ID_EMPTY",
            "error_description": "User ID can't be empty"
        }
        

Name
type

Description

error
string

String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only error_description shows the reason

error_description
string

Error message for the developer. Do not show it to the end user without processing

Possible Error Codes

Code

Description

Value

CHAT_ID_EMPTY

Chat ID can't be empty

CHAT_ID not provided

USER_ID_EMPTY

User ID can't be empty

USER_ID not provided

ACCESS_ERROR

Action unavailable

Operation not available for this chat

ACCESS_ERROR

It is forbidden to delete users of this chat

Users cannot be removed from this chat

ACCESS_ERROR

LEAVE_OWNER_FORBIDDEN

Owner of the chat cannot be removed without transferring rights

WRONG_REQUEST

You don't have access or user isn't a member of the chat

No permission to delete or user is not a member of the chat

BOT_ID_ERROR

Bot not found

Chat bot not found

APP_ID_ERROR

Bot was installed by another REST application

Chat bot was 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
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

429

OPERATION_TIME_LIMIT
Method is blocked due to operation time limit

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

401

NO_AUTH_FOUND
Wrong authorization data

The request contains no authorization data: neither an access token nor a webhook code was passed

401

INVALID_REQUEST
Https required

Methods are called over the HTTPS protocol only

401

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support

401

ACCESS_DENIED
REST is available only on commercial plans

The REST API is available only on commercial plans. A webhook receives a different error message — REST is available only by subscription

401

INVALID_CREDENTIALS
Invalid request credentials

No active webhook with the specified user identifier and secret code was found

404

ERROR_METHOD_NOT_FOUND
Method not 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

401

insufficient_scope
The request requires higher privileges than provided by the webhook token

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 provided by the access token

401

expired_token
The access token provided has expired

The access token has expired

401

user_access_error
The user does not have access to the application

The application is installed, but the Bitrix24 administrator has granted access to it only to specific users

403

PORTAL_DELETED
Portal was deleted

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