Transfer a Dialogue to an Operator or Queue using imopenlines.bot.session.transfer

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: imopenlines, imbot

Who 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
type

Description

CHAT_ID*
integer

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
integer

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
integer

The identifier of the queue to which the dialogue should be transferred.

Pass the value of the ID field from the response of the method imopenlines.config.list.get.

The QUEUE field from the response of imopenlines.config.list.get contains USER_ID of the employees in the queue and is not suitable as QUEUE_ID

TRANSFER_ID
string|integer

Universal transfer destination parameter.

Allowed formats: USER_ID of the employee or the string queue<QUEUE_ID>.

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
boolean

Flag indicating the presence of the chat bot in the dialogue after the transfer.

Allowed values:

  • Y — the bot leaves the chat immediately
  • N — the bot stays until the transfer is confirmed

By default, N is used

CLIENT_ID
string

This parameter is mandatory only for webhooks.

Pass:

  • the same CLIENT_ID that was specified when registering the chat bot using the method imbot.register
  • or the value of the botToken parameter passed during the registration of the chat bot using the method imbot.v2.Bot.register

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
        
// 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
        
        try {
          const response = await $b24.actions.v2.call.make<boolean>({
            method: 'imopenlines.bot.session.transfer',
            params: {
              CHAT_ID: 112,
              USER_ID: 12,
              LEAVE: 'N',
            },
            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('Session transferred:', result)
          }
        } 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 transferSession() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'imopenlines.bot.session.transfer',
                params: {
                  CHAT_ID: 112,
                  USER_ID: 12,
                  LEAVE: 'N',
                },
                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('Session transferred:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', transferSession)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.imopenlines.bot.session.transfer(
                chat_id=112,
                user_id=12,
                leave=False,
            ).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 {
            $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);
        }
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "imopenlines.bot.session.transfer", b24.Params{
        	"CHAT_ID":   112,
        	"USER_ID":   12,
        	"LEAVE":     "N",
        	"CLIENT_ID": "**put_your_client_id_or_bot_token_here**",
        })
        if err != nil {
        	return fmt.Errorf("imopenlines.bot.session.transfer: %w", err)
        }
        
        var ok bool
        if err := json.Unmarshal(res.Result, &ok); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        fmt.Println("done:", ok)
        

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
type

Description

result
boolean

Contains true if the dialogue was successfully transferred

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

Value

400

CHAT_ID_EMPTY

Chat ID can't be empty

CHAT_ID not provided or value is <= 0

400

USER_ID_EMPTY

User ID can't be empty

USER_ID provided with an empty value or value <= 0

400

QUEUE_ID_EMPTY

QUEUE ID can't be empty

QUEUE_ID provided with an empty value or value <= 0

400

TRANSFER_ID_EMPTY

Queue ID or User ID can't be empty

Neither USER_ID nor QUEUE_ID provided, and TRANSFER_ID not specified

400

BOT_ID_ERROR

Bot not found

No registered chat bot found in the application

400

OPERATOR_WRONG

You cannot redirect to this operator

Transfer to the specified operator or queue is not available

403

WRONG_AUTH_TYPE

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