Add Result to Task tasks.task.result.add
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:
tasksWho can execute the method: any user with access to the task
This method belongs to REST 3.0. The call specifics and response format of the new API version are described in the REST 3.0 overview.
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/ segment to the request URL:
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
// 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, ISODate } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type TaskResultAddResult = {
item: {
id: number,
taskId: number,
text: string,
authorId: number,
createdAt: ISODate,
updatedAt: ISODate | null,
status: string,
fileIds: number[],
rights: {
edit: boolean,
remove: boolean,
},
messageId: number | null,
},
}
try {
const response = await $b24.actions.v3.call.make<TaskResultAddResult>({
method: 'tasks.task.result.add',
params: {
fields: {
taskId: 51,
text: 'Task work has been completed',
},
},
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(result.item.id, result.item.taskId, result.item.status)
}
} 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 addTaskResult() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v3.call.make({
method: 'tasks.task.result.add',
params: {
fields: {
taskId: 51,
text: 'Task work has been completed',
},
},
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(result.item.id, result.item.taskId, result.item.status)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', addTaskResult)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
fields = {
"taskId": 51,
"text": "The work on the task is completed",
}
try:
bitrix_response = client.tasks.task.result.add(
fields=fields,
).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}")
SDKs do not yet 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());
}
SDKs do not yet 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());
}
);
SDKs do not yet 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>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "tasks.task.result.add", b24.Params{
"fields": b24.Params{
"taskId": 51,
"text": "Task completed",
},
})
if err != nil {
return fmt.Errorf("tasks.task.result.add: %w", err)
}
// The method wraps the response in an object with the "item" key.
raw, ok := b24.Unwrap(res.Result, "item")
if !ok {
return fmt.Errorf("no item key in the response")
}
var item struct {
ID b24.ID `json:"id"`
TaskID b24.ID `json:"taskId"`
Text string `json:"text"`
AuthorID b24.ID `json:"authorId"`
CreatedAt string `json:"createdAt"`
Status string `json:"status"`
}
if err := json.Unmarshal(raw, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.ID, item.TaskID)
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: 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 |