Update Open Channel imopenlines.config.update
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:
imopenlinesWho can execute the method: user with permission to modify open channels
The method imopenlines.config.update updates an open channel.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CONFIG_ID* |
Identifier of the open channel. You can obtain the identifier of the open channel when creating an open channel or by using the method to get the list of open channels |
|
PARAMS |
Object with settings for the update. The set of fields corresponds to the PARAMS parameter of the |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"CONFIG_ID": 15,
"PARAMS": {
"LINE_NAME": "Online Store Support Line (VIP)",
"QUEUE": [
{
"ENTITY_TYPE": "user",
"ENTITY_ID": "1"
},
{
"ENTITY_TYPE": "user",
"ENTITY_ID": "15"
},
{
"ENTITY_TYPE": "user",
"ENTITY_ID": "23"
}
],
"QUEUE_TYPE": "strictly",
"QUEUE_TIME": 45,
"NO_ANSWER_TIME": 120,
"WELCOME_MESSAGE": "Y",
"WELCOME_MESSAGE_TEXT": "Hello! We will respond within a couple of minutes",
"WORKTIME_ENABLE": "Y",
"WORKTIME_FROM": "09:00",
"WORKTIME_TO": "21:00",
"WORKTIME_TIMEZONE": "Europe/Berlin"
}
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imopenlines.config.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"CONFIG_ID": 15,
"PARAMS": {
"LINE_NAME": "Online Store Support Line (VIP)",
"QUEUE": [
{
"ENTITY_TYPE": "user",
"ENTITY_ID": "1"
},
{
"ENTITY_TYPE": "user",
"ENTITY_ID": "15"
},
{
"ENTITY_TYPE": "user",
"ENTITY_ID": "23"
}
],
"QUEUE_TYPE": "strictly",
"QUEUE_TIME": 45,
"NO_ANSWER_TIME": 120,
"WELCOME_MESSAGE": "Y",
"WELCOME_MESSAGE_TEXT": "Hello! We will respond within a couple of minutes",
"WORKTIME_ENABLE": "Y",
"WORKTIME_FROM": "09:00",
"WORKTIME_TO": "21:00",
"WORKTIME_TIMEZONE": "Europe/Berlin"
},
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/imopenlines.config.update
try
{
const response = await $b24.callMethod(
'imopenlines.config.update',
{
CONFIG_ID: 15,
PARAMS: {
LINE_NAME: 'Online Store Support Line (VIP)',
QUEUE: [
{
ENTITY_TYPE: 'user',
ENTITY_ID: '1'
},
{
ENTITY_TYPE: 'user',
ENTITY_ID: '15'
},
{
ENTITY_TYPE: 'user',
ENTITY_ID: '23'
}
],
QUEUE_TYPE: 'strictly',
QUEUE_TIME: 45,
NO_ANSWER_TIME: 120,
WELCOME_MESSAGE: 'Y',
WELCOME_MESSAGE_TEXT: 'Hello! We will respond within a couple of minutes',
WORKTIME_ENABLE: 'Y',
WORKTIME_FROM: '09:00',
WORKTIME_TO: '21:00',
WORKTIME_TIMEZONE: 'Europe/Berlin'
}
}
);
const result = response.getData().result;
console.log(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'imopenlines.config.update',
[
'CONFIG_ID' => 15,
'PARAMS' => [
'LINE_NAME' => 'Online Store Support Line (VIP)',
'QUEUE' => [
[
'ENTITY_TYPE' => 'user',
'ENTITY_ID' => '1',
],
[
'ENTITY_TYPE' => 'user',
'ENTITY_ID' => '15',
],
[
'ENTITY_TYPE' => 'user',
'ENTITY_ID' => '23',
],
],
'QUEUE_TYPE' => 'strictly',
'QUEUE_TIME' => 45,
'NO_ANSWER_TIME' => 120,
'WELCOME_MESSAGE' => 'Y',
'WELCOME_MESSAGE_TEXT' => 'Hello! We will respond within a couple of minutes',
'WORKTIME_ENABLE' => 'Y',
'WORKTIME_FROM' => '09:00',
'WORKTIME_TO' => '21:00',
'WORKTIME_TIMEZONE' => 'Europe/Berlin',
],
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
BX24.callMethod(
'imopenlines.config.update',
{
CONFIG_ID: 15,
PARAMS: {
LINE_NAME: 'Online Store Support Line (VIP)',
QUEUE: [
{
ENTITY_TYPE: 'user',
ENTITY_ID: '1'
},
{
ENTITY_TYPE: 'user',
ENTITY_ID: '15'
},
{
ENTITY_TYPE: 'user',
ENTITY_ID: '23'
}
],
QUEUE_TYPE: 'strictly',
QUEUE_TIME: 45,
NO_ANSWER_TIME: 120,
WELCOME_MESSAGE: 'Y',
WELCOME_MESSAGE_TEXT: 'Hello! We will respond within a couple of minutes',
WORKTIME_ENABLE: 'Y',
WORKTIME_FROM: '09:00',
WORKTIME_TO: '21:00',
WORKTIME_TIMEZONE: 'Europe/Berlin'
}
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imopenlines.config.update',
[
'CONFIG_ID' => 15,
'PARAMS' => [
'LINE_NAME' => 'Online Store Support Line (VIP)',
'QUEUE' => [
[
'ENTITY_TYPE' => 'user',
'ENTITY_ID' => '1',
],
[
'ENTITY_TYPE' => 'user',
'ENTITY_ID' => '15',
],
[
'ENTITY_TYPE' => 'user',
'ENTITY_ID' => '23',
],
],
'QUEUE_TYPE' => 'strictly',
'QUEUE_TIME' => 45,
'NO_ANSWER_TIME' => 120,
'WELCOME_MESSAGE' => 'Y',
'WELCOME_MESSAGE_TEXT' => 'Hello! We will respond within a couple of minutes',
'WORKTIME_ENABLE' => 'Y',
'WORKTIME_FROM' => '09:00',
'WORKTIME_TO' => '21:00',
'WORKTIME_TIMEZONE' => 'Europe/Berlin',
],
]
);
print_r($result);
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1773667094,
"finish": 1773667094.239236,
"duration": 0.23923611640930176,
"processing": 0,
"date_start": "2026-03-16T16:18:14+01:00",
"date_finish": "2026-03-16T16:18:14+01:00",
"operating_reset_at": 1773667694,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Returns:
|
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error": "CONFIG_ID_EMPTY",
"error_description": "Config ID can't be empty"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Config ID can't be empty |
The |
|
|
|
Permission denied |
Insufficient rights to modify the channel |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site 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
- Open Channels: Overview of Methods and Events
- Add Open Channel imopenlines.config.add
- Get Open Line by ID imopenlines.config.get
- Get the List of Open Channels imopenlines.config.list.get
- Delete Open Channel imopenlines.config.delete
- Get Link to Public Page of Open Channels imopenlines.config.path.get