Get Chat by User Code imopenlines.session.open

Scope: imopenlines

Who can execute the method: any user with access permission to the dialogue

The method imopenlines.session.open returns the chat ID of the open line based on the user code USER_CODE.

Method Parameters

Required parameters are marked with *

Name
type

Description

USER_CODE*
string

String code of the user for the external system channel.

Code format: <connector>|<LINE_ID>|<CONNECTOR_CHAT_ID>|<CONNECTOR_USER_ID>, where:

<connector> — connector identifier: livechat, telegram, and others
<LINE_ID> — identifier of the open line
<CONNECTOR_CHAT_ID> — chat identifier in the channel
<CONNECTOR_USER_ID> — user identifier in the channel

The value can be obtained using the method imopenlines.dialog.get from the entity_id field or the method imopenlines.session.history.get from result.chat.<chatId>.entityId

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"USER_CODE":"livechat|22|1761|587"}' \
          https://your-domain.bitrix24.com/rest/1/webhook_key/imopenlines.session.open.json

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"USER_CODE":"livechat|22|1761|587","auth":"<access_token>"}' \
          https://your-domain.bitrix24.com/rest/imopenlines.session.open.json

try {
            const response = await $b24.callMethod(
                'imopenlines.session.open',
                {
                    USER_CODE: 'livechat|22|1761|587',
                }
            );
        
            const { result } = response.getData();
            console.log(result);
        } catch (error) {
            console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'imopenlines.session.open',
                    [
                        'USER_CODE' => 'livechat|22|1761|587',
                    ]
                );
        
            $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 opening chat: ' . $exception->getMessage();
        }

BX24.callMethod(
            'imopenlines.session.open',
            {
                USER_CODE: 'livechat|22|1761|587',
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error().ex);
                } else {
                    console.log(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'imopenlines.session.open',
            [
                'USER_CODE' => 'livechat|22|1761|587',
            ]
        );
        
        if (!empty($result['error'])) {
            echo 'Error: ' . $result['error_description'];
        } else {
            echo 'Success: ' . print_r($result['result'], true);
        }

Response Handling

HTTP Status: 200

{
            "result": {
                "chatId": "1763"
            },
            "time": {
                "start": 1773666416,
                "finish": 1773666416.279787,
                "duration": 0.2797870635986328,
                "processing": 0,
                "date_start": "2026-03-16T16:06:56+01:00",
                "date_finish": "2026-03-16T16:06:56+01:00",
                "operating_reset_at": 1773667016,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `object`	Root object of the response (detailed description)
time `time`	Information about the request execution time

Result Object

Name `type`	Description
chatId `integer`	Identifier of the open line chat

Error Handling

HTTP Status: 400

{
            "error": "ACCESS_DENIED",
            "error_description": "You cannot open this conversation because you do not have sufficient permissions"
        }

Name `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `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
`400`	`ACCESS_DENIED`	You cannot open this conversation because you do not have sufficient permissions	No access to the chat with the specified `USER_CODE`

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not allowed to be called using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The methods must be called using the HTTPS protocol
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is available only on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user whose access token or webhook was used to call the method lacks permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	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
`500`	`PORTAL_DELETED` Portal was deleted	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

Remove a User from the CRM Object Chat

Start a new dialog

Get Chat by User Code imopenlines.session.open

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Result ObjectResult Object

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning