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
// 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
// Shape of each widget returned in result[]
type RepoWidgetItem = {
ID: string
XML_ID: string
APP_CODE: string
ACTIVE: 'Y' | 'N'
NAME: string
DESCRIPTION: string | null
SECTIONS: string
SITE_TEMPLATE_ID: string | null
PREVIEW: string
MANIFEST: Record<string, unknown>
CONTENT: string
CREATED_BY_ID: string
MODIFIED_BY_ID: string
DATE_CREATE: string
DATE_MODIFY: string
}
try {
// landing.repowidget.getlist 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<RepoWidgetItem[]>({
method: 'landing.repowidget.getlist',
params: {
params: {
select: ['ID', 'NAME'],
filter: {
'>ID': '1',
},
},
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('Widgets count on this page:', 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 getRepoWidgetList() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
// landing.repowidget.getlist 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: 'landing.repowidget.getlist',
params: {
params: {
select: ['ID', 'NAME'],
filter: {
'>ID': '1',
},
},
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('Widgets count on this page:', result.length, result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', getRepoWidgetList)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.landing.repowidget.getlist(
params={
"select": [
"ID",
"NAME",
],
"filter": {
">ID": "1",
},
},
).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(
'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: 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 |
|
|
|
The REST API is available only on commercial plans. 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 |