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: task

Who 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.

REST 3.0 has a method with the same name, tasks.task.result.list, with filtering, field selection, and pagination.

Method Parameters

Required parameters are marked with *

Name
type

Description

taskId*
integer

The identifier of the task from which to retrieve results.

You can retrieve it when creating a new task or by using the get task list method

params
object

Additional data in the response. To retrieve it, pass the required key with the value Y, for example, {"WITH_USER_INFO": "Y"}:

  • WITH_USER_INFO — the userInfo object with the name and avatar of the result author
  • WITH_FILE_INFO — the fileInfo object with data on attached files
  • WITH_PARSED_TEXT — the parsedText field with text for the mobile app. With it, the method also returns fileInfo

The method returns all task results in one response and has no pagination.

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 all results of the task in one response, without pagination
          const response = await $b24.actions.v2.call.make<TaskResultItem[]>({
            method: 'tasks.task.result.list',
            params: {
              taskId: 8017,
            },
            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 all results of the task in one response, without pagination
              const response = await $b24.actions.v2.call.make({
                method: 'tasks.task.result.list',
                params: {
                  taskId: 8017,
                },
                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}")
        
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
type

Description

result
array

An array of task results

time
time

Information about the time taken for the request

Element result

Name
type

Description

id
integer

The identifier of the result

taskId
integer

The identifier of the task

commentId
integer

The identifier of the comment marked as a result.

Equals 0 if the result was created by REST 3.0 methods, for example, tasks.task.result.add or tasks.task.result.addfromchatmessage

createdBy
integer

The identifier of the result author

createdAt
string

The date and time the result was created in ISO 8601 format. For a result created from a comment, this is the comment creation date

updatedAt
string

The date and time of the last modification of the result in ISO 8601 format

status
integer

The status of the result. Possible values:

  • 0 — result is open
  • 1 — result is closed

Bitrix24 closes results when the task is completed, and they remain closed after the task is resumed. A result added to an already completed task using tasks.task.result.add remains open

text
string

The text of the result

formattedText
string

The text of the result with formatting

files
array

A list of identifiers of files attached to the result.

Contains an empty array if there are no files in the result

userInfo
object

Data of the result author: the key is the user identifier, and the value is a user object.

The method returns the field if you pass the WITH_USER_INFO: Y key in params

fileInfo
object | array

Data of attached files: the key is the file identifier, and the value is an object with file data. If there are no files, an empty array is returned.

The method returns the field if you pass the WITH_FILE_INFO: Y or WITH_PARSED_TEXT: Y key in params

parsedText
string

Result text prepared for the mobile app.

The method returns the field if you pass the WITH_PARSED_TEXT: Y key in params

User Object in userInfo

Name
type

Description

id
string

User identifier, for example, "1"

name
string

First name

secondName
string

Middle name. null if not filled in

lastName
string

Last name

formattedName
string

First and last name in the format used in Bitrix24

avatar
string

Path to the avatar. If there is no photo, the path to the default image is returned

For a task that does not exist, an administrator receives an empty result array without an error. Any other user receives the Access denied. error in this case.

Error Handling

HTTP Status: 400

{
            "error":"0",
            "error_description":"Access denied."
        }
        

Name
type

Description

error
string

String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only error_description shows the reason

error_description
string

Error message for the developer. Do not show it to the end user without processing

Possible Error Codes

Code

Description

Value

0

Access denied.

The user does not have access to the task

0

Task not found.

0 was passed in the taskId parameter

100

Could not find value for parameter

The required parameter taskId is not passed

100

Invalid value {value} to match with parameter {taskId}. Should be value of type int.

An invalid type value was passed in the taskId parameter. It should be of type integer

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
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

429

OPERATION_TIME_LIMIT
Method is blocked due to operation time limit

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

401

NO_AUTH_FOUND
Wrong authorization data

The request contains no authorization data: neither an access token nor a webhook code was passed

401

INVALID_REQUEST
Https required

Methods are called over the HTTPS protocol only

401

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support

401

ACCESS_DENIED
REST is available only on commercial plans

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 — REST is available only by subscription

401

INVALID_CREDENTIALS
Invalid request credentials

No active webhook with the specified user identifier and secret code was found

404

ERROR_METHOD_NOT_FOUND
Method not 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

401

insufficient_scope
The request requires higher privileges than provided by the webhook token

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 provided by the access token

401

expired_token
The access token provided has expired

The access token has expired

401

user_access_error
The user does not have access to the application

The application is installed, but the Bitrix24 administrator has granted access to it only to specific users

403

PORTAL_DELETED
Portal was deleted

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

Continue Learning