Get the List of Open Channels imopenlines.config.list.get
Scope:
imopenlinesWho can execute the method: any user
The method imopenlines.config.list.get retrieves a list of open channels.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
PARAMS |
Selection parameters (detailed description) |
|
OPTIONS |
Additional options (detailed description) |
PARAMS Parameter
|
Name |
Description |
|
select |
An array containing the list of fields to be selected. You can specify fields from the Result Array Element table. The fields |
|
order |
An object for sorting the list of open channels in the format The sorting direction can take the following values:
For |
|
filter |
An object for filtering the list of open channels in the format For |
|
limit |
The number of items per page. Default: |
|
offset |
Offset for pagination. Default: |
OPTIONS Parameter
|
Name |
Description |
|
QUEUE |
Return the operator queue. Possible values:
|
|
CONFIG_QUEUE |
Return the line queue. Each queue element contains
|
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"PARAMS": {
"select": ["ID", "LINE_NAME", "ACTIVE"],
"order": {"ID": "ASC"},
"filter": {"ACTIVE": "Y"},
"limit": 50,
"offset": 0
},
"OPTIONS": {
"QUEUE": "Y",
"CONFIG_QUEUE": "Y"
}
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imopenlines.config.list.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"PARAMS": {
"select": ["ID", "LINE_NAME", "ACTIVE"],
"order": {"ID": "ASC"},
"filter": {"ACTIVE": "Y"},
"limit": 50,
"offset": 0
},
"OPTIONS": {
"QUEUE": "Y",
"CONFIG_QUEUE": "Y"
},
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/imopenlines.config.list.get
try
{
const response = await $b24.callMethod(
'imopenlines.config.list.get',
{
PARAMS: {
select: ['ID', 'LINE_NAME', 'ACTIVE'],
order: { ID: 'ASC' },
filter: { ACTIVE: 'Y' },
limit: 50,
offset: 0
},
OPTIONS: {
QUEUE: 'Y',
CONFIG_QUEUE: 'Y'
}
}
);
const result = response.getData().result;
console.log(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'imopenlines.config.list.get',
[
'PARAMS' => [
'select' => ['ID', 'LINE_NAME', 'ACTIVE'],
'order' => ['ID' => 'ASC'],
'filter' => ['ACTIVE' => 'Y'],
'limit' => 50,
'offset' => 0,
],
'OPTIONS' => [
'QUEUE' => 'Y',
'CONFIG_QUEUE' => 'Y',
],
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
BX24.callMethod(
'imopenlines.config.list.get',
{
PARAMS: {
select: ['ID', 'LINE_NAME', 'ACTIVE'],
order: { ID: 'ASC' },
filter: { ACTIVE: 'Y' },
limit: 50,
offset: 0
},
OPTIONS: {
QUEUE: 'Y',
CONFIG_QUEUE: 'Y'
}
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imopenlines.config.list.get',
[
'PARAMS' => [
'select' => ['ID', 'LINE_NAME', 'ACTIVE'],
'order' => ['ID' => 'ASC'],
'filter' => ['ACTIVE' => 'Y'],
'limit' => 50,
'offset' => 0,
],
'OPTIONS' => [
'QUEUE' => 'Y',
'CONFIG_QUEUE' => 'Y',
],
]
);
print_r($result);
Response Handling
HTTP Status: 200
{
"result": [
{
"ID": "15",
"LINE_NAME": "VIP Support Line",
"ACTIVE": "Y",
"QUEUE": [101, 205],
"QUEUE_USERS_FIELDS": {
"101": {
"USER_NAME": "John Smith",
"USER_WORK_POSITION": "Operator",
"USER_AVATAR": "https://example.bitrix24.com/upload/main/a1b/avatar.jpg",
"USER_AVATAR_ID": 312
},
"205": {
"USER_NAME": "Anna Johnson",
"USER_WORK_POSITION": null,
"USER_AVATAR": "",
"USER_AVATAR_ID": null
}
},
"CONFIG_QUEUE": [
{
"ENTITY_ID": "10",
"ENTITY_TYPE": "department"
}
]
},
{
"ID": "16",
"LINE_NAME": "Sales Line",
"ACTIVE": "Y",
"QUEUE": [101],
"QUEUE_USERS_FIELDS": {
"101": {
"USER_NAME": "John Smith",
"USER_WORK_POSITION": "Operator",
"USER_AVATAR": "https://example.bitrix24.com/upload/main/a1b/avatar.jpg",
"USER_AVATAR_ID": 312
}
},
"CONFIG_QUEUE": []
}
],
"time": {
"start": 1741688574.50636,
"finish": 1741688574.701981,
"duration": 0.19562101364135742,
"processing": 0.09473705291748047,
"date_start": "2025-03-11T10:29:34+01:00",
"date_finish": "2025-03-11T10:29:34+01:00",
"operating_reset_at": 1741689174,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
List of open channels (detailed description) |
|
time |
Information about the request execution time |
Result Array Element
|
Name |
Description |
|
ID |
Identifier of the open channel |
|
LINE_NAME |
Name of the open channel |
|
ACTIVE |
Activity status of the line. Possible values:
|
|
CRM |
CRM interaction status. Possible values:
|
|
CRM_CREATE |
Scenario for creating a CRM element |
|
CRM_CREATE_SECOND |
Additional mode for creating a CRM element |
|
CRM_CREATE_THIRD |
Additional mode for creating a CRM element. Possible values:
|
|
CRM_FORWARD |
Status of forwarding to CRM. Possible values:
|
|
CRM_CHAT_TRACKER |
Status of sending the dialog to the CRM tracker. Possible values:
|
|
CRM_TRANSFER_CHANGE |
Status of changing the responsible person during transfer. Possible values:
|
|
CRM_SOURCE |
Mode of working with the source in CRM |
|
QUEUE_TYPE |
Mode of distributing requests |
|
QUEUE_TIME |
Time to transfer the request to the next operator |
|
NO_ANSWER_TIME |
Time until the no-answer scenario is triggered |
|
CHECK_AVAILABLE |
Check the availability of operators. Possible values:
|
|
WATCH_TYPING |
Show text being typed by the operator. Possible values:
|
|
WELCOME_BOT_ENABLE |
Status of using the welcome bot. Possible values:
|
|
WELCOME_MESSAGE |
Status of the welcome message. Possible values:
|
|
WELCOME_MESSAGE_TEXT |
Text of the welcome message |
|
VOTE_MESSAGE |
Status of the feedback request. Possible values:
|
|
VOTE_TIME_LIMIT |
Time limit for feedback |
|
VOTE_BEFORE_FINISH |
Request feedback before the dialog ends. Possible values:
|
|
VOTE_CLOSING_DELAY |
Use a delay for closing after feedback. Possible values:
|
|
VOTE_MESSAGE_1_TEXT |
Text of the first feedback scenario |
|
VOTE_MESSAGE_1_LIKE |
Text for positive feedback in the first scenario |
|
VOTE_MESSAGE_1_DISLIKE |
Text for negative feedback in the first scenario |
|
VOTE_MESSAGE_2_TEXT |
Text of the second feedback scenario |
|
VOTE_MESSAGE_2_LIKE |
Text for positive feedback in the second scenario |
|
VOTE_MESSAGE_2_DISLIKE |
Text for negative feedback in the second scenario |
|
AGREEMENT_MESSAGE |
Status of displaying the agreement message. Possible values:
|
|
AGREEMENT_ID |
Identifier of the agreement |
|
CATEGORY_ENABLE |
Status of using categories. Possible values:
|
|
CATEGORY_ID |
Identifier of the category |
|
WELCOME_BOT_JOIN |
Mode of connecting the welcome bot |
|
WELCOME_BOT_ID |
Identifier of the welcome bot |
|
WELCOME_BOT_TIME |
Time to wait for the welcome bot connection |
|
WELCOME_BOT_LEFT |
Mode of disconnecting the welcome bot |
|
NO_ANSWER_RULE |
Scenario for no response from the operator |
|
NO_ANSWER_FORM_ID |
Identifier of the no-answer scenario form |
|
NO_ANSWER_BOT_ID |
Identifier of the no-answer scenario bot |
|
NO_ANSWER_TEXT |
Text message for no response |
|
WORKTIME_ENABLE |
Status of considering working hours. Possible values:
|
|
WORKTIME_FROM |
Start of working hours |
|
WORKTIME_TO |
End of working hours |
|
WORKTIME_TIMEZONE |
Working hours time zone |
|
WORKTIME_HOLIDAYS |
Array of holidays |
|
WORKTIME_DAYOFF |
Array of days off |
|
WORKTIME_DAYOFF_RULE |
Scenario for handling requests during non-working hours |
|
WORKTIME_DAYOFF_FORM_ID |
Identifier of the non-working hours scenario form |
|
WORKTIME_DAYOFF_BOT_ID |
Identifier of the non-working hours scenario bot |
|
WORKTIME_DAYOFF_TEXT |
Text message during non-working hours |
|
CLOSE_RULE |
Scenario for closing the dialog |
|
CLOSE_FORM_ID |
Identifier of the closing form |
|
CLOSE_BOT_ID |
Identifier of the closing bot |
|
CLOSE_TEXT |
Text message upon closing |
|
FULL_CLOSE_TIME |
Time for full session closure |
|
AUTO_CLOSE_RULE |
Auto-closing scenario |
|
AUTO_CLOSE_FORM_ID |
Identifier of the auto-closing form |
|
AUTO_CLOSE_BOT_ID |
Identifier of the auto-closing bot |
|
AUTO_CLOSE_TIME |
Time until auto-closing |
|
AUTO_CLOSE_TEXT |
Text for auto-closing |
|
AUTO_EXPIRE_TIME |
Time until activity expiration |
|
DATE_CREATE |
Date of setting creation in serialized form |
|
DATE_MODIFY |
Date of setting modification in serialized form |
|
MODIFY_USER_ID |
Identifier of the user who modified the settings |
|
TEMPORARY |
Status of temporary line. Possible values:
|
|
XML_ID |
External identifier. Possible values:
|
|
LANGUAGE_ID |
Language of the line |
|
QUICK_ANSWERS_IBLOCK_ID |
Identifier of the quick answers information block |
|
SESSION_PRIORITY |
Session priority |
|
TYPE_MAX_CHAT |
Mode of limiting active dialogs per operator |
|
MAX_CHAT |
Maximum active dialogs per operator |
|
OPERATOR_DATA |
Mode of displaying operator data |
|
QUEUE |
Identifiers of operators in the queue. Field is returned when |
|
QUEUE_USERS_FIELDS |
Additional fields of queue users. Key — user identifier, value — description of queue fields (detailed description). Field is returned when |
|
CONFIG_QUEUE |
Ordered list of line queue objects (detailed description). Field is returned when |
|
DEFAULT_OPERATOR_DATA |
Set of default operator display fields |
|
KPI_FIRST_ANSWER_TIME |
Standard time for the first response |
|
KPI_FIRST_ANSWER_ALERT |
Status of notification for overdue first response. Possible values:
|
|
KPI_FIRST_ANSWER_LIST |
List of recipients for first response notifications. Possible values:
|
|
KPI_FIRST_ANSWER_TEXT |
Text of notification for overdue first response |
|
KPI_FURTHER_ANSWER_TIME |
Standard time for subsequent responses |
|
KPI_FURTHER_ANSWER_ALERT |
Status of notification for overdue subsequent responses. Possible values:
|
|
KPI_FURTHER_ANSWER_LIST |
List of recipients for subsequent response notifications. Possible values:
|
|
KPI_FURTHER_ANSWER_TEXT |
Text of notification for overdue subsequent responses |
|
KPI_CHECK_OPERATOR_ACTIVITY |
Status of monitoring operator activity. Possible values:
|
|
SEND_NOTIFICATION_EMPTY_QUEUE |
Status of notifications for an empty queue. Possible values:
|
|
USE_WELCOME_FORM |
Status of using the welcome form. Possible values:
|
|
WELCOME_FORM_ID |
Identifier of the welcome form |
|
WELCOME_FORM_DELAY |
Status of delay in showing the welcome form. Possible values:
|
|
SEND_WELCOME_EACH_SESSION |
Show welcome message in each session. Possible values:
|
|
CONFIRM_CLOSE |
Require confirmation for closing. Possible values:
|
|
IGNORE_WELCOME_FORM_RESPONSIBLE |
Ignore the responsible person in the welcome form. Possible values:
|
QUEUE_USERS_FIELDS Object
|
Name |
Description |
|
USER_NAME |
User's name. Possible values:
|
|
USER_WORK_POSITION |
User's position. Possible values:
|
|
USER_AVATAR |
Link to avatar. Possible values:
|
|
USER_AVATAR_ID |
Identifier of the avatar file |
CONFIG_QUEUE Object
|
Name |
Description |
|
ENTITY_ID |
Identifier of the object in the queue |
|
ENTITY_TYPE |
Type of the object in the queue |
Error Handling
HTTP Status: 400
{
"error": "INVALID_FORMAT",
"error_description": "A wrong format for the PARAMS field 'filter' is passed"
}
|
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 |
|
|
|
A wrong format for the PARAMS field 'select' is passed |
The |
|
|
|
A wrong format for the PARAMS field 'order' is passed |
The |
|
|
|
A wrong format for the PARAMS field 'filter' is passed |
The |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Open Lines in Bitrix24
- Add Open Channel imopenlines.config.add
- Update Open Channel imopenlines.config.update
- Get Open Line by ID imopenlines.config.get
- Delete Open Channel imopenlines.config.delete
- Get Link to Public Page of Open Channels imopenlines.config.path.get