Get a List of Storage Sections entity.section.get
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:
entityWho can execute the method: any user upon application authorization
The entity.section.get method retrieves a list of sections from the application's data storage.
The method works only in the context of an 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. |
|
SORT |
Object format:
where:
Refer to the Section Type for a list of available sorting fields. The default is Example: |
|
FILTER |
Object format:
where:
Refer to the Section Type for a list of available filtering fields. You can add prefixes to the keys
|
|
start |
Pagination parameter. The page size is fixed at The formula for obtaining the N-th page: More details can be found in the article Features of List Methods |
Code Examples
How to Use Examples in Documentation
Example of retrieving sections from the storage, where:
ENTITY— storage identifierdishSORT— sorting by nameFILTER— only active sections
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ENTITY":"dish","SORT":{"NAME":"ASC"},"FILTER":{"ACTIVE":"Y"},"start":0,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/entity.section.get
// 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, ISODate } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of each SectionItem returned in result[]
type SectionItem = {
ID: string
CODE: string | null
TIMESTAMP_X: ISODate
DATE_CREATE: ISODate
CREATED_BY: string
MODIFIED_BY: string
ACTIVE: 'Y' | 'N'
SORT: string
NAME: string
PICTURE: string | null
DETAIL_PICTURE: string | null
DESCRIPTION: string | null
LEFT_MARGIN: string
RIGHT_MARGIN: string
DEPTH_LEVEL: string
ENTITY: string
SECTION: string | null
}
try {
// entity.section.get returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
const response = await $b24.actions.v2.call.make<SectionItem[]>({
method: 'entity.section.get',
params: {
ENTITY: 'dish',
SORT: { NAME: 'ASC' },
FILTER: { ACTIVE: 'Y' },
start: 0,
},
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('sections:', result.length, 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 fetchSections() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
// entity.section.get returns a single page (max 50 records). For the whole result set
// use a list helper: $b24.actions.v2.callList.make() returns every record as one
// array, $b24.actions.v2.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `start` variant when sort matters.
const response = await $b24.actions.v2.call.make({
method: 'entity.section.get',
params: {
ENTITY: 'dish',
SORT: { NAME: 'ASC' },
FILTER: { ACTIVE: 'Y' },
start: 0,
},
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('sections:', result.length, result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', fetchSections)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.entity.section.get(
entity="dish",
sort={
"NAME": "ASC",
},
filter={
"ACTIVE": "Y",
},
start=0,
).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(
'entity.section.get',
[
'ENTITY' => 'dish',
'SORT' => ['NAME' => 'ASC'],
'FILTER' => ['ACTIVE' => 'Y'],
'start' => 0,
]
);
$result = $response
->getResponseData()
->getResult();
echo '<pre>';
print_r($result);
echo '</pre>';
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting entity sections: ' . $e->getMessage();
}
BX24.callMethod(
'entity.section.get',
{
ENTITY: 'dish',
SORT: { NAME: 'ASC' },
FILTER: { ACTIVE: 'Y' },
},
(result) => {
if (result.error()) {
console.error(result.error());
return;
}
console.info(result.data());
if (result.more()) {
result.next();
}
},
);
require_once('crest.php');
$result = CRest::call(
'entity.section.get',
[
'ENTITY' => 'dish',
'SORT' => ['NAME' => 'ASC'],
'FILTER' => ['ACTIVE' => 'Y'],
'start' => 0,
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "entity.section.get", b24.Params{
"ENTITY": "dish",
"SORT": b24.Params{
"NAME": "ASC",
},
"FILTER": b24.Params{
"ACTIVE": "Y",
},
"start": 0,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("entity.section.get: %w", err)
}
var items []struct {
ID b24.ID `json:"ID"`
TimestampX string `json:"TIMESTAMP_X"`
DateCreate string `json:"DATE_CREATE"`
CreatedBy string `json:"CREATED_BY"`
ModifiedBy string `json:"MODIFIED_BY"`
Active string `json:"ACTIVE"`
}
if err := json.Unmarshal(res.Result, &items); err != nil {
return fmt.Errorf("parse response: %w", err)
}
for _, it := range items {
fmt.Println(it.ID, it.TimestampX)
}
Response Handling
HTTP Status: 200
{
"result": [
{
"ID": "671",
"CODE": null,
"TIMESTAMP_X": "2026-03-23T17:15:51+02:00",
"DATE_CREATE": "2026-03-23T17:15:51+02:00",
"CREATED_BY": "577",
"MODIFIED_BY": "577",
"ACTIVE": "Y",
"SORT": "500",
"NAME": "Parent Section",
"PICTURE": null,
"DETAIL_PICTURE": null,
"DESCRIPTION": null,
"LEFT_MARGIN": "1",
"RIGHT_MARGIN": "6",
"DEPTH_LEVEL": "1",
"ENTITY": "dish",
"SECTION": null
},
{
"ID": "669",
"CODE": null,
"TIMESTAMP_X": "2026-03-23T17:14:22+02:00",
"DATE_CREATE": "2026-03-23T17:14:22+02:00",
"CREATED_BY": "577",
"MODIFIED_BY": "577",
"ACTIVE": "Y",
"SORT": "500",
"NAME": "Test Section",
"PICTURE": null,
"DETAIL_PICTURE": null,
"DESCRIPTION": null,
"LEFT_MARGIN": "7",
"RIGHT_MARGIN": "8",
"DEPTH_LEVEL": "1",
"ENTITY": "dish",
"SECTION": null
},
{
"ID": "673",
"CODE": null,
"TIMESTAMP_X": "2026-03-23T17:16:37+02:00",
"DATE_CREATE": "2026-03-23T17:16:37+02:00",
"CREATED_BY": "577",
"MODIFIED_BY": "577",
"ACTIVE": "Y",
"SORT": "500",
"NAME": "Test Section",
"PICTURE": null,
"DETAIL_PICTURE": null,
"DESCRIPTION": null,
"LEFT_MARGIN": "4",
"RIGHT_MARGIN": "5",
"DEPTH_LEVEL": "2",
"ENTITY": "dish",
"SECTION": "671"
},
{
"ID": "675",
"CODE": "test-section",
"TIMESTAMP_X": "2026-03-23T17:42:32+02:00",
"DATE_CREATE": "2026-03-23T17:42:32+02:00",
"CREATED_BY": "577",
"MODIFIED_BY": "577",
"ACTIVE": "Y",
"SORT": "500",
"NAME": "Test Section",
"PICTURE": null,
"DETAIL_PICTURE": null,
"DESCRIPTION": "Description of the test section",
"LEFT_MARGIN": "2",
"RIGHT_MARGIN": "3",
"DEPTH_LEVEL": "2",
"ENTITY": "dish",
"SECTION": "671"
}
],
"total": 4,
"time": {
"start": 1774338416,
"finish": 1774338416.415466,
"duration": 0.4154660701751709,
"processing": 0,
"date_start": "2026-03-24T10:46:56+02:00",
"date_finish": "2026-03-24T10:46:56+02:00",
"operating_reset_at": 1774339016,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
List of storage sections |
|
total |
Total number of sections in the selection |
|
next |
Offset for retrieving the next page (if available) |
|
time |
Information about the request execution time |
Section Type
|
Name |
Description |
|
ID |
Identifier of the section |
|
CODE |
Symbolic code of the section |
|
TIMESTAMP_X |
Date and time of the last modification |
|
DATE_CREATE |
Date and time of creation |
|
CREATED_BY |
Identifier of the user who created the section |
|
MODIFIED_BY |
Identifier of the user who modified the section |
|
ACTIVE |
Active flag ( |
|
SORT |
Sorting index |
|
NAME |
Name of the section |
|
PICTURE |
URL of the section picture or |
|
DETAIL_PICTURE |
URL of the detailed section picture or |
|
DESCRIPTION |
Description of the section |
|
LEFT_MARGIN |
Left boundary of the section in the tree |
|
RIGHT_MARGIN |
Right boundary of the section in the tree |
|
DEPTH_LEVEL |
Depth level of the section |
|
ENTITY |
Identifier of the storage |
|
SECTION |
Identifier of the parent section or |
Error Handling
HTTP Status: 400
{
"error": "ERROR_ARGUMENT",
"error_description": "Argument 'ENTITY' is null or empty",
"argument": "ENTITY"
}
{
"error": "ERROR_ENTITY_NOT_FOUND",
"error_description": "Entity not found"
}
|
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 |
|
|
Argument 'ENTITY' is null or empty |
Parameter |
|
|
Entity code is too long. Max length is N characters. |
|
|
|
Entity not found |
Storage with the provided |
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 |