Change Chat Owner via imbot.chat.setOwner

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.setOwner.

The method imbot.chat.setOwner changes the owner of 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 imbot.chat.get method.
USER_ID* `integer`	The identifier of the new chat owner. You can get the user identifier using the user.get and user.search methods.
BOT_ID `integer`	The identifier of the chat bot. You can obtain the bot identifier using the imbot.bot.list method. If this parameter is not provided, the method searches for the first bot registered by the current application.
CLIENT_ID `string`	A technical parameter for scenarios without `clientId` in authorization. If provided, it is used as `custom{CLIENT_ID}` to identify the application.

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"CHAT_ID":2727,"USER_ID":1269}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imbot.chat.setOwner

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"CHAT_ID":2727,"USER_ID":1269,"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/imbot.chat.setOwner

try
        {
            const response = await $b24.callMethod(
                'imbot.chat.setOwner',
                {
                    CHAT_ID: 2727,
                    USER_ID: 1269,
                }
            );
            
            const result = response.getData().result;
            console.log('Chat owner set:', result);
            
            processResult(result);
        }
        catch( error )
        {
            console.error('Error:', error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'imbot.chat.setOwner',
                    [
                        'CHAT_ID' => 2727,
                        'USER_ID' => 1269
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error setting chat owner: ' . $e->getMessage();
        }

BX24.callMethod(
            'imbot.chat.setOwner',
            {
                CHAT_ID: 2727,
                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.setOwner',
            [
                'CHAT_ID' => 2727,
                '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.setOwner", b24.Params{
        	"CHAT_ID": 2727,
        	"USER_ID": 1269,
        })
        if err != nil {
        	return fmt.Errorf("imbot.chat.setOwner: %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": 1771952858,
                "finish": 1771952858.856461,
                "duration": 0.8564610481262207,
                "processing": 0,
                "date_start": "2026-02-24T17:07:38+01:00",
                "date_finish": "2026-02-24T17:07:38+01:00",
                "operating_reset_at": 1771953458,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `boolean`	`true` if the chat owner has been changed.
time `time`	Information about the execution time of the request.

Error Handling

HTTP Status: 400, 403

{
            "error": "CHAT_ID_EMPTY",
            "error_description": "Chat 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	Cannot change the owner of a group chat.
`WRONG_REQUEST`	Change owner can only owner and user must be member in chat	Only the current owner can change the owner, and the user must be a participant in the chat.
`BOT_ID_ERROR`	Bot not found	Chat bot not found.
`APP_ID_ERROR`	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 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

Was the article helpful?

Assign or Remove Chat Administrator Rights

Update Chat Title

Change Chat Owner via imbot.chat.setOwner

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning