Update Checklist Item of Task Template tasks.template.checklist.update

Scope: task

Who can execute the method: user with permissions to modify the task template

The method tasks.template.checklist.update updates a checklist item of the task template.

Method Parameters

Required parameters are marked with *

Name `type`	Description
templateId* `integer`	Identifier of the task template. The identifier of the task template can be obtained when creating a new template
checkListItemId* `integer`	Identifier of the checklist item. The identifier of the checklist item can be obtained when creating a new item or by using the method getting the list of items
fields* `object`	Fields to update the checklist item (detailed description)

Parameter fields

Name `type`	Description
TITLE `string`	Text of the checklist item If `PARENT_ID` is passed with a value of `0`, then `TITLE` is the name of the checklist
PARENT_ID `integer`	Identifier of the parent item. Use for nested checklists If `PARENT_ID` is passed with a value of `0`, the system will create a new checklist in the task template If there is no checklist item with the specified `PARENT_ID` in the template, the system will create a new checklist If the main checklist item is moved under another checklist item, it will move along with its sub-items while maintaining the hierarchy. The checklists will merge into one
SORT_INDEX `integer`	Sort index. The lower the value, the higher the item in the list or sublist
IS_COMPLETE `boolean`	Completion status of the item. Possible values: `Y` — completed `N` — not completed
IS_IMPORTANT `boolean`	Mark indicating that the item is important. Possible values: `Y` — important `N` — ordinary
MEMBERS `object`	Object describing the participants of the checklist item. Key — user identifier, value — object with the participant type parameter `TYPE`. Possible participant type values: `'TYPE': 'A'` — Participant `'TYPE': 'U'` — Observer The `MEMBERS` field is completely replaced. To retain current participants, pass them along with new values The system will add checklist item participants to the task in the same roles

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{
          "templateId": 139,
          "checkListItemId": 37,
          "fields": {
            "TITLE": "4. Prepare the dashboard and send the link"
          }
        }' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/tasks.template.checklist.update

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{
          "templateId": 139,
          "checkListItemId": 37,
          "fields": {
            "TITLE": "4. Prepare the dashboard and send the link"
          },
          "auth": "**put_access_token_here**"
        }' \
        https://**put_your_bitrix24_address**/rest/tasks.template.checklist.update

