Move Page landing.landing.move
Scope:
landingWho can execute the method: a user with "edit" and "delete" permissions on the site
The method landing.landing.move moves a page to another site or folder.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
lid* |
The identifier of the page to be moved. The page identifier can be obtained using the method landing.landing.getList, as well as from the results of the methods landing.landing.add, landing.landing.addByTemplate, and landing.landing.copy |
|
toSiteId |
The identifier of the destination site. If the parameter is not provided or equals The site identifier can be obtained using the method landing.site.getList |
|
toFolderId |
The identifier of the destination folder in the target site. If the parameter is not provided or equals If you are moving the page to a folder, that folder must belong to the same site. You cannot move a page to another site and to a folder of that site in one go — the method will return an error. In this case, first move the page to the desired site, and then in a separate call — to the desired folder. The folder identifier can be obtained using the method landing.site.getFolders |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"lid": 2227,
"toSiteId": 157,
"toFolderId": 95
}' \
"https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.landing.move.json"
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"lid": 2227,
"toSiteId": 157,
"toFolderId": 95,
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/landing.landing.move.json"
try
{
const response = await $b24.callMethod(
'landing.landing.move',
{
lid: 2227,
toSiteId: 157,
toFolderId: 95
}
);
const result = response.getData().result;
console.info(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'landing.landing.move',
[
'lid' => 2227,
'toSiteId' => 157,
'toFolderId' => 95,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . var_export($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error moving page: ' . $e->getMessage();
}
BX24.callMethod(
'landing.landing.move',
{
lid: 2227,
toSiteId: 157,
toFolderId: 95
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'landing.landing.move',
[
'lid' => 2227,
'toSiteId' => 157,
'toFolderId' => 95,
]
);
if (isset($result['error']))
{
echo 'Error: ' . $result['error_description'];
}
else
{
echo '<pre>';
print_r($result['result']);
echo '</pre>';
}
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1773789756,
"finish": 1773789756.4837,
"duration": 0.4837000370025635,
"processing": 0,
"date_start": "2026-03-18T02:22:36+01:00",
"date_finish": "2026-03-18T02:22:36+01:00",
"operating_reset_at": 1773790356,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The result of the move. Returns |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error": "FOLDER_NOT_FOUND",
"error_description": "Folder 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 |
|
|
Required parameter |
|
|
Page not found, deleted, or unavailable to the current user |
|
|
Insufficient permissions to modify the target site |
|
|
Insufficient permissions to delete the source page |
|
|
Target folder not found or inaccessible for verification. This error also occurs if you attempt to change the page's site and provide a folder from another site in one call |
|
|
Data type error in the method call parameters |
|
|
Internal error while executing the method |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Add Page or Folder landing.landing.add
- Add Page by Template landing.landing.addByTemplate
- Copy Page landing.landing.copy
- Delete Page landing.landing.delete
- Get a List of Pages landing.landing.getList
- Mark Page as Deleted landing.landing.markDelete
- Update Page landing.landing.update