Add Result to Task tasks.task.result.add
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect the MCP server so the assistant can use the official REST documentation.
Scope:
tasksWho can execute the method: any user with access to the task
The method tasks.task.result.add adds a result to a task.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
Object with result fields |
Parameter fields
|
Name |
Description |
|
taskId* |
Task identifier. The identifier can be obtained when creating a task, getting a task, or using the old method of getting a list of tasks |
|
text* |
Result text |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ parameter to the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/tasks.task.result.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"taskId":51,"text":"Task completed"}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/tasks.task.result.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"taskId":51,"text":"Task completed"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/tasks.task.result.add
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.add',
{
fields: {
taskId: 51,
text: 'Task completed'
}
}
);
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.add',
[
'fields' => [
'taskId' => 51,
'text' => 'Task completed',
],
]
);
$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.add',
{
fields: {
taskId: 51,
text: 'Task completed'
}
},
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.add',
[
'fields' => [
'taskId' => 51,
'text' => 'Task completed',
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"item": {
"id": 17,
"taskId": 51,
"text": "Task completed",
"authorId": 1,
"createdAt": "2026-04-30T10:15:00+02:00",
"updatedAt": null,
"status": "open",
"fileIds": [],
"rights": {
"edit": true,
"remove": true
},
"messageId": null
}
},
"time": {
"start": 1777529700,
"finish": 1777529700.123456,
"duration": 0.123456,
"processing": 0.1,
"date_start": "2026-04-30T10:15:00+02:00",
"date_finish": "2026-04-30T10:15:00+02:00",
"operating_reset_at": 1777530300,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with response data |
|
item |
Task result object (detailed description) |
|
time |
Information about the request execution time |
Object item
|
Name |
Description |
|
id |
Result identifier |
|
taskId |
Task identifier |
|
text |
Result text |
|
authorId |
Result author identifier |
|
createdAt |
Result creation date |
|
updatedAt |
Result update date |
|
status |
Result status. Possible values: |
|
fileIds |
Result file identifiers |
|
rights |
Current user's rights on the result (detailed description) |
|
messageId |
Chat message identifier if the result was created from a message |
Object rights
|
Name |
Description |
|
edit |
Returns |
|
remove |
Returns |
Error Handling
HTTP Status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_DTOVALIDATIONEXCEPTION",
"message": "Validation error",
"validation": [
{
"field": "text",
"message": "The required field \"text\" is not filled"
}
]
}
}
|
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 task identifier in |
|
|
Required field |
Provide the result text in |
|
|
Field |
Do not provide |
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Required field |
Provide the |
|
|
Field |
Provide |
|
|
|
Provide a positive task identifier |
|
|
|
Provide the task identifier in |
|
|
|
Specify the identifier of an existing task |
Access Error
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
HTTP Status: 403
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
Check the user's rights on 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 |
Continue Learning
- Add Result from Task Chat Message tasks.task.result.addfromchatmessage
- Update Task Result tasks.task.result.update
- Get the list of task results tasks.task.result.list
- Delete Task Result tasks.task.result.delete