try
        {
            const response = await $b24.callMethod(
                'tasks.template.checklist.update',
                {
                    templateId: 139,
                    checkListItemId: 37,
                    fields: {
                        TITLE: '4. Prepare the dashboard and send the link'
                    }
                }
            );
        
            const result = response.getData().result;
            console.log(result);
        }
        catch (error)
        {
            console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'tasks.template.checklist.update',
                    [
                        'templateId' => 139,
                        'checkListItemId' => 37,
                        'fields' => [
                            'TITLE' => '4. Prepare the dashboard and send the link'
                        ]
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            print_r($result);
        } catch (Throwable $e) {
            echo $e->getMessage();
        }

BX24.callMethod(
            'tasks.template.checklist.update',
            {
                templateId: 139,
                checkListItemId: 37,
                fields: {
                    TITLE: '4. Prepare the dashboard and send the link'
                }
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.log(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'tasks.template.checklist.update',
            [
                'templateId' => 139,
                'checkListItemId' => 37,
                'fields' => [
                    'TITLE' => '4. Prepare the dashboard and send the link'
                ]
            ]
        );
        
        print_r($result);

Response Handling

HTTP Status: 200

{
            "result": {
                "checkListItem": {
                    "id": 37,
                    "copiedId": null,
                    "userId": 503,
                    "createdBy": null,
                    "parentId": 23,
                    "title": "4. Prepare the dashboard and send the link",
                    "sortIndex": 3,
                    "displaySortIndex": "",
                    "isComplete": false,
                    "isImportant": true,
                    "completedCount": 0,
                    "members": [
                        {
                            "id": "547",
                            "type": "A",
                            "name": "Anna Peterson",
                            "personalPhoto": "57129",
                            "personalGender": "",
                            "image": "https://mysite.com/b17053/resize_cache/57129/c0120a8d7c10d63c83e32398d1ec4d9e/main/137/137bfa78b877be117e75f1ac8652834a/anna.png",
                            "isCollaber": false
                        }
                    ],
                    "attachments": [],
                    "nodeId": null,
                    "templateId": 139
                }
            },
            "time": {
                "start": 1773238088,
                "finish": 1773238088.917228,
                "duration": 0.9172279834747314,
                "processing": 0,
                "date_start": "2026-03-11T17:08:08+01:00",
                "date_finish": "2026-03-11T17:08:08+01:00",
                "operating_reset_at": 1773238688,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `object`	Object with response data (detailed description)
time `time`	Information about the request execution time

Object result

Name `type`	Description
checkListItem `object`	Updated checklist item (detailed description)

Object checkListItem

Name `type`	Description
id `integer`	Identifier of the checklist item
copiedId `integer`	Identifier of the original item when copied, if applicable
userId `integer`	Identifier of the user in the context of which the object was created
createdBy `integer`	Identifier of the item creator
parentId `integer`	Identifier of the parent item. A value of `0` indicates a root item
title `string`	Text of the checklist item
sortIndex `integer`	Sorting index. The lower the value, the higher the item appears in the list or sublist
displaySortIndex `string`	Auxiliary value for display order
isComplete `boolean`	Status of item completion
isImportant `boolean`	Importance flag for the item
completedCount `integer`	Number of completions for the item
members `array`	Array of objects with description of participants. If there is no data, an empty array `[]` is returned
attachments `object`	Object with description of attachments. If there is no data, an empty array `[]` is returned
nodeId `integer`	Service identifier of the node, if used
templateId `integer`	Identifier of the task template

Object members

Name `type`	Description
id `string`	Identifier of the user
type `string`	User's role in the checklist item. Possible values: `A` — Participant `U` — Observer
name `string`	User's name
personalPhoto `string`	Identifier of the user's avatar file on Drive
personalGender `string`	User's gender. Possible values: `M` — Male `F` — Female
image `string`	Link to the user's avatar
isCollaber `boolean`	Indicator that the user is an external participant

Object attachments

Name `type`	Description
`string`	Identifier of the file on Drive in the format `n<fileId>`, where the key is the identifier of the attachment

Error Handling

HTTP Status: 400

{
            "error": "100",
            "error_description": "Could not find value for parameter {templateId}"
        }

Name `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `error_description`	Textual description of the error. The description is not intended to be shown to the end user in its raw form

Possible Error Codes

Status	Code	Description	Value
`400`	`100`	Could not find value for parameter	Required parameter `templateId` not provided
`400`	`100`	Bitrix\Tasks\CheckList\Internals\CheckList All parameters in the constructor must have real class type	Required parameter `checkListItemId` not provided
`400`	`100`	Could not find value for parameter	Required parameter `fields` not provided or empty
`400`	`0`	Bitrix\Tasks\CheckList\CheckListFacade::onAfterUpdate(): Argument #1 ($taskId) must be of type int, string given, called in /var/www/html/bitrix/modules/tasks/lib/checklist/checklistfacade.php on line 313	Empty or incorrect type `templateId` provided
`400`	`0`	Incorrect value [] for field [ENTITY_ID] in item [, Item name]	Non-existent, empty, or incorrect type `checkListItemId` provided
`400`	`0`	Changing item: action not available	User does not have permission to modify the task template

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not allowed to be called using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The methods must be called using the HTTPS protocol
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is available only on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user whose access token or webhook was used to call the method lacks permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users
`500`	`PORTAL_DELETED` Portal was deleted	The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning

Add Checklist Item

Retrieve Checklist Item

Update Checklist Item of Task Template tasks.template.checklist.update

Method ParametersMethod Parameters

Parameter fieldsParameter fields

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Object resultObject result

Object checkListItemObject checkListItem

Object membersObject members

Object attachmentsObject attachments

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning