Update Task Template tasks.template.update
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:
taskWho can execute the method: user with template editing access permission
The method tasks.template.update updates an existing task template.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
templateId* |
Identifier of the task template. The task template identifier can be obtained when creating a new template |
|
fields* |
Fields of the template that need to be modified. The fields and value types correspond to the description on the Task Template Fields page |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"templateId": 139,
"fields": {
"TITLE": "Preparation of Weekly Project Status and Approval",
"DESCRIPTION": "Updated task template for preparing the weekly project status and final approval before submission",
"PRIORITY": 1,
"TASK_CONTROL": "Y",
"ADD_IN_REPORT": "Y",
"UF_CRM_TASK": ["L_1179", "D_1833"]
}
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/tasks.template.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"templateId": 139,
"fields": {
"TITLE": "Preparation of Weekly Project Status and Approval",
"DESCRIPTION": "Updated task template for preparing the weekly project status and final approval before submission",
"PRIORITY": 1,
"TASK_CONTROL": "Y",
"ADD_IN_REPORT": "Y",
"UF_CRM_TASK": ["L_1179", "D_1833"]
},
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/tasks.template.update
try
{
const response = await $b24.callMethod(
'tasks.template.update',
{
templateId: 139,
fields: {
TITLE: 'Preparation of Weekly Project Status and Approval',
DESCRIPTION: 'Updated task template for preparing the weekly project status and final approval before submission',
PRIORITY: 1,
TASK_CONTROL: 'Y',
ADD_IN_REPORT: 'Y',
UF_CRM_TASK: ['L_1179', 'D_1833']
}
}
);
const result = response.getData().result;
console.log(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'tasks.template.update',
[
'templateId' => 139,
'fields' => [
'TITLE' => 'Preparation of Weekly Project Status and Approval',
'DESCRIPTION' => 'Updated task template for preparing the weekly project status and final approval before submission',
'PRIORITY' => 1,
'TASK_CONTROL' => 'Y',
'ADD_IN_REPORT' => 'Y',
'UF_CRM_TASK' => ['L_1179', 'D_1833']
]
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
echo 'Error updating template: ' . $e->getMessage();
}
BX24.callMethod(
'tasks.template.update',
{
templateId: 139,
fields: {
TITLE: 'Preparation of Weekly Project Status and Approval',
DESCRIPTION: 'Updated task template for preparing the weekly project status and final approval before submission',
PRIORITY: 1,
TASK_CONTROL: 'Y',
ADD_IN_REPORT: 'Y',
UF_CRM_TASK: ['L_1179', 'D_1833']
}
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'tasks.template.update',
[
'templateId' => 139,
'fields' => [
'TITLE' => 'Preparation of Weekly Project Status and Approval',
'DESCRIPTION' => 'Updated task template for preparing the weekly project status and final approval before submission',
'PRIORITY' => 1,
'TASK_CONTROL' => 'Y',
'ADD_IN_REPORT' => 'Y',
'UF_CRM_TASK' => ['L_1179', 'D_1833']
]
]
);
print_r($result);
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1773221471,
"finish": 1773221471.833299,
"duration": 0.833298921585083,
"processing": 0,
"date_start": "2026-03-11T12:31:11+01:00",
"date_finish": "2026-03-11T12:31:11+01:00",
"operating_reset_at": 1773222071,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Returns Returns
|
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "100",
"error_description": "Could not find value for parameter {templateId}"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
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 |
|
|
|
Could not find value for parameter |
Required parameter |
|
|
|
Invalid value {} to match with parameter {templateId}. Should be value of type int. |
Parameter |
|
|
|
Could not find value for parameter |
Required parameter |
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 |
Continue Learning
- Add Task Template tasks.template.add
- Get Task Template by ID tasks.template.get
- Delete Task Template tasks.template.delete
- Get the List of Task Template Fields `tasks.template.fields`