Get a List of Storage Items: entity.item.get
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 authorized in the application
The entity.item.get method retrieves a list of items from the application's data storage.
This 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 Item Type section for a list of available sorting fields. By default, |
|
FILTER |
Object format:
where:
Refer to the Item Type section 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: For more details, refer to the article Features of List Methods |
Code Examples
How to Use Examples in Documentation
Example of retrieving storage items where:
ENTITY— storage identifierdish_v2SORT— sorting by activity date and identifierFILTER— date range of activity
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ENTITY":"dish_v2","SORT":{"DATE_ACTIVE_FROM":"ASC","ID":"ASC"},"FILTER":{">=DATE_ACTIVE_FROM":"2026-03-01T00:00:00+01:00","<DATE_ACTIVE_FROM":"2026-04-01T00:00:00+01:00"},"start":0,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/entity.item.get
try
{
const response = await $b24.callMethod(
'entity.item.get',
{
ENTITY: 'dish_v2',
SORT: {
DATE_ACTIVE_FROM: 'ASC',
ID: 'ASC',
},
FILTER: {
'>=DATE_ACTIVE_FROM': '2026-03-01T00:00:00+01:00',
'<DATE_ACTIVE_FROM': '2026-04-01T00:00:00+01:00',
},
start: 0,
}
);
const result = response.getData().result;
console.info(result);
}
catch (error)
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'entity.item.get',
[
'ENTITY' => 'dish_v2',
'SORT' => [
'DATE_ACTIVE_FROM' => 'ASC',
'ID' => 'ASC',
],
'FILTER' => [
'>=DATE_ACTIVE_FROM' => '2026-03-01T00:00:00+01:00',
'<DATE_ACTIVE_FROM' => '2026-04-01T00:00:00+01:00',
],
'start' => 0,
]
);
$result = $response
->getResponseData()
->getResult();
echo '<pre>';
print_r($result);
echo '</pre>';
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting entity items: ' . $e->getMessage();
}
BX24.callMethod(
'entity.item.get',
{
ENTITY: 'dish_v2',
SORT: {
DATE_ACTIVE_FROM: 'ASC',
ID: 'ASC',
},
FILTER: {
'>=DATE_ACTIVE_FROM': '2026-03-01T00:00:00+01:00',
'<DATE_ACTIVE_FROM': '2026-04-01T00:00:00+01:00',
},
},
(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.item.get',
[
'ENTITY' => 'dish_v2',
'SORT' => [
'DATE_ACTIVE_FROM' => 'ASC',
'ID' => 'ASC',
],
'FILTER' => [
'>=DATE_ACTIVE_FROM' => '2026-03-01T00:00:00+01:00',
'<DATE_ACTIVE_FROM' => '2026-04-01T00:00:00+01:00',
],
'start' => 0,
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": [
{
"ID": "2331",
"TIMESTAMP_X": "2026-03-25T12:29:06+01:00",
"MODIFIED_BY": "577",
"DATE_CREATE": "2026-03-25T12:29:06+01:00",
"CREATED_BY": "577",
"ACTIVE": "Y",
"DATE_ACTIVE_FROM": "",
"DATE_ACTIVE_TO": "",
"SORT": "500",
"NAME": "Test Item",
"PREVIEW_PICTURE": null,
"PREVIEW_TEXT": null,
"DETAIL_PICTURE": null,
"DETAIL_TEXT": null,
"CODE": null,
"ENTITY": "dish",
"SECTION": null
}
],
"total": 1,
"time": {
"start": 1774430946,
"finish": 1774430946.627232,
"duration": 0.6272320747375488,
"processing": 0,
"date_start": "2026-03-25T12:29:06+01:00",
"date_finish": "2026-03-25T12:29:06+01:00",
"operating_reset_at": 1774431546,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
List of storage items |
|
total |
Total number of items in the selection |
|
next |
Offset for retrieving the next page (if available) |
|
time |
Information about the execution time of the request |
Item Type
|
Name |
Description |
|
ID |
Identifier of the item |
|
TIMESTAMP_X |
Date and time of the last modification |
|
MODIFIED_BY |
Identifier of the user who modified the item |
|
DATE_CREATE |
Date and time of creation |
|
CREATED_BY |
Identifier of the user who created the item |
|
ACTIVE |
Active flag ( |
|
Start date of activity or empty string |
|
|
End date of activity or empty string |
|
|
SORT |
Sorting index |
|
NAME |
Name of the item |
|
URL of the preview image |
|
|
Preview text |
|
|
URL of the detailed image |
|
|
Detailed text |
|
|
Symbolic code of the item |
|
|
ENTITY |
Identifier of the storage |
|
Identifier of the section |
|
|
PROPERTY_VALUES |
Object of property values in the format You can obtain a list of available property codes using the entity.item.property.get method. |
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 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 |
|
|
Filter validator errors |
Invalid values were provided for the |
|
|
Entity not found |
The storage with the provided |
|
|
Access denied! Application context required |
No application context ( |
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 Item to the Storage entity.item.add
- Update Entity Storage `entity.item.update`
- Delete Entity Storage Method: entity.item.delete
- Properties of Data Storage Elements: Overview of Methods