Get a List of Time Tracking Records task.elapseditem.getlist

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

The method task.elapseditem.getlist returns a list of time tracking records for a task.

Method Parameters

Name
type

Description

taskId
integer

Task identifier.

The task identifier can be obtained when creating a new task or by using the get task list method

order
object

Object for sorting the result (detailed description provided below)

filter
object

Object for filtering the result (detailed description provided below)

select
array

Array of fields of records that will be returned by the method. You can specify only the fields you need. If the array contains the value "*", all available fields will be returned.

By default, all fields of the main request table will be returned

params
object

Object for call options. The element is an object NAV_PARAMS of the form {'call option': 'value' [, ...]} (detailed description provided below) in structure

Warning

The method accepts parameters positionally. Follow the order from the table: taskId, order, filter, select, params. If you pass order, filter, select, and params as named fields of a single object, the request will fail.

Note

Features of manually adding information about work time that was actually performed several days ago. In this case, the values of some fields change:

  • CREATED_DATE — start date
  • DATE_START — record creation date
  • DATE_STOP — record end date

order Parameter

Name
type

Description

ID
string

Identifier of the time tracking record. Can take values:

  • asc — ascending
  • desc — descending

USER_ID
string

Identifier of the user on behalf of whom the time tracking record was made. Can take values:

  • asc — ascending
  • desc — descending

MINUTES
string

Time spent, in minutes. Can take values:

  • asc — ascending
  • desc — descending

SECONDS
string

Time spent, in seconds. Can take values:

  • asc — ascending
  • desc — descending

CREATED_DATE
string

Record creation date. Can take values:

  • asc — ascending
  • desc — descending

DATE_START
string

Start date. Can take values:

  • asc — ascending
  • desc — descending

DATE_STOP
string

End date. Can take values:

  • asc — ascending
  • desc — descending

filter Parameter

Name
type

Description

ID
integer

Identifier of the time tracking record

USER_ID
integer

Identifier of the user on behalf of whom the time tracking record was made

CREATED_DATE
datetime

Record creation date

Note

Before the name of the filtered field, you can specify the type of filtering:

  • "!" — not equal
  • "<" — less than
  • "<=" — less than or equal
  • ">" — greater than
  • ">=" — greater than or equal

'filter values' — a single value or an array

Name
type

Description

nPageSize
integer

Number of items per page. To limit the load on pagination, a limit of 50 records is imposed

iNumPage
integer

Page number in pagination

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '[3839,{"ID":"asc"},{"USER_ID":1},["ID","TASK_ID","USER_ID","SECONDS","MINUTES","COMMENT_TEXT","CREATED_DATE"],{"NAV_PARAMS":{"nPageSize":2,"iNumPage":1}}]' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/task.elapseditem.getlist
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '[3839,{"ID":"asc"},{"USER_ID":1},["ID","TASK_ID","USER_ID","SECONDS","MINUTES","COMMENT_TEXT","CREATED_DATE"],{"NAV_PARAMS":{"nPageSize":2,"iNumPage":1}}]' \
        https://**put_your_bitrix24_address**/rest/task.elapseditem.getlist?auth=**put_access_token_here**
        
