Get a List of Special Pages from landing.syspage.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:
landingWho can execute the method: a user with "read" access permission for the site
The method landing.syspage.get returns a list of special pages for the site.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the site. The site identifier can be obtained using the landing.site.getList method or from the result of the landing.site.add method |
|
active |
Return only pages that are not deleted and are active. The filter is considered enabled if |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"id": 1390,
"active": true
}' \
"https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.syspage.get.json"
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"id": 1390,
"active": true,
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/landing.syspage.get.json"
// 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
type SyspageItem = {
TYPE: string,
LANDING_ID: string,
TITLE: string,
DELETED: string,
ACTIVE: string,
}
// Shape of the payload returned in result (match the "response handling" section of the page)
type SyspageGetResult = Record<string, SyspageItem>
try {
const response = await $b24.actions.v2.call.make<SyspageGetResult>({
method: 'landing.syspage.get',
params: {
id: 1390,
active: true,
},
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(Object.keys(result).map(key => result[key]))
}
} 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 getSyspages() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'landing.syspage.get',
params: {
id: 1390,
active: true,
},
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(Object.keys(result).map(key => result[key]))
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', getSyspages)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.landing.syspage.get(
bitrix_id=1390,
).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.syspage.get',
[
'id' => 1390,
'active' => true,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting special pages: ' . $e->getMessage();
}
BX24.callMethod(
'landing.syspage.get',
{
id: 1390,
active: true
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'landing.syspage.get',
[
'id' => 1390,
'active' => true,
]
);
if (isset($result['error']))
{
echo 'Error: ' . $result['error_description'];
}
else
{
echo '<pre>';
print_r($result['result']);
echo '</pre>';
}
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "landing.syspage.get", b24.Params{
"id": 1390,
"active": true,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("landing.syspage.get: %w", err)
}
keys, ok := b24.Keys(res.Result)
if !ok {
return fmt.Errorf("expected an object in the response")
}
fmt.Println("fields in response:", len(keys))
Response Handling
HTTP Status: 200
{
"result": {
"mainpage": {
"TYPE": "mainpage",
"LANDING_ID": "711",
"TITLE": "Classic Store. Clothing",
"DELETED": "N",
"ACTIVE": "Y"
},
"catalog": {
"TYPE": "catalog",
"LANDING_ID": "713",
"TITLE": "Catalog",
"DELETED": "N",
"ACTIVE": "Y"
},
"personal": {
"TYPE": "personal",
"LANDING_ID": "717",
"TITLE": "Personal Section",
"DELETED": "N",
"ACTIVE": "Y"
},
"cart": {
"TYPE": "cart",
"LANDING_ID": "2261",
"TITLE": "Cart",
"DELETED": "N",
"ACTIVE": "Y"
},
"order": {
"TYPE": "order",
"LANDING_ID": "721",
"TITLE": "Order Checkout",
"DELETED": "N",
"ACTIVE": "Y"
},
"compare": {
"TYPE": "compare",
"LANDING_ID": "749",
"TITLE": "Comparison",
"DELETED": "N",
"ACTIVE": "Y"
},
"payment": {
"TYPE": "payment",
"LANDING_ID": "751",
"TITLE": "Order Payment",
"DELETED": "N",
"ACTIVE": "Y"
}
},
"time": {
"start": 1774349441,
"finish": 1774349441.726663,
"duration": 0.7266631126403809,
"processing": 0,
"date_start": "2026-03-24T13:50:41+01:00",
"date_finish": "2026-03-24T13:50:41+01:00",
"operating_reset_at": 1774350041,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The result of the request execution. The method returns an object with special pages grouped by type code (detailed description). If the site is not found or the user does not have "read" access permission for the site, the method will return If access to the site is available but no special pages are assigned, the method will return an empty object |
|
time |
Information about the request execution time |
Result Object
|
Name |
Description |
|
type code |
Object binding of the special page (detailed description) Key of the Possible values: |
Special Page Binding Object
|
Name |
Description |
|
TYPE |
Code of the special page type. The value matches the key in the |
|
LANDING_ID |
Identifier of the page designated as special for the site. Returned as a string in the response |
|
TITLE |
Title of the page |
|
DELETED |
Flag indicating if the page is deleted. Possible values: |
|
ACTIVE |
Flag indicating if the page is active. Possible values: |
Error Handling
HTTP Status: 400
{
"error": "MISSING_PARAMS",
"error_description": "Insufficient call parameters, missing: id"
}
|
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 |
|
|
The required parameter |
|
|
Access to the method call is denied: the user does not have access to the method or the |
|
|
Data type error in the |
|
|
Internal error during method execution |
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 |