Get a List of Custom Blocks landing.repo.getList
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:
landingWho can execute the method: a user with View access permission in the Sites section
The method landing.repo.getList retrieves a list of custom blocks.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
params |
Object format:
where:
For more details on each parameter, see the params parameter section |
params Parameter
|
Name |
Description |
|
select |
Array format:
where:
For a list of available fields for selection, see the result element type section. Elements in |
|
filter |
Object format:
where:
For a list of available fields for filtering, see the result element type section. If |
|
order |
Object format:
where:
For a list of available fields for sorting, see the result element type section |
|
group |
Array of fields for grouping the result. Format:
where:
Examples:
For a list of available fields, see the result element type section |
|
limit |
Limit of records |
|
offset |
Offset of records |
Note
If the method is called in the context of an application, the server additionally adds a filter for the current application.
In this case, only blocks created by the same application will be included in the response.
Code Examples
How to Use Examples in Documentation
Example of retrieving a list of blocks, where:
params.select— fields to return in the responseparams.filter— conditions for filtering recordsparams.order— sorting the resultparams.group— grouping fields
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"params": {
"select": ["ID", "NAME", "DATE_MODIFY"],
"filter": {"ACTIVE": "Y"},
"order": {"ID": "DESC"},
"group": ["ACTIVE"]
}
}' \
"https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.repo.getList.json"
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"params": {
"select": ["ID", "NAME", "DATE_MODIFY"],
"filter": {"ACTIVE": "Y"},
"order": {"ID": "DESC"},
"group": ["ACTIVE"]
},
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/landing.repo.getList.json"
try
{
const response = await $b24.callMethod(
'landing.repo.getList',
{
params: {
select: ['ID', 'NAME', 'DATE_MODIFY'],
filter: { ACTIVE: 'Y' },
order: { ID: 'DESC' },
group: ['ACTIVE']
}
}
);
console.info(response.getData().result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'landing.repo.getList',
[
'params' => [
'select' => ['ID', 'NAME', 'DATE_MODIFY'],
'filter' => ['ACTIVE' => 'Y'],
'order' => ['ID' => 'DESC'],
'group' => ['ACTIVE'],
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting landing repository list: ' . $e->getMessage();
}
BX24.callMethod(
'landing.repo.getList',
{
params: {
select: ['ID', 'NAME', 'DATE_MODIFY'],
filter: { ACTIVE: 'Y' },
order: { ID: 'DESC' },
group: ['ACTIVE']
}
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'landing.repo.getList',
[
'params' => [
'select' => ['ID', 'NAME', 'DATE_MODIFY'],
'filter' => ['ACTIVE' => 'Y'],
'order' => ['ID' => 'DESC'],
'group' => ['ACTIVE'],
],
]
);
echo '<pre>';
print_r($result);
echo '</pre>';
Response Handling
HTTP Status: 200
{
"result": [
{
"ID": "5",
"XML_ID": "ctx_full_1774873150158",
"APP_CODE": "bitrix.restapi",
"ACTIVE": "Y",
"NAME": "Context full test block",
"DESCRIPTION": "Check full fields from getList",
"SECTIONS": "cover,about",
"SITE_TEMPLATE_ID": null,
"PREVIEW": "https://www.bitrix24.com/images/b24_screen.png",
"MANIFEST": {
"block": {
"name": "Context full test block"
},
"nodes": {
".landing-block-node-text": {
"name": "Text",
"type": "text"
}
}
},
"CONTENT": "<section class=\"landing-block\"><div class=\"container\">Test</div></section>",
"CREATED_BY_ID": "577",
"MODIFIED_BY_ID": "577",
"DATE_CREATE": "30.03.2026 14:19:11",
"DATE_MODIFY": "30.03.2026 14:19:11"
}
],
"time": {
"start": 1774873153,
"finish": 1774873153.634216,
"duration": 0.6342160701751709,
"processing": 0,
"date_start": "2026-03-30T15:19:13+02:00",
"date_finish": "2026-03-30T15:19:13+02:00",
"operating_reset_at": 1774873753,
"operating": 0.11733078956604004
}
}
Returned Data
|
Name |
Description |
|
result |
List of blocks more details |
|
time |
Information about the request execution time |
Result Element Type
|
Name |
Description |
|
ID |
Identifier of the block |
|
XML_ID |
External code of the block |
|
Application code |
|
|
ACTIVE |
Activity status ( |
|
NAME |
Name of the block |
|
DESCRIPTION |
Description of the block |
|
SECTIONS |
Sections of the block |
|
Identifier of the site template |
|
|
PREVIEW |
Link to preview |
|
Manifest of the block. For more details on the manifest structure: Manifest format description. Example of a manifest in the method response: landing.block.getManifestFile |
|
|
CONTENT |
HTML of the block |
|
CREATED_BY_ID |
Identifier of the author |
|
MODIFIED_BY_ID |
Identifier of the user who modified the record |
|
DATE_CREATE |
Creation date in the format |
|
DATE_MODIFY |
Modification date in the format |
Error Handling
HTTP Status: 400
{
"error": "ERROR_ARGUMENT",
"error_description": "The value of an argument 'params' has an invalid type",
"argument": "params"
}
{
"error": "ACCESS_DENIED",
"error_description": "Insufficient permissions."
}
|
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 |
|
|
Insufficient permissions |
User did not pass general access checks |
|
|
The value of an argument 'params' has an invalid type |
The |
|
|
Internal error |
Error executing the method on the server side |
|
|
Insufficient scope for the token |
The token does not contain the |
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 a Custom Block to the Repository landing.repo.register
- Check Content for Dangerous Substrings landing.repo.checkContent
- Delete User Block landing.repo.unregister
- Custom Blocks: Overview of Methods