Get the List of Task Results tasks.task.result.list
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:
taskWho can execute the method: any user with access to the task
The method tasks.task.result.list retrieves a list of results associated with a task.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
taskId* |
The identifier of the task from which to retrieve results. The task identifier can be obtained when creating a new task or by using the get task list method |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"taskId":8017}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/tasks.task.result.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"taskId":8017,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/tasks.task.result.list
// 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 one task result item returned in result[]
type TaskResultItem = {
id: number
taskId: number
commentId: number
createdBy: number
createdAt: ISODate | null
updatedAt: ISODate | null
status: number
text: string
formattedText: string
files: number[]
}
try {
// tasks.task.result.list returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
const response = await $b24.actions.v2.call.make<TaskResultItem[]>({
method: 'tasks.task.result.list',
params: {
taskId: 8017,
start: 0,
},
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('Task results count:', result.length, 'First result:', result[0]?.id, result[0]?.text)
}
} 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 fetchTaskResultList() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
// tasks.task.result.list returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
const response = await $b24.actions.v2.call.make({
method: 'tasks.task.result.list',
params: {
taskId: 8017,
start: 0,
},
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('Task results count:', result.length, 'First result:', result[0]?.id, result[0]?.text)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', fetchTaskResultList)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.tasks.task.result.list(
task_id=8017,
).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}")
Example as_list
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.tasks.task.result.list(
task_id=8017,
).as_list().response
result = bitrix_response.result
for item in result:
print(item)
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}")
Example as_list_fast
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.tasks.task.result.list(
task_id=8017,
).as_list_fast(descending=True).response
result = bitrix_response.result
for item in result:
print(item)
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}")
try {
$response = $b24Service
->core
->call(
'tasks.task.result.list',
[
'taskId' => 8017
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error listing task results: ' . $e->getMessage();
}
BX24.callMethod(
'tasks.task.result.list',
{
"taskId": 8017
},
function(result){
console.info(result.data());
console.log(result);
}
);
require_once('crest.php');
$result = CRest::call(
'tasks.task.result.list',
[
'taskId' => 8017
]
);
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.list", b24.Params{
"taskId": 8017,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("tasks.task.result.list: %w", err)
}
var items []struct {
ID b24.ID `json:"id"`
TaskID b24.ID `json:"taskId"`
CommentID b24.ID `json:"commentId"`
CreatedBy int `json:"createdBy"`
CreatedAt string `json:"createdAt"`
UpdatedAt string `json:"updatedAt"`
}
if err := json.Unmarshal(res.Result, &items); err != nil {
return fmt.Errorf("parse response: %w", err)
}
for _, it := range items {
fmt.Println(it.ID, it.TaskID)
}
// Total and Next are filled in by list methods; for a full
// list traversal, use client.Core().Pages and Scan.
if res.Total != nil {
fmt.Println("total:", *res.Total)
}
Response Handling
HTTP Status: 200
{
"result": [
{
"id": 23,
"taskId": 8017,
"commentId": 3197,
"createdBy": 503,
"createdAt": "2025-07-15T14:30:00+02:00",
"updatedAt": "2025-08-19T16:45:48+02:00",
"status": 0,
"text": "Client signed the documents",
"formattedText": "Client signed the documents",
"files": []
},
{
"id": 21,
"taskId": 8017,
"commentId": 3199,
"createdBy": 503,
"createdAt": "2025-07-13T14:30:00+02:00",
"updatedAt": "2025-08-19T16:45:56+02:00",
"status": 0,
"text": "Sent documents to the client. The client promises to respond on [B]Monday[\/B].",
"formattedText": "Sent documents to the client. The client promises to respond on \u003Cb\u003EMonday\u003C\/b\u003E.",
"files": [1055,1057,1059,1061,1063]
}
],
"time": {
"start": 1755611166.509052,
"finish": 1755611166.542696,
"duration": 0.03364396095275879,
"processing": 0.00906991958618164,
"date_start": "2025-08-19T16:46:06+02:00",
"date_finish": "2025-08-19T16:46:06+02:00",
"operating_reset_at": 1755611766,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
An array of objects, where each object describes a task result |
|
id |
The identifier of the result |
|
taskId |
The identifier of the task |
|
commentId |
The identifier of the comment marked as a result |
|
createdBy |
The identifier of the user who marked the result |
|
createdAt |
The date and time the result was marked in ISO 8601 format |
|
updatedAt |
The date and time of the last modification of the result in ISO 8601 format |
|
status |
The status of the result. Possible values:
The result becomes closed after the task is completed and retains this status after the task is resumed. Only new results in an unfinished task will be open. A comment with an open result cannot be added again to the result. If the result is closed, adding is possible |
|
text |
The text of the result |
|
formattedText |
The text of the result with formatting |
|
files |
A list of identifiers of files attached to the result. Contains an empty array if there are no files in the comment |
|
time |
Information about the time taken for the request |
Error Handling
HTTP Status: 400
{
"error":"100",
"error_description":"Invalid value {value} to match with parameter {commentId}. Should be value of type int."
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
Value |
|
|
Access denied. |
The user does not have access to the task or a task with such |
|
|
Invalid value {value} to match with parameter {commentId}. Should be value of type int. |
An invalid type value was passed in the |
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 |