Set a New Chat Name imconnector.chat.name.set

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

Who can execute the method: any user

The method imconnector.chat.name.set sets a new name for the chat.

The method works only in the context of the application.

Method Parameters

Required parameters are marked with *

Name
type

Description

CONNECTOR*
string

The string code of the connector specified in the ID parameter when calling imconnector.register

LINE*
integer

Identifier of the Open Channel

The identifier can be obtained using the methods imopenlines.config.get and imopenlines.config.list.get

CHAT_ID*
string

Identifier of the chat in the external system

NAME*
string

New name for the chat

USER_ID
string

User identifier. This parameter is mandatory only for connectors without group chats from the external side. For such a connector, the CHAT_GROUP parameter in the imconnector.register method must be set to false

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"CONNECTOR":"connector","LINE":105,"CHAT_ID":"47e007b1-ee15-43db-bcba-1c26e5884d3f","NAME":"New Dialog Name","auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/imconnector.chat.name.set
        
// This snippet is an ES module: top-level await requires type="module" or a bundler.
        // $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
        import { Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        // Shape of the payload returned in result (match the "response handling" section of the page)
        type ChatNameSetResult = {
          SUCCESS: boolean
          DATA: {
            RESULT: Record<string, unknown>
          }
        }
        
        try {
          const response = await $b24.actions.v2.call.make<ChatNameSetResult>({
            method: 'imconnector.chat.name.set',
            params: {
              CONNECTOR: 'connector',
              LINE: 105,
              CHAT_ID: '47e007b1-ee15-43db-bcba-1c26e5884d3f',
              NAME: 'New dialog name',
            },
            requestId: Text.getUuidRfc4122()
          })
        
          // The payload is available only on a successful response
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('SUCCESS:', result.SUCCESS, 'DATA:', result.DATA)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }
        
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
        <script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function setChatName() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'imconnector.chat.name.set',
                params: {
                  CONNECTOR: 'connector',
                  LINE: 105,
                  CHAT_ID: '47e007b1-ee15-43db-bcba-1c26e5884d3f',
                  NAME: 'New dialog name',
                },
                requestId: B24Js.Text.getUuidRfc4122()
              })
        
              // The payload is available only on a successful response
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('SUCCESS:', result.SUCCESS, 'DATA:', result.DATA)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', setChatName)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.imconnector.chat.name.set(
                connector="connector",
                line=105,
                chat_id="47e007b1-ee15-43db-bcba-1c26e5884d3f",
                name="New dialog name",
            ).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 {
            $params = [
                'CONNECTOR' => 'connector',
                'LINE'      => 105,
                'CHAT_ID'   => '47e007b1-ee15-43db-bcba-1c26e5884d3f',
                'NAME'      => 'New Dialog Name',
            ];
        
            $response = $b24Service
                ->core
                ->call(
                    'imconnector.chat.name.set',
                    $params
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result->error()) {
                echo 'Error: ' . $result->error();
            } else {
                echo 'Success: ' . $result->data();
            }
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error setting chat name: ' . $e->getMessage();
        }
        
var params = {
            CONNECTOR: 'connector',
            LINE: 105,
            CHAT_ID: '47e007b1-ee15-43db-bcba-1c26e5884d3f',
            NAME: 'New Dialog Name'
        };
        BX24.callMethod(
            'imconnector.chat.name.set',
            params,
            function(result)
            {
                if(result.error())
                    alert("Error: " + result.error());
                else
                    alert("Success: " + result.data());
            }
        );
        
require_once('crest.php');
        
        $params = [
            'CONNECTOR' => 'connector',
            'LINE' => 105,
            'CHAT_ID' => '47e007b1-ee15-43db-bcba-1c26e5884d3f',
            'NAME' => 'New Dialog Name'
        ];
        
        $result = CRest::call(
            'imconnector.chat.name.set',
            $params
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "imconnector.chat.name.set", b24.Params{
        	"CONNECTOR": "connector",
        	"LINE":      105,
        	"CHAT_ID":   "47e007b1-ee15-43db-bcba-1c26e5884d3f",
        	"NAME":      "New Dialog Name",
        })
        if err != nil {
        	return fmt.Errorf("imconnector.chat.name.set: %w", err)
        }
        
        // The response arrives as json.RawMessage — unmarshal it
        // into a struct matching the response shape shown below on this page.
        fmt.Printf("%s\n", res.Result)
        

Response Handling

HTTP Status: 200

{
            "result": {
                "SUCCESS": true,
                "DATA": {
                    "RESULT": {}
                }
            },
            "time": {
                "start": 1732110908.525962,
                "finish": 1732110908.879113,
                "duration": 0.3531508445739746,
                "processing": 0.07694888114929199,
                "date_start": "2024-11-20T15:55:08+02:00",
                "date_finish": "2024-11-20T15:55:08+02:00"
            }
        }
        

Returned Data

Name
type

Description

result
object

Result of setting the chat name (detailed description)

time
time

Information about the request execution time

result Object

Name
type

Description

SUCCESS
boolean

Returns true when the new chat name is successfully set

DATA
object

Contains the RESULT object with parameters of the new chat name

Error Handling

HTTP Status: 400

{
            "error": "NOT_ACTIVE_LINE",
            "error_description": "The line with this ID is inactive or does not exist"
        }
        

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

Status

Code

Description

400

NOT_ACTIVE_LINE

The line with this ID is inactive or does not exist

400

IMCONNECTOR_NO_CORRECT_PROVIDER

Unable to find a suitable provider for the connector

400

ERROR_ARGUMENT

Required parameters NAME, CHAT_ID, USER_ID, CONNECTOR, or LINE are missing

400

CHAT_RENAMING_FAILED

Failed to rename 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
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

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 — 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