Transfer a Dialogue to an Operator or Queue using imopenlines.bot.session.transfer
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:
imopenlines,imbotWho can execute the method: application user with a registered chat bot
The method imopenlines.bot.session.transfer transfers a dialogue from the chat bot in an open line to a specified operator or queue.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CHAT_ID* |
The identifier of the chat whose dialogue needs to be transferred. The chat identifier can be obtained using the methods imopenlines.dialog.get or imopenlines.crm.chat.get |
|
USER_ID |
The identifier of the employee to whom the dialogue should be transferred. The user identifier can be obtained using the methods user.get or user.search |
|
QUEUE_ID |
The identifier of the queue to which the dialogue should be transferred. Pass the value of the The |
|
Universal transfer destination parameter. Allowed formats: The user identifier can be obtained using the methods user.get and user.search, and the queue identifier can be obtained using the method imopenlines.config.list.get |
|
|
LEAVE |
Flag indicating the presence of the chat bot in the dialogue after the transfer. Allowed values:
By default, |
|
CLIENT_ID |
This parameter is mandatory only for webhooks. Pass:
|
It is recommended to pass only one destination parameter: USER_ID, QUEUE_ID, or TRANSFER_ID. If multiple parameters are passed simultaneously, the method uses the following priority: USER_ID -> QUEUE_ID -> TRANSFER_ID. When passing TRANSFER_ID, the method converts it to USER_ID or QUEUE_ID.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"CHAT_ID":112,"USER_ID":12,"LEAVE":"N","CLIENT_ID":"**put_your_client_id_or_bot_token_here**"}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/imopenlines.bot.session.transfer
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"CHAT_ID":112,"USER_ID":12,"LEAVE":"N","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/imopenlines.bot.session.transfer
try {
const response = await $b24.callMethod('imopenlines.bot.session.transfer', {
CHAT_ID: 112,
USER_ID: 12,
LEAVE: 'N',
});
const { result } = response.getData();
console.log('Session transferred:', result);
} catch (error) {
console.error('Error transferring session:', error);
}
try {
$response = $b24Service
->core
->call(
'imopenlines.bot.session.transfer',
[
'CHAT_ID' => 112,
'USER_ID' => 12,
'LEAVE' => 'N',
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Session transferred: ' . var_export($result, true);
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error transferring session: ' . $exception->getMessage();
}
BX24.callMethod(
'imopenlines.bot.session.transfer',
{
CHAT_ID: 112,
USER_ID: 12,
LEAVE: 'N',
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imopenlines.bot.session.transfer',
[
'CHAT_ID' => 112,
'USER_ID' => 12,
'LEAVE' => 'N',
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Session transferred: ' . var_export($result['result'], true);
}
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1728626400.456,
"finish": 1728626400.539,
"duration": 0.083,
"processing": 0.031,
"date_start": "2024-10-11T10:00:00+02:00",
"date_finish": "2024-10-11T10:00:00+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Contains |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400, 403
{
"error": "TRANSFER_ID_EMPTY",
"error_description": "Queue ID or User 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 |
|
|
|
Chat ID can't be empty |
|
|
|
|
User ID can't be empty |
|
|
|
|
QUEUE ID can't be empty |
|
|
|
|
Queue ID or User ID can't be empty |
Neither |
|
|
|
Bot not found |
No registered chat bot found in the application |
|
|
|
You cannot redirect to this operator |
Transfer to the specified operator or queue is not available |
|
|
|
Access for this method not allowed by session authorization |
Method called with session authorization, which is prohibited for this method |
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
- Send an Automatic Message in the imopenlines.bot.session.message.send Dialog
- Switch Dialog to Free Operator imopenlines.bot.session.operator
- Finish Dialog imopenlines.bot.session.finish