Add Result from Task Chat Message tasks.task.result.addfromchatmessage
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect the MCP server so that the assistant uses the official REST documentation.
Scope:
tasksWho can execute the method: any user with access to the task
The method tasks.task.result.addfromchatmessage creates a task result from a task chat message.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
Object with message fields |
Parameter fields
|
Name |
Description |
|
messageId* |
Identifier of the task chat message. The identifier can be obtained when sending a message using the tasks.task.chat.message.send method |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ parameter in the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/tasks.task.result.addfromchatmessage
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"messageId":335}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/tasks.task.result.addfromchatmessage
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"messageId":335},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/tasks.task.result.addfromchatmessage
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try
{
const response = await $b24.callMethod(
'tasks.task.result.addfromchatmessage',
{
fields: {
messageId: 335
}
}
);
const result = response.getData().result;
console.info(result.item);
}
catch( error )
{
console.error(error);
}
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'tasks.task.result.addfromchatmessage',
[
'fields' => [
'messageId' => 335,
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
}
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'tasks.task.result.addfromchatmessage',
{
fields: {
messageId: 335
}
},
function(result){
console.info(result.data());
}
);
The SDK does not currently support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'tasks.task.result.addfromchatmessage',
[
'fields' => [
'messageId' => 335,
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"item": {
"id": 18,
"taskId": 51,
"text": "Task work completed",
"authorId": 1,
"createdAt": "2026-04-30T10:25:00+02:00",
"updatedAt": null,
"status": "open",
"fileIds": [],
"rights": {
"edit": true,
"remove": true
},
"messageId": 335
}
},
"time": {
"start": 1777530300,
"finish": 1777530300.123456,
"duration": 0.123456,
"processing": 0.1,
"date_start": "2026-04-30T10:25:00+02:00",
"date_finish": "2026-04-30T10:25:00+02:00",
"operating_reset_at": 1777530900,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with response data |
|
item |
Object of the task result. The fields of the object match the response of the method tasks.task.result.add |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
"message": "Error during request object validation",
"validation": [
{
"field": "fields",
"message": "Required field `fields` is missing"
}
]
}
}
|
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_DTOVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Required field |
Provide the message identifier in |
|
|
Field |
Do not pass |
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Required field |
Provide a |
|
|
Field |
Provide |
|
|
|
Specify the message identifier from the task chat |
|
|
|
Check that the task associated with the chat exists |
Error Code: BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unknown field for entity |
Only pass the |
Access Error
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
HTTP Status: 403
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
Check user permissions to create a result from the chat message |
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 |
Continue Learning
- Add Result to Task tasks.task.result.add
- Update Task Result tasks.task.result.update
- Get the list of task results tasks.task.result.list
- Delete Task Result tasks.task.result.delete