Update the entity.section.update method
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:
entityWho can execute the method: a user with access permission level
W(write) orX(manage) on the data storage
The entity.section.update method updates a section of the application's data storage.
The method works only in the context of the application.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
ENTITY* |
Identifier of the application's data storage. Use the value specified when creating the storage. You can obtain the identifier using the entity.get method. |
|
ID* |
Identifier of the section to be updated. |
|
NAME |
Name of the section. |
|
SECTION |
Identifier of the parent section. |
|
ACTIVE |
Active flag for the section:
|
|
SORT |
Sorting index of the section. |
|
CODE |
Symbolic code of the section. |
|
DESCRIPTION |
Description of the section. |
|
PICTURE |
Image of the section. File format — see the article How to upload files. |
|
DETAIL_PICTURE |
Detailed image of the section. File format — see the article How to upload files. |
|
UF_ |
Custom fields of the section |
Code Examples
How to Use Examples in Documentation
Example of updating a section where:
ENTITY— identifier of the storagedishID— identifier of the section673- all main parameters are updated:
NAME,SECTION,ACTIVE,SORT,CODE,DESCRIPTION,PICTURE,DETAIL_PICTURE,UF_*
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ENTITY":"dish","ID":673,"NAME":"Test Section (updated)","SECTION":671,"ACTIVE":"Y","SORT":550,"CODE":"test-section-updated","DESCRIPTION":"Updated description","PICTURE":["section.jpg","**base64_section_image**"],"DETAIL_PICTURE":["section-detail.jpg","**base64_section_detail_image**"],"UF_COLOR":"#ff6600","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/entity.section.update
try
{
const response = await $b24.callMethod(
'entity.section.update',
{
ENTITY: 'dish',
ID: 673,
NAME: 'Test Section (updated)',
SECTION: 671,
ACTIVE: 'Y',
DESCRIPTION: 'Updated description',
CODE: 'test-section-updated',
SORT: 550,
PICTURE: ['section.jpg', '**base64_section_image**'],
DETAIL_PICTURE: ['section-detail.jpg', '**base64_section_detail_image**'],
UF_COLOR: '#ff6600',
}
);
const result = response.getData().result;
console.info(result);
}
catch (error)
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'entity.section.update',
[
'ENTITY' => 'dish',
'ID' => 673,
'NAME' => 'Test Section (updated)',
'SECTION' => 671,
'ACTIVE' => 'Y',
'DESCRIPTION' => 'Updated description',
'CODE' => 'test-section-updated',
'SORT' => 550,
'PICTURE' => ['section.jpg', '**base64_section_image**'],
'DETAIL_PICTURE' => ['section-detail.jpg', '**base64_section_detail_image**'],
'UF_COLOR' => '#ff6600',
]
);
$result = $response
->getResponseData()
->getResult();
echo '<pre>';
print_r($result);
echo '</pre>';
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating entity section: ' . $e->getMessage();
}
BX24.callMethod(
'entity.section.update',
{
ENTITY: 'dish',
ID: 673,
NAME: 'Test Section (updated)',
SECTION: 671,
ACTIVE: 'Y',
DESCRIPTION: 'Updated description',
CODE: 'test-section-updated',
SORT: 550,
PICTURE: ['section.jpg', '**base64_section_image**'],
DETAIL_PICTURE: ['section-detail.jpg', '**base64_section_detail_image**'],
UF_COLOR: '#ff6600',
},
(result) => {
result.error()
? console.error(result.error())
: console.info(result.data())
;
},
);
require_once('crest.php');
$result = CRest::call(
'entity.section.update',
[
'ENTITY' => 'dish',
'ID' => 673,
'NAME' => 'Test Section (updated)',
'SECTION' => 671,
'ACTIVE' => 'Y',
'DESCRIPTION' => 'Updated description',
'CODE' => 'test-section-updated',
'SORT' => 550,
'PICTURE' => ['section.jpg', '**base64_section_image**'],
'DETAIL_PICTURE' => ['section-detail.jpg', '**base64_section_detail_image**'],
'UF_COLOR' => '#ff6600',
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1774341623,
"finish": 1774341623.380336,
"duration": 0.38033604621887207,
"processing": 0,
"date_start": "2026-03-24T11:40:23+01:00",
"date_finish": "2026-03-24T11:40:23+01:00",
"operating_reset_at": 1774342223,
"operating": 0.1318378448486328
}
}
Returned Data
|
Name |
Description |
|
result |
Result of the method execution. Returns |
|
time |
Information about the request execution time. |
Error Handling
HTTP Status: 400
{
"error": "ERROR_SECTION_NOT_FOUND",
"error_description": "Section not found"
}
|
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
|
Code |
Description |
Value |
|
|
Argument 'ENTITY' is null or empty |
The |
|
|
Entity code is too long. Max length is N characters. |
The |
|
|
Argument 'ID' is null or empty |
The |
|
|
Entity not found |
The storage with the provided |
|
|
Section not found |
The section with the specified |
|
|
Access denied! |
Insufficient permissions to update the section. |
|
|
Internal error updating entity section. Try updating again. |
Internal error while updating the section. |
|
|
Invalid file type |
An unsupported file type was provided in |
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 Section to the entity.section.add Storage
- Get a List of Sections with entity.section.get
- Delete the entity.section.delete method
- Data Storage Sections: Overview of Methods