Get the list of task results tasks.task.result.list
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect the MCP server so that 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.list returns a list of task results.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
order |
An object for sorting the list of results in the format The sorting direction can take the following values:
The field for sorting can take the following values:
|
|
filter* |
An array of conditions for filtering the list of results. Be sure to pass the condition for Each condition is an array with the field name, operator, and value. For the operator Condition formats:
Available filter operators:
The filterable field can take the following values:
|
|
select |
An array of fields to select. If the parameter is not passed, the method will return the default fields. The field can take the following values:
|
|
pagination |
An object for managing pagination. Pagination parameters:
|
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the parameter /api/ in the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/tasks.task.result.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"filter":[["taskId",51]],"select":["id","taskId","text","authorId","createdAt","status","messageId"],"order":{"createdAt":"DESC"},"pagination":{"limit":10,"offset":0}}' \
https://**put_your_bitrix24_address**/rest/api/**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 '{"filter":[["taskId",51]],"select":["id","taskId","text","authorId","createdAt","status","messageId"],"order":{"createdAt":"DESC"},"pagination":{"limit":10,"offset":0},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/tasks.task.result.list
The SDK does not yet 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.result.list',
{
filter: [
['taskId', 51]
],
select: ['id', 'taskId', 'text', 'authorId', 'createdAt', 'status', 'messageId'],
order: {
createdAt: 'DESC'
},
pagination: {
limit: 10,
offset: 0
}
}
);
const result = response.getData().result;
console.info(result.items);
}
catch( error )
{
console.error(error);
}
The SDK does not yet support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'tasks.task.result.list',
[
'filter' => [
['taskId', 51],
],
'select' => ['id', 'taskId', 'text', 'authorId', 'createdAt', 'status', 'messageId'],
'order' => [
'createdAt' => 'DESC',
],
'pagination' => [
'limit' => 10,
'offset' => 0,
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
}
The SDK does not yet support calls to the address /rest/api/. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'tasks.task.result.list',
{
filter: [
['taskId', 51]
],
select: ['id', 'taskId', 'text', 'authorId', 'createdAt', 'status', 'messageId'],
order: {
createdAt: 'DESC'
},
pagination: {
limit: 10,
offset: 0
}
},
function(result){
console.info(result.data());
}
);
The SDK does not yet 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.result.list',
[
'filter' => [
['taskId', 51],
],
'select' => ['id', 'taskId', 'text', 'authorId', 'createdAt', 'status', 'messageId'],
'order' => [
'createdAt' => 'DESC',
],
'pagination' => [
'limit' => 10,
'offset' => 0,
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": {
"items": [
{
"id": 17,
"taskId": 51,
"text": "Task work completed",
"authorId": 1,
"createdAt": "2026-04-30T10:15:00+02:00",
"status": "open",
"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 |
An object with response data (detailed description) |
|
time |
Information about the request execution time |
Result Object
|
Name |
Description |
|
items |
An array of task results. The fields of the elements depend on the |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
"message": "Error validating the request object",
"validation": [
{
"field": "filter",
"message": "The field value cannot be empty"
}
]
}
}
|
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 field value cannot be empty |
Pass the filter as an array of conditions |
|
|
The |
Pass |
Error code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTFILTERVALIDATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
A filter for the required field |
Pass a condition for |
Error code: BITRIX_REST_V3_EXCEPTION_INVALIDFILTEREXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unable to recognize the filter expression |
Pass the filter as an array of conditions |
Error code: BITRIX_REST_V3_EXCEPTION_UNKNOWNFILTEROPERATOREXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unknown filter operator |
Use operators |
Error code: BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unable to recognize the pagination parameter |
Pass |
Error code: BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unknown field |
Pass only fields from the list: |
Error code: BITRIX_REST_V3_EXCEPTION_INVALIDORDEREXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Unable to recognize the sorting expression |
Pass the sorting direction |
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 to read 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 to Task tasks.task.result.add
- Add Result from Task Chat Message tasks.task.result.addfromchatmessage
- Update Task Result tasks.task.result.update
- Delete Task Result tasks.task.result.delete