Send a Message in Task Chat tasks.task.chat.message.send
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:
tasksWho can execute the method: any user with read access permission for the task or higher
The method tasks.task.chat.message.send sends a new message to the task chat.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
An object with message parameters |
Parameter fields
Required parameters are marked with *
|
Name |
Description |
|
taskId* |
The identifier of the task to which the message should be sent. The task identifier can be obtained when creating a new task or through the old method of getting the task list |
|
text* |
The message text |
Code Examples
How to Use Examples in Documentation
The new API call differs by the addition of the /api/ parameter in the request:
https://{address}/rest/api/{user_id}/{webhook_token}/tasks.task.chat.message.send
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"taskId":51,"text":"Message from external system"}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/tasks.task.chat.message.send
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"taskId":51,"text":"Message from external system"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/tasks.task.chat.message.send
The SDK does not currently support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
try
{
const response = await $b24.callMethod(
'tasks.task.chat.message.send',
{
fields: {
taskId: 51,
text: 'Message from external system',
}
}
);
const result = response.getData().result;
console.log('Message sent with ID:', result);
processResult(result);
}
catch( error )
{
console.error('Error:', error);
}
The SDK does not currently support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'tasks.task.chat.message.send',
[
'fields' =>
[
'taskId' => 51,
'text' => 'Message from external system'
]
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error sending chat message: ' . $e->getMessage();
}
The SDK does not currently support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'tasks.task.chat.message.send',
{
'fields': {
'taskId': 51,
'text': 'Message from external system'
}
},
function(result){
console.info(result.data());
console.log(result);
}
);
The SDK does not currently support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'tasks.task.chat.message.send',
[
'fields' =>
[
'taskId' => 51,
'text' => 'Message from external system'
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"result": true
},
"time": {
"start": 1762257254,
"finish": 1762257254.211513,
"duration": 0.21151304244995117,
"processing": 0,
"date_start": "2025-11-04T15:54:14+01:00",
"date_finish": "2025-11-04T15:54:14+01:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The root element of the response. Contains an object with the key |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_DTOVALIDATIONEXCEPTION",
"message": "Error during object validation",
"validation": [
{
"message": "The required field \u0022taskId\u0022 is not filled",
"field": "taskId"
}
]
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
Description of the error related to the specified field |
Possible Error Codes
Request Validation Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
The required field |
Add the specified field to the request body |
|
|
The field |
Ensure the value passed is of the correct type |
Access Denied Error
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
No access to the task |
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 permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary 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 portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site 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 |