// 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 ElapsedItem = {
          ID: string
          TASK_ID: string
          USER_ID: string
          COMMENT_TEXT: string
          SECONDS: string
          MINUTES: string
          SOURCE: string
          CREATED_DATE: ISODate | null
          DATE_START: ISODate | null
          DATE_STOP: ISODate | null
        }
        
        try {
          // task.elapseditem.getlist 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 variant when sort matters.
          const response = await $b24.actions.v2.call.make<ElapsedItem[]>({
            method: 'task.elapseditem.getlist',
            params: [
              3839,
              { ID: 'asc' },
              { USER_ID: 1 },
              ['ID', 'TASK_ID', 'USER_ID', 'SECONDS', 'MINUTES', 'COMMENT_TEXT', 'CREATED_DATE'],
              { NAV_PARAMS: { nPageSize: 2, iNumPage: 1 } },
            ],
            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('Elapsed items count:', result.length, 'First item:', result[0])
          }
        } 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 getElapsedItems() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              // task.elapseditem.getlist 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 variant when sort matters.
              const response = await $b24.actions.v2.call.make({
                method: 'task.elapseditem.getlist',
                params: [
                  3839,
                  { ID: 'asc' },
                  { USER_ID: 1 },
                  ['ID', 'TASK_ID', 'USER_ID', 'SECONDS', 'MINUTES', 'COMMENT_TEXT', 'CREATED_DATE'],
                  { NAV_PARAMS: { nPageSize: 2, iNumPage: 1 } },
                ],
                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('Elapsed items count:', result.length, 'First item:', result[0])
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', getElapsedItems)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        order = {
            "ID": "asc",
        }
        
        filter = {
            "USER_ID": 1,
        }
        
        try:
            bitrix_response = client.task.elapseditem.getlist(
                taskid=3839,
                order=order,
                filter=filter,
                select=["ID", "TASK_ID", "USER_ID", "SECONDS", "MINUTES", "COMMENT_TEXT", "CREATED_DATE"],
                params={
                    "NAV_PARAMS": {
                        "nPageSize": 2,
                        "iNumPage": 1,
                    },
                },
            ).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}")
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'task.elapseditem.getlist',
                    [
                        3839,
                        ['ID' => 'asc'],
                        ['USER_ID' => 1],
                        ['ID', 'TASK_ID', 'USER_ID', 'SECONDS', 'MINUTES', 'COMMENT_TEXT', 'CREATED_DATE'],
                        [
                            'NAV_PARAMS' => [
                                'nPageSize' => 2,
                                'iNumPage' => 1,
                            ],
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error getting elapsed time records: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'task.elapseditem.getlist',
            [
                3839,
                {'ID': 'asc'},
                {'USER_ID': 1},
                ['ID', 'TASK_ID', 'USER_ID', 'SECONDS', 'MINUTES', 'COMMENT_TEXT', 'CREATED_DATE'],
                {"NAV_PARAMS":{
                        "nPageSize":2,
                        "iNumPage":1
                    }
                },
            ],
            function(result) {
                if (result.error()) {
                    console.error(result.error());
                } else {
                    console.info(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'task.elapseditem.getlist',
            [
                3839,
                ['ID' => 'asc'],
                ['USER_ID' => 1],
                ['ID', 'TASK_ID', 'USER_ID', 'SECONDS', 'MINUTES', 'COMMENT_TEXT', 'CREATED_DATE'],
                [
                    'NAV_PARAMS' => [
                        'nPageSize' => 2,
                        'iNumPage' => 1,
                    ],
                ],
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "task.elapseditem.getlist", []any{
            3839,
            b24.Params{
                "ID": "asc",
            },
            b24.Params{
                "USER_ID": 1,
            },
            []string{"ID", "TASK_ID", "USER_ID", "SECONDS", "MINUTES", "COMMENT_TEXT", "CREATED_DATE"},
            b24.Params{
                "NAV_PARAMS": b24.Params{
                    "nPageSize": 2,
                    "iNumPage": 1,
                },
            },
        }, b24.WithIdempotent())
        if err != nil {
        	return fmt.Errorf("task.elapseditem.getlist: %w", err)
        }
        
        var items []struct {
        	ID          b24.ID `json:"ID"`
        	TaskID      b24.ID `json:"TASK_ID"`
        	UserID      b24.ID `json:"USER_ID"`
        	CommentText string `json:"COMMENT_TEXT"`
        	Seconds     string `json:"SECONDS"`
        	Minutes     string `json:"MINUTES"`
        }
        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)
        }
        

Response Handling

HTTP Status: 200

{
            "result":[
                {
                    "ID": "153",
                    "TASK_ID": "3839",
                    "USER_ID": "1",
                    "COMMENT_TEXT": "",
                    "SECONDS": "5100",
                    "MINUTES": "85",
                    "CREATED_DATE": "2025-12-18T14:16:51+02:00"
                },
                {
                    "ID": "155",
                    "TASK_ID": "3839",
                    "USER_ID": "1",
                    "COMMENT_TEXT": "",
                    "SECONDS": "23",
                    "MINUTES": "0",
                    "CREATED_DATE": "2025-12-18T14:16:37+02:00"
                }
            ],
            "total": 2,
            "time":{
                "start":1787829762,
                "finish":1787829762.985642,
                "duration":0.9856419563293457,
                "processing":0,
                "date_start":"2026-08-27T14:22:42+02:00",
                "date_finish":"2026-08-27T14:22:42+02:00",
                "operating_reset_at":1787830362,
                "operating":0.11980605125427246
            }
        }
        

Returned Data

Name
type

Description

result
array

Array of objects with information about time tracking records for the task

total
integer

Total number of records found

time
time

Information about the request execution time

Error Handling

HTTP Status: 400

{
            "error":"ERROR_CORE",
            "error_description":"ACTION_NOT_ALLOWED"
        }
        

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

0x100002

Access denied

0x000004

Action not allowed

0x000040

Unknown error

0x000100

Invalid method parameters provided

ERROR_CORE

Error executing the action. Check task access and the order of the method's positional parameters

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