Transfer a dialog to another operator or to another line imopenlines.operator.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:
imopenlinesWho can execute the method: any user with dialog permissions
The method imopenlines.operator.transfer transfers a dialog to another operator or to the queue of another open line.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CHAT_ID* |
Identifier of the open line chat. The identifier can be obtained using the imopenlines.session.open or imopenlines.dialog.get methods. |
|
Universal parameter for transferring the dialog. Allowed formats: The user identifier can be obtained using the user.get and user.search methods, and the queue identifier can be obtained using the imopenlines.config.list.get method. |
|
|
USER_ID |
Identifier of the operator to whom the dialog should be transferred. The user identifier can be obtained using the user.get and user.search methods. |
|
QUEUE_ID |
Identifier of the line to which the dialog should be transferred.
|
It is recommended to pass only one parameter: TRANSFER_ID, 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":2043,"USER_ID":15}' \
https://your-domain.bitrix24.com/rest/1/webhook_key/imopenlines.operator.transfer.json
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"CHAT_ID":2043,"USER_ID":15,"auth":"<access_token>"}' \
https://your-domain.bitrix24.com/rest/imopenlines.operator.transfer.json
try {
const response = await $b24.callMethod(
'imopenlines.operator.transfer',
{
CHAT_ID: 2043,
USER_ID: 15,
}
);
const { result } = response.getData();
console.log(result);
} catch (error) {
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'imopenlines.operator.transfer',
[
'CHAT_ID' => 2043,
'USER_ID' => 15,
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error transferring dialog: ' . $exception->getMessage();
}
BX24.callMethod(
'imopenlines.operator.transfer',
{
CHAT_ID: 2043,
USER_ID: 15,
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'imopenlines.operator.transfer',
[
'CHAT_ID' => 2043,
'USER_ID' => 15,
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Success: ' . print_r($result['result'], true);
}
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1773663032,
"finish": 1773663032.493037,
"duration": 0.49303698539733887,
"processing": 0,
"date_start": "2026-03-16T15:10:32+02:00",
"date_finish": "2026-03-16T15:10:32+02:00",
"operating_reset_at": 1773663632,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Returns |
|
time |
Information about the execution time of the request. |
Error Handling
HTTP Status: 400
{
"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 |
Empty or invalid |
|
|
|
QUEUE ID can't be empty |
Empty or invalid |
|
|
|
Queue ID or User ID can't be empty |
|
|
|
|
You cannot redirect to this operator |
The target operator or line is unavailable for transferring the current dialog. |
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
- Take the dialog for yourself imopenlines.operator.answer
- Finish Your Dialogue imopenlines.operator.finish
- Finish Another Operator's Dialog imopenlines.operator.another.finish
- Skip Dialog imopenlines.operator.skip
- Mark a conversation as "spam" imopenlines.operator.spam