Send Messages to Bitrix24 imconnector.send.messages
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 is 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 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 name and last_name fields 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 |
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": "Smith",
"name": "John",
"picture": {"url": "https://example.com/u42.png"},
"url": "https://example.com/users/42",
"gender": "male",
"email": "john@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
const payload = {
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: '+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',
},
},
],
};
const response = await $b24.callMethod('imconnector.send.messages', payload);
console.log(response.getData());
$result = $b24Service->core->call(
'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' => '+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: 'Smith',
name: 'John',
picture: { url: 'https://example.com/u42.png' },
url: 'https://example.com/users/42',
gender: 'male',
email: 'john@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' => 'Smith',
'name' => 'John',
'picture' => ['url' => 'https://example.com/u42.png'],
'url' => 'https://example.com/users/42',
'gender' => 'male',
'email' => 'john@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',
],
],
],
]
);
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+01:00",
"date_finish": "2026-03-11T13:53:14+01: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 |
Date of the message 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, such as a 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 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 |
|
|
|
Current authorization type is denied for this method Application context required |
Method called not in the context of an application 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: 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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
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
- 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 Channel Connector for Chat on the Site