Get the List of Connectors imconnector.list
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: a user with permission to modify Open Channels connectors
The method imconnector.list returns a list of all connectors registered in Bitrix24.
The method works only in the context of an application.
Method Parameters
No parameters.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/imconnector.list
// 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
// Shape of the payload returned in result (match the "response handling" section of the page)
type ConnectorListResult = Record<string, string>
try {
const response = await $b24.actions.v2.call.make<ConnectorListResult>({
method: 'imconnector.list',
params: {},
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('Connectors:', 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 listConnectors() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'imconnector.list',
params: {},
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('Connectors:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', listConnectors)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.imconnector.list().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}")
$result = $b24Service->core->call(
'imconnector.list',
[]
);
BX24.callMethod(
'imconnector.list',
{},
function(result) {
console.log(result.data());
}
);
$result = CRest::call(
'imconnector.list',
[]
);
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "imconnector.list", nil, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("imconnector.list: %w", err)
}
var item struct {
Livechat string `json:"livechat"`
Telegrambot string `json:"telegrambot"`
Network string `json:"network"`
Myconnector string `json:"myconnector"`
}
if err := json.Unmarshal(res.Result, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.Livechat, item.Telegrambot)
Response Handling
HTTP Status: 200
{
"result": {
"livechat": "Live Chat",
"telegrambot": "Telegram",
"network": "Bitrix24.Network",
"myconnector": "My Connector"
},
"time": {
"start": 1738065600.11,
"finish": 1738065600.17,
"duration": 0.06,
"processing": 0.03,
"date_start": "2025-01-28T12:00:00+00:00",
"date_finish": "2025-01-28T12:00:00+00:00"
}
}
Returned Data
|
Name |
Description |
|
result |
An object of the form |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400, 403
{
"error": "ACCESS_DENIED",
"error_description": "You don't have access to this action"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Current authorization type is denied for this method. Application context required |
Method called outside of the application OAuth context |
|
|
|
The ImOpenLines module is not installed |
The |
|
|
|
You don't have access to this action |
The user does not have permission to modify connectors |
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 |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
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 |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was 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 |
|
|
|
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 |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
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
- Register the Connector imconnector.register
- Activate Connector imconnector.activate
- Get the Status of the Connector imconnector.status
- Set Connector Settings imconnector.connector.data.set
- Unregister the Connector imconnector.unregister
- Send Messages to Bitrix24 imconnector.send.messages
- Update Sent Messages with imconnector.update.messages
- Delete Sent Messages imconnector.delete.messages
- Update Status "Delivered" imconnector.send.status.delivery
- Set a New Chat Name imconnector.chat.name.set