Get the list of widgets landing.repowidget.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: any user
The method landing.repowidget.getlist returns a list of widgets for the current application, filtered by the specified criteria.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
params* |
Array of fields to retrieve the list of widgets |
Parameter params
Required parameters are marked with *
|
Name |
Description |
|
select |
Array with the list of fields to be selected. If not provided or an empty array is passed, all available widgets will be selected |
|
filter |
Object for filtering the selected records in the format Possible values for An additional prefix can be specified for the key to clarify the filter behavior. Possible prefix values:
|
|
group |
Array for grouping widgets. Grouping can be done by fields of the widget |
|
order |
Object for sorting the selected records in the format Possible values for Possible values for
|
Fields field
Fields of the widget object. Present in the request and response.
|
Name |
Description |
|
ID |
Widget identifier |
|
XML_ID |
Unique record code |
|
APP_CODE |
Code of the current application |
|
ACTIVE |
Widget activity. Accepts values:
|
|
NAME |
Widget name |
|
DESCRIPTION |
Widget description |
|
SECTIONS |
Code of the section where the widget will be added |
|
PREVIEW |
URL of the widget cover image for the widget selection slider |
|
WIDGET_PARAMS |
Parameters for the Vue template engine |
|
CONTENT |
Widget markup using Vue constructs |
|
MANIFEST |
Widget manifest |
|
CREATED_BY_ID |
Identifier of the user who created the record |
|
MODIFIED_BY_ID |
Identifier of the user who modified the record |
|
DATE_CREATE |
Creation date |
|
DATE_MODIFY |
Modification date |
|
SITE_TEMPLATE_ID |
Binding of the widget to a specific site template. Only for on-premise Bitrix24! |
Code Examples
How to Use Examples in Documentation
// callListMethod: Retrieves all data at once. Use only for small selections (< 1000 items) due to high memory usage.
try {
const response = await $b24.callListMethod(
'landing.repowidget.getlist',
{
params: {
select: [
'ID', 'NAME'
],
filter: {
'>ID': '1'
}
}
},
(progress) => { console.log('Progress:', progress) }
)
const items = response.getData() || []
for (const entity of items) { console.log('Entity:', entity) }
} catch (error) {
console.error('Request failed', error)
}
// fetchListMethod: Retrieves data in parts using an iterator. Use it for large data volumes to optimize memory usage.
try {
const generator = $b24.fetchListMethod('landing.repowidget.getlist', {
params: {
select: [
'ID', 'NAME'
],
filter: {
'>ID': '1'
}
}
}, 'ID')
for await (const page of generator) {
for (const entity of page) { console.log('Entity:', entity) }
}
} catch (error) {
console.error('Request failed', error)
}
// callMethod: Manually controls pagination through the start parameter. Use it for precise control of request batches. For large datasets, it is less efficient than fetchListMethod.
try {
const response = await $b24.callMethod('landing.repowidget.getlist', {
params: {
select: [
'ID', 'NAME'
],
filter: {
'>ID': '1'
}
}
}, 0)
const result = response.getData().result || []
for (const entity of result) { console.log('Entity:', entity) }
} catch (error) {
console.error('Request failed', error)
}
try {
$response = $b24Service
->core
->call(
'landing.repowidget.getlist',
[
'params' => [
'select' => [
'ID', 'NAME'
],
'filter' => [
'>ID' => '1'
]
]
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting repowidget list: ' . $e->getMessage();
}
BX24.callMethod(
'landing.repowidget.getlist',
{
params: {
select: [
'ID', 'NAME'
],
filter: {
'>ID': '1'
}
}
},
function(result)
{
if(result.error())
console.error(result.error());
else
console.info(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'landing.repowidget.getList',
[
'params' => [
'select' => ['ID', 'NAME'],
'filter' => [
'>ID' => '1'
]
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": [
{
"ID": "4",
"XML_ID": "my_widget",
"APP_CODE": "app.code",
"ACTIVE": "Y",
"NAME": "My widget",
"DESCRIPTION": null,
"SECTIONS": "widgets_company_life",
"SITE_TEMPLATE_ID": null,
"PREVIEW": "https://my-app.com/main_preview.jpg",
"MANIFEST": {
"block": {
"type": [
"mainpage"
],
"subtype": [
"widgetvue"
],
"subtype_params": {
"rootNode": ".w-container",
"demoData": {
"desc": "JustSome widget data",
"count": "420"
},
"handler": "https://my-app.com/vibe.php",
"style": "https://my-app.com/vibe.css",
"lang": {
"de": {
"W_TITLE": "People and their age",
"W_EMPTY": "No people"
},
"en": {
"W_TITLE": "Widget title",
"W_EMPTY": "Empty!"
}
}
}
}
},
"CONTENT": "<div class=\"w-container\">{{desc}}</div>",
"CREATED_BY_ID": "1",
"MODIFIED_BY_ID": "1",
"DATE_CREATE": "10.10.2024 15:55:30",
"DATE_MODIFY": "16.10.2024 16:12:57"
}
],
"time": {
"start": 1729162340.81773,
"finish": 1729162344.800994,
"duration": 3.9832639694213867,
"processing": 3.8990869522094727,
"date_start": "2024-10-17T15:52:20+01:00",
"date_finish": "2024-10-17T15:52:24+01:00",
"operating": 3.899045944213867
}
}
Returned Data
|
Name |
Description |
|
result |
Array of widgets. Each element of the array is an object, permissible fields are described above. |
|
time |
Information about the execution time of the request |
Error Handling
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 Widget to Start Page: the Vibe landing.repowidget.register
- Unregister Widget for Vibe landing.repowidget.unregister
- Enable Debug Mode landing.repowidget.debug