Get Task List v 3.0 tasks.task.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: tasks

Who can execute the method: any user

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 tasks.task.list method returns a list of tasks based on the specified conditions.

Access to the data depends on permissions:

  • An administrator sees all tasks
  • A manager sees the tasks of their employees
  • Others see only the tasks available to them

Method Parameters

Required parameters are marked with *

Name
type

Description

select
array

List of fields to be returned in the response. If select is not specified, the method returns only the id of the task.

Field names for select match the keys of the task object from the Task object block

filter
array

Task filtering conditions in the format:

  • ["field", "operator", value]
  • ["field", value], default operator =

In REST 3.0, filtering by the id field is supported for tasks.

More details about filtering in REST 3.0

order
object

Sorting of results in the { "field": "value" } format.

Available values:

  • ASC — ascending
  • DESC — descending

Available fields for sorting: id, title, creatorId, created, responsibleId, deadline, startPlan, endPlan, groupId, priority, status, started, estimatedTime, changed, closed, activity, mark, allowsChangeDeadline, allowsTimeTracking.

See the field descriptions in the Task object block

By default, tasks are sorted by id in ascending order

pagination
object

Pagination parameters:

  • page — page number
  • limit — number of tasks per page, default 50, maximum 1000
  • offset — task offset. If page and limit are provided, the offset is calculated automatically

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

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"select":["id","title","responsibleId","deadline","status"],"filter":[["id",">",1000]],"order":{"id":"ASC"},"pagination":{"page":1,"limit":20,"offset":0}}' \
        https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/tasks.task.list
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"select":["id","title","responsibleId","deadline","status"],"filter":[["id",">",1000]],"order":{"id":"ASC"},"pagination":{"page":1,"limit":20,"offset":0},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/api/tasks.task.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
        
        type TaskListItem = {
          id: number
          title: string
          responsibleId: number
          deadline: ISODate | null
          status: string
        }
        
        // Shape of the payload returned in result (match the "response handling" section of the page)
        type TaskListResult = {
          items: TaskListItem[]
        }
        
        try {
          // tasks.task.list returns a single page. For the whole result set
          // use a list helper: $b24.actions.v3.callList.make() returns every record as one
          // array, $b24.actions.v3.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 + `pagination` variant when sort matters.
          const response = await $b24.actions.v3.call.make<TaskListResult>({
            method: 'tasks.task.list',
            params: {
              select: [
                'id',
                'title',
                'responsibleId',
                'deadline',
                'status',
              ],
              filter: [
                ['id', '>', 1000],
              ],
              order: {
                id: 'ASC',
              },
              pagination: {
                page: 1,
                limit: 20,
                offset: 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('Tasks:', result.items)
          }
        } 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 listTasks() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v3.call.make({
                method: 'tasks.task.list',
                params: {
                  select: [
                    'id',
                    'title',
                    'responsibleId',
                    'deadline',
                    'status',
                  ],
                  filter: [
                    ['id', '>', 1000],
                  ],
                  order: {
                    id: 'ASC',
                  },
                  pagination: {
                    page: 1,
                    limit: 20,
                    offset: 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('Tasks:', result.items)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', listTasks)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        select = [
            "id",
            "title",
            "responsibleId",
            "deadline",
            "status",
        ]
        
        filter = [
            [
                "id",
                ">",
                1000,
            ],
        ]
        
        order = {
            "id": "ASC",
        }
        
        pagination = {
            "page": 1,
            "limit": 20,
            "offset": 0,
        }
        
        try:
            bitrix_response = client.tasks.task.list(
                select=select,
                filter=filter,
                order=order,
                pagination=pagination,
            ).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.list',
                    [
                        'select' => [
                            'id',
                            'title',
                            'responsibleId',
                            'deadline',
                            'status',
                        ],
                        'filter' => [
                            ['id', '>', 1000],
                        ],
                        'order' => [
                            'id' => 'ASC',
                        ],
                        'pagination' => [
                            'page' => 1,
                            'limit' => 20,
                            'offset' => 0,
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error fetching tasks: ' . $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.list',
            {
                select: [
                    'id',
                    'title',
                    'responsibleId',
                    'deadline',
                    'status'
                ],
                filter: [
                    ['id', '>', 1000]
                ],
                order: {
                    id: 'ASC'
                },
                pagination: {
                    page: 1,
                    limit: 20,
                    offset: 0
                }
            },
            function(result){
                console.info(result.data());
                console.log(result);
            }
        );
        

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.list',
            [
                'select' => [
                    'id',
                    'title',
                    'responsibleId',
                    'deadline',
                    'status'
                ],
                'filter' => [
                    ['id', '>', 1000]
                ],
                'order' => [
                    'id' => 'ASC'
                ],
                'pagination' => [
                    'page' => 1,
                    'limit' => 20,
                    'offset' => 0
                ]
            ]
        );
        
        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.list", b24.Params{
        	"select": []string{"id", "title", "responsibleId", "deadline", "status"},
        	"filter": []any{
        		[]any{"id", ">", 1000},
        	},
        	"order": b24.Params{
        		"id": "ASC",
        	},
        	"pagination": b24.Params{
        		"page":   1,
        		"limit":  20,
        		"offset": 0,
        	},
        }, b24.WithIdempotent())
        if err != nil {
        	return fmt.Errorf("tasks.task.list: %w", err)
        }
        
        // The method wraps the response in an object with the "items" key.
        raw, ok := b24.Unwrap(res.Result, "items")
        if !ok {
        	return fmt.Errorf("no items key in the response")
        }
        
        var items []struct {
        	ID            b24.ID `json:"id"`
        	Title         string `json:"title"`
        	ResponsibleID b24.ID `json:"responsibleId"`
        	Deadline      string `json:"deadline"`
        	Status        string `json:"status"`
        }
        if err := json.Unmarshal(raw, &items); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        for _, it := range items {
        	fmt.Println(it.ID)
        }
        

Response Handling

HTTP status: 200

{
            "result": {
                "items": [
                    {
                        "id": 3835,
                        "title": "Collect feedback",
                        "responsibleId": 93,
                        "deadline": "2026-12-25T23:00:00+03:00",
                        "status": "pending"
                    },
                    {
                        "id": 3836,
                        "title": "Prepare the contract",
                        "responsibleId": 29,
                        "deadline": null,
                        "status": "in_progress"
                    },
                    {
                        "id": 3837,
                        "title": "Approve the estimate",
                        "responsibleId": 171,
                        "deadline": "2025-12-27T18:00:00+03:00",
                        "status": "completed"
                    }
                ]
            },
            "time": {
                "start": 1765445133,
                "finish": 1765445134.139558,
                "duration": 1.1395580768585205,
                "processing": 1,
                "date_start": "2026-06-17T12:25:33+03:00",
                "date_finish": "2026-06-17T12:25:34+03:00",
                "operating_reset_at": 1765445733,
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
object

Object with response data

items
array

Array of task objects

items[]
object

Task object. The set of fields depends on the select parameter. If select is not specified, the method returns only id.

See the field descriptions in the Task object block

time
time

Information about the request execution time

Error Handling

HTTP status: 400

{
            "error": {
                "code": "BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION",
                "message": "Unable to recognize the pagination parameter `{\"limit\":\"abc\"}`"
            }
        }
        

Name
type

Description

error.code
string

String error code. Use it to identify the type of exception

error.message
string

Text description of the error

error.validation
array

Array with error details. Present only in data validation errors BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION

error.validation[].field
string

Name of the field where the validation error occurred

error.validation[].message
string

Description of the error related to the specified field

Possible Error Codes

Access Errors

Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION

Field

Error description

How to Fix

-

Access denied

Check user permissions and scope tasks

Filtering Errors

Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION

Field

Error description

How to Fix

#FIELD#

In DTO TaskDto, the #FIELD# field requires the Filterable attribute for such a request

Use only the id field in the filter

Sorting Errors

Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDORDEREXCEPTION

Field

Error description

How to Fix

order

Unable to recognize sorting parameter #ORDER#

Provide direction ASC or DESC and a field available for sorting

Pagination Errors

Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION

Field

Error description

How to Fix

limit
offset
page

Unable to recognize pagination parameter #PAGE#

Provide numeric values. limit must not be equal to 0

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