Send Messages to Bitrix24 imconnector.send.messages
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:
imopenlinesWho can execute the method: any user
The method imconnector.send.messages accepts messages from an external system and forwards them to an open line in Bitrix24 via a custom connector.
The method parameters utilize values from the external system: user ID, chat ID, chat link, and its name in the application that registered the connector.
Upon execution, the method returns the chat ID and the open line dialog ID created in Bitrix24.
The method works only in the context of an application.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CONNECTOR* |
The string code of the connector specified in the |
|
LINE* |
The ID of the open line. The ID can be obtained using the methods imopenlines.config.get and imopenlines.config.list.get |
|
MESSAGES* |
An array of messages. Each element of the array represents a single message in the object format with three required blocks: The structure of the object is described in detail below |
MESSAGES Parameter
|
Name |
Description |
|
user |
User data from the external system. The structure of the object is described in detail below |
|
message |
Message data from the external system. The structure of the object is described in detail below |
|
chat |
Chat data from the external system. The structure of the object is described in detail below |
User Object
|
Name |
Description |
|
id* |
User ID in the external system. The value is generated on the side of the external system |
|
last_name |
User's last name |
|
name |
User's first name |
|
picture |
User's avatar. Pass it as an object with the |
|
url |
Link to the user's profile in the external system |
|
gender |
User's gender. Supported values are |
|
email |
User's email |
|
phone |
User's phone |
|
skip_phone_validate |
Disables phone validation before saving in CRM. Acceptable value is |
The fields name and last_name can contain letters, spaces, hyphens, and apostrophes. Numbers and other special characters are not allowed. The maximum length for name and last_name is 25 characters. The language and case can be any.
The skip_phone_validate parameter is recommended to be used only in rare cases when the number fails the built-in validation. This is a workaround to bypass the phone validator's limitations. In a typical scenario, pass the phone without this parameter.
Message Object
|
Name |
Description |
|
id |
Message ID in the external system. The value is generated on the side of the external system |
|
date |
Message time in Unix Timestamp in seconds |
|
text |
Message text. You must pass either the For acceptable formatting, refer to the article Formatting |
|
files |
An array of files. Each file is passed as an array of the form The format of the transmitted file is not restricted. In chat, the attachment can be displayed as an image for types: |
|
disable_crm |
Disables the CRM tracker for the message. Acceptable value is |
|
user_id |
The ID of the manager in Bitrix24. If you pass |
Chat Object
|
Name |
Description |
|
id* |
Chat or channel ID in the external system. It is recommended to pass the same value as in |
|
name |
Chat or channel name. It is recommended to use the value from |
|
url |
Link to the chat or channel in the external system. It is recommended to use the value from |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"CONNECTOR": "myconnector",
"LINE": 107,
"MESSAGES": [
{
"user": {
"id": "ext-user-42",
"last_name": "Ivanov",
"name": "Ivan",
"picture": {"url": "https://example.com/u42.png"},
"url": "https://example.com/users/42",
"gender": "male",
"email": "ivan@example.com",
"phone": "+19990000000",
"skip_phone_validate": "Y"
},
"message": {
"id": "ext-msg-1001",
"date": 1773265993,
"text": "Good afternoon",
"files": [
{"url": "https://example.com/files/spec.pdf", "name": "spec.pdf"}
],
"disable_crm": "Y"
},
"chat": {
"id": "channel-123",
"name": "Support Channel",
"url": "https://example.com/chats/123"
}
}
],
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/imconnector.send.messages
// 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 SendMessagesResult = {
SUCCESS: boolean
DATA: {
RESULT: Array<{
user: string
message: {
id: string
date: object
text: string
files: unknown[]
}
chat: {
id: string
name: string
description: string
}
extra: {
skip_phone_validate?: string
disable_tracker?: string
}
SUCCESS: boolean
ERRORS?: string[]
session?: {
ID: string
CHAT_ID: string
}
}>
}
}
try {
const response = await $b24.actions.v2.call.make<SendMessagesResult>({
method: 'imconnector.send.messages',
params: {
CONNECTOR: 'myconnector',
LINE: 107,
MESSAGES: [
{
user: {
id: 'ext-user-42',
last_name: 'Smith',
name: 'John',
picture: { url: 'https://example.com/u42.png' },
url: 'https://example.com/users/42',
gender: 'male',
email: 'john@example.com',
phone: '+499990000000',
skip_phone_validate: 'Y',
},
message: {
id: 'ext-msg-1001',
date: 1773265993,
text: 'Hello',
files: [{ url: 'https://example.com/files/spec.pdf', name: 'spec.pdf' }],
disable_crm: 'Y',
},
chat: {
id: 'channel-123',
name: 'Support channel',
url: 'https://example.com/chats/123',
},
},
],
},
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('Success:', result.SUCCESS, 'Sessions:', result.DATA.RESULT.map(r => r.session?.CHAT_ID))
}
} 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 sendMessages() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'imconnector.send.messages',
params: {
CONNECTOR: 'myconnector',
LINE: 107,
MESSAGES: [
{
user: {
id: 'ext-user-42',
last_name: 'Smith',
name: 'John',
picture: { url: 'https://example.com/u42.png' },
url: 'https://example.com/users/42',
gender: 'male',
email: 'john@example.com',
phone: '+499990000000',
skip_phone_validate: 'Y',
},
message: {
id: 'ext-msg-1001',
date: 1773265993,
text: 'Hello',
files: [{ url: 'https://example.com/files/spec.pdf', name: 'spec.pdf' }],
disable_crm: 'Y',
},
chat: {
id: 'channel-123',
name: 'Support channel',
url: 'https://example.com/chats/123',
},
},
],
},
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('Success:', result.SUCCESS, 'Sessions:', result.DATA.RESULT.map(r => r.session?.CHAT_ID))
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', sendMessages)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.imconnector.send.messages(
connector="myconnector",
line=107,
messages=[
{
"user": {
"id": "ext-user-42",
"last_name": "Smith",
"name": "John",
"picture": {
"url": "https://example.com/u42.png",
},
"url": "https://example.com/users/42",
"gender": "male",
"email": "john@example.com",
"phone": "+499990000000",
"skip_phone_validate": "Y",
},
"message": {
"id": "ext-msg-1001",
"date": 1773265993,
"text": "Hello",
"files": [
{
"url": "https://example.com/files/spec.pdf",
"name": "spec.pdf",
},
],
"disable_crm": "Y",
},
"chat": {
"id": "channel-123",
"name": "Support channel",
"url": "https://example.com/chats/123",
},
},
],
).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.send.messages',
[
'CONNECTOR' => 'myconnector',
'LINE' => 107,
'MESSAGES' => [
[
'user' => [
'id' => 'ext-user-42',
'last_name' => 'Ivanov',
'name' => 'Ivan',
'picture' => ['url' => 'https://example.com/u42.png'],
'url' => 'https://example.com/users/42',
'gender' => 'male',
'email' => 'ivan@example.com',
'phone' => '+19990000000',
'skip_phone_validate' => 'Y',
],
'message' => [
'id' => 'ext-msg-1001',
'date' => 1773265993,
'text' => 'Good afternoon',
'files' => [
['url' => 'https://example.com/files/spec.pdf', 'name' => 'spec.pdf'],
],
'disable_crm' => 'Y',
],
'chat' => [
'id' => 'channel-123',
'name' => 'Support Channel',
'url' => 'https://example.com/chats/123',
],
],
],
]
);
BX24.callMethod(
'imconnector.send.messages',
{
CONNECTOR: 'myconnector',
LINE: 107,
MESSAGES: [
{
user: {
id: 'ext-user-42',
last_name: 'Ivanov',
name: 'Ivan',
picture: { url: 'https://example.com/u42.png' },
url: 'https://example.com/users/42',
gender: 'male',
email: 'ivan@example.com',
phone: '+19990000000',
skip_phone_validate: 'Y',
},
message: {
id: 'ext-msg-1001',
date: 1773265993,
text: 'Good afternoon',
files: [{ url: 'https://example.com/files/spec.pdf', name: 'spec.pdf' }],
disable_crm: 'Y',
},
chat: {
id: 'channel-123',
name: 'Support Channel',
url: 'https://example.com/chats/123',
},
},
],
},
function(result) {
console.log(result.data());
}
);
$result = CRest::call(
'imconnector.send.messages',
[
'CONNECTOR' => 'myconnector',
'LINE' => 107,
'MESSAGES' => [
[
'user' => [
'id' => 'ext-user-42',
'last_name' => 'Ivanov',
'name' => 'Ivan',
'picture' => ['url' => 'https://example.com/u42.png'],
'url' => 'https://example.com/users/42',
'gender' => 'male',
'email' => 'ivan@example.com',
'phone' => '+19990000000',
'skip_phone_validate' => 'Y',
],
'message' => [
'id' => 'ext-msg-1001',
'date' => 1773265993,
'text' => 'Good afternoon',
'files' => [
['url' => 'https://example.com/files/spec.pdf', 'name' => 'spec.pdf'],
],
'disable_crm' => 'Y',
],
'chat' => [
'id' => 'channel-123',
'name' => 'Support Channel',
'url' => 'https://example.com/chats/123',
],
],
],
]
);
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "imconnector.send.messages", b24.Params{
"CONNECTOR": "myconnector",
"LINE": 107,
"MESSAGES": []b24.Params{
{
"user": b24.Params{
"id": "ext-user-42",
"last_name": "Ivanov",
"name": "Ivan",
"picture": b24.Params{
"url": "https://example.com/u42.png",
},
"url": "https://example.com/users/42",
"gender": "male",
"email": "klaus@example.com",
"phone": "+499990000000",
"skip_phone_validate": "Y",
},
"message": b24.Params{
"id": "ext-msg-1001",
"date": 1773265993,
"text": "Good afternoon",
"files": []b24.Params{
{
"url": "https://example.com/files/spec.pdf",
"name": "spec.pdf",
},
},
"disable_crm": "Y",
},
"chat": b24.Params{
"id": "channel-123",
"name": "Support Channel",
"url": "https://example.com/chats/123",
},
},
},
})
if err != nil {
return fmt.Errorf("imconnector.send.messages: %w", err)
}
var item struct {
Success bool `json:"SUCCESS"`
}
if err := json.Unmarshal(res.Result, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.Success)
Response Handling
HTTP Status: 200
{
"result": {
"SUCCESS": true,
"DATA": {
"RESULT": [
{
"user": "585",
"message": {
"id": "ext-msg-1001",
"date": {},
"text": "Good afternoon",
"files": []
},
"chat": {
"id": "channel-123",
"name": "Support Channel",
"description": "Link to the original post: https://example.com/chats/123"
},
"extra": {
"skip_phone_validate": "Y",
"disable_tracker": "Y"
},
"SUCCESS": true,
"session": {
"ID": "323",
"CHAT_ID": "1767"
}
}
]
}
},
"time": {
"start": 1773265993,
"finish": 1773265994.487149,
"duration": 1.4871490001678467,
"processing": 1,
"date_start": "2026-03-11T13:53:13+02:00",
"date_finish": "2026-03-11T13:53:14+02:00",
"operating_reset_at": 1773266593,
"operating": 1.1916680335998535
}
}
Returned Data
|
Name |
Description |
|
SUCCESS |
Returns |
|
DATA |
Data containing information about the sent messages. The structure of the object is described in detail below |
|
time |
Information about the request execution time |
DATA Object
|
Name |
Description |
|
RESULT |
An array of results for each element of The structure of the element is described in detail below |
RESULT[] Object
|
Name |
Description |
|
user |
Internal user ID in Bitrix24 |
|
message |
Message data after processing (detailed description) |
|
chat |
Chat data after processing (detailed description) |
|
extra |
Additional flags for message processing (detailed description) |
|
SUCCESS |
Indicates successful processing of the current array element |
|
ERRORS |
An array of error texts for the current element, returned when |
|
session |
Information about the open line session, returned if available (detailed description) |
Message Object
|
Name |
Description |
|
id |
External message ID |
|
date |
Message date after processing |
|
text |
Message text |
|
files |
An array of message files |
Chat Object
|
Name |
Description |
|
id |
Chat or channel ID |
|
name |
Chat or channel name |
|
description |
Description of the chat, e.g., link to the original post |
Extra Object
|
Name |
Description |
|
skip_phone_validate |
Indicates phone validation is disabled, returned when the value is |
|
disable_tracker |
Indicates the CRM tracker is disabled, returned when the value is |
Session Object
|
Name |
Description |
|
ID |
Open line session ID |
|
CHAT_ID |
Chat ID in Bitrix24 |
Error Handling
HTTP Status: 400, 403
{
"error": "ERROR_ARGUMENT",
"error_description": "Argument 'MESSAGES' is null or empty"
}
|
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 |
The method was called outside the application context OAuth |
|
|
|
Argument 'CONNECTOR' is null or empty |
|
|
|
|
Argument 'LINE' is null or empty |
|
|
|
|
Argument 'MESSAGES' is null or empty |
|
|
|
|
The value of an argument 'MESSAGES' must be of type array |
|
|
|
|
The MESSAGES parameter must be an array of messages (arrays) |
Elements of |
|
|
|
The incorrect structure of a message inside MESSAGES parameter |
The |
|
|
|
The line with this ID is inactive or does not exist |
An inactive |
|
|
|
Failed to find a suitable provider for the connector |
Unable to initialize the provider for the connector |
|
|
|
No valid command specified |
Unable to determine the command for processing incoming data |
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 |
|
|
|
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 — |
|
|
|
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
- Get the List of Connectors imconnector.list
- Unregister the Connector imconnector.unregister
- 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
- How to Create an Open Channels Connector for Website Chat