Update the section of the universal list lists.section.update
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:
listsWho can execute the method: a user with "Edit" or "Edit with restrictions" access permission for the required list
The method lists.section.update updates a list section.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
IBLOCK_TYPE_ID* |
Information block type ID. Standard types:
In the on-premise version, you can also specify the ID of any existing custom information block type. |
|
IBLOCK_ID* |
Identifier of the information block. The identifier can be obtained using the lists.get method |
|
IBLOCK_CODE* |
Symbolic code of the information block. The code can be obtained using the lists.get method At least one of the parameters must be specified: |
|
SECTION_ID* |
Identifier of the section. The identifier can be obtained using the lists.section.get method |
|
SECTION_CODE* |
Symbolic code of the section. The code can be obtained using the lists.section.get At least one of the parameters must be specified: |
|
FIELDS* |
Array of fields. |
FIELDS Parameter
Required parameters are marked with *
|
Name |
Description |
|
NAME* |
Name of the section |
|
EXTERNAL_ID |
External identifier of the section |
|
XML_ID |
External identifier (XML ID) |
|
SORT |
Sorting |
|
ACTIVE |
Activity status. Possible values:
|
|
PICTURE |
Deprecated. Image. Object in the format To delete the image, use the object in the format |
|
DESCRIPTION |
Deprecated. Description |
|
DESCRIPTION_TYPE |
Deprecated. Description type. Possible values:
Defaults to |
|
DETAIL_PICTURE |
Deprecated. Detail image. Object in the format To delete the image, use the object in the format |
|
SECTION_PROPERTY |
Deprecated. User properties |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"IBLOCK_TYPE_ID":"lists","IBLOCK_ID":95,"SECTION_ID":169,"FIELDS":{"NAME":"Updated Marketing Documents","EXTERNAL_ID":"ext_marketing_docs_002","XML_ID":"xml_marketing_docs_002","SORT":600,"ACTIVE":"Y"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/lists.section.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"IBLOCK_TYPE_ID":"lists","IBLOCK_ID":95,"SECTION_ID":169,"FIELDS":{"NAME":"Updated Marketing Documents","EXTERNAL_ID":"ext_marketing_docs_002","XML_ID":"xml_marketing_docs_002","SORT":600,"ACTIVE":"Y"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/lists.section.update
// 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 } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
try {
const response = await $b24.actions.v2.call.make<boolean>({
method: 'lists.section.update',
params: {
IBLOCK_TYPE_ID: 'lists',
IBLOCK_ID: 95,
SECTION_ID: 169,
FIELDS: {
NAME: 'Updated marketing documents',
EXTERNAL_ID: 'ext_marketing_docs_002',
XML_ID: 'xml_marketing_docs_002',
SORT: 600,
ACTIVE: 'Y',
},
},
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('Section updated successfully:', result)
}
} 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 updateSection() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'lists.section.update',
params: {
IBLOCK_TYPE_ID: 'lists',
IBLOCK_ID: 95,
SECTION_ID: 169,
FIELDS: {
NAME: 'Updated marketing documents',
EXTERNAL_ID: 'ext_marketing_docs_002',
XML_ID: 'xml_marketing_docs_002',
SORT: 600,
ACTIVE: 'Y',
},
},
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('Section updated successfully:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', updateSection)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
fields = {
"NAME": "Updated marketing documents",
"EXTERNAL_ID": "ext_marketing_docs_002",
"XML_ID": "xml_marketing_docs_002",
"SORT": 600,
"ACTIVE": "Y",
}
try:
bitrix_response = client.lists.section.update(
iblock_type_id='lists',
iblock_id=95,
section_id=169,
fields=fields,
).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(
'lists.section.update',
[
'IBLOCK_TYPE_ID' => 'lists',
'IBLOCK_ID' => 95,
'SECTION_ID' => 169,
'FIELDS' => [
'NAME' => 'Updated Marketing Documents',
'EXTERNAL_ID' => 'ext_marketing_docs_002',
'XML_ID' => 'xml_marketing_docs_002',
'SORT' => 600,
'ACTIVE' => 'Y',
]
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating section: ' . $e->getMessage();
}
BX24.callMethod(
'lists.section.update',
{
IBLOCK_TYPE_ID: 'lists',
IBLOCK_ID: 95,
SECTION_ID: 169,
FIELDS: {
NAME: 'Updated Marketing Documents',
EXTERNAL_ID: 'ext_marketing_docs_002',
XML_ID: 'xml_marketing_docs_002',
SORT: 600,
ACTIVE: 'Y',
}
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'lists.section.update',
[
'IBLOCK_TYPE_ID' => 'lists',
'IBLOCK_ID' => 95,
'SECTION_ID' => 169,
'FIELDS' => [
'NAME' => 'Updated Marketing Documents',
'EXTERNAL_ID' => 'ext_marketing_docs_002',
'XML_ID' => 'xml_marketing_docs_002',
'SORT' => 600,
'ACTIVE' => 'Y',
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "lists.section.update", b24.Params{
"IBLOCK_TYPE_ID": "lists",
"IBLOCK_ID": 95,
"SECTION_ID": 169,
"FIELDS": b24.Params{
"NAME": "Updated Marketing Documents",
"EXTERNAL_ID": "ext_marketing_docs_002",
"XML_ID": "xml_marketing_docs_002",
"SORT": 600,
"ACTIVE": "Y",
},
})
if err != nil {
return fmt.Errorf("lists.section.update: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("done:", ok)
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1761555629,
"finish": 1761555630.010893,
"duration": 1.0108931064605713,
"processing": 1,
"date_start": "2025-10-27T12:00:29+02:00",
"date_finish": "2025-10-27T12:00:30+02:00",
"operating_reset_at": 1761556229,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Returns |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400
{
"error":"ERROR_REQUIRED_PARAMETERS_MISSING",
"error_description":"Required parameter is missing"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
Value |
|
|
Required parameter |
Required parameter not provided |
|
|
Section not found |
Section with the specified |
|
|
— |
Error updating the section |
|
|
Access denied |
Insufficient rights to update the section |
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 |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
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 |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
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 — |
|
|
|
No active webhook with the specified user identifier and secret code was 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 |
|
|
|
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 |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
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 |