Get a List of Tasks tasks.task.list
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
tasksWho can execute the method: any user
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 |
Description |
|
select |
List of fields to be returned in the response. If Field names for |
|
filter |
Task filtering conditions in the format:
In REST 3.0, filtering by the |
|
order |
Sorting of results in the Available values:
Available fields for sorting: See the field descriptions in the Task object block By default, tasks are sorted by |
|
pagination |
Pagination parameters:
|
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>
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>';
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 |
Description |
|
result |
Object with response data |
|
items |
Array of task objects |
|
items[] |
Task object. The set of fields depends on the See the field descriptions in the Task object block |
|
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 |
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
Access Errors
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Access denied |
Check user permissions and scope |
Filtering Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
In DTO |
Use only the |
Sorting Errors
Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDORDEREXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Unable to recognize sorting parameter |
Provide direction |
Pagination Errors
Error Code: BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Unable to recognize pagination parameter |
Provide numeric values. |
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 |