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: entity

Who can execute the method: a user with access permission level W (write) or X (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
type

Description

ENTITY*
string

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*
integer

Identifier of the section to be updated.

NAME
string

Name of the section.

SECTION
integer

Identifier of the parent section.

ACTIVE
string

Active flag for the section:

  • Y — section is active
  • N — section is inactive.

SORT
integer

Sorting index of the section.

CODE
string

Symbolic code of the section.

DESCRIPTION
string

Description of the section.

PICTURE
file

Image of the section. File format — see the article How to upload files.

DETAIL_PICTURE
file

Detailed image of the section. File format — see the article How to upload files.

UF_
object

Custom fields of the section UF_* in the format {"UF_CODE": value}

Code Examples

How to Use Examples in Documentation

Example of updating a section where:

  • ENTITY — identifier of the storage dish
  • ID — identifier of the section 673
  • 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
type

Description

result
boolean

Result of the method execution. Returns true for a successful update.

time
time

Information about the request execution time.

Error Handling

HTTP Status: 400

{
            "error": "ERROR_SECTION_NOT_FOUND",
            "error_description": "Section not found"
        }
        

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

Code

Description

Value

ERROR_ARGUMENT

Argument 'ENTITY' is null or empty

The ENTITY parameter is not provided or is empty after cleaning.

ERROR_ARGUMENT

Entity code is too long. Max length is N characters.

The ENTITY value is too long.

ERROR_ARGUMENT

Argument 'ID' is null or empty

The ID parameter is not provided or has a value of 0.

ERROR_ENTITY_NOT_FOUND

Entity not found

The storage with the provided ENTITY was not found.

ERROR_SECTION_NOT_FOUND

Section not found

The section with the specified ID was not found in this storage.

ACCESS_DENIED

Access denied!

Insufficient permissions to update the section.

ERROR_CORE

Internal error updating entity section. Try updating again.

Internal error while updating the section.

ERROR_CORE

Invalid file type

An unsupported file type was provided in PICTURE or DETAIL_PICTURE.

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 permitted for calls 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 HTTPS protocol is required for method calls

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is only available on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user associated with the access token or webhook used to call the method lacks the necessary 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 portal administrator has restricted access to this application to specific users only

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 "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