Move Page landing.landing.move

If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect the MCP server so that the assistant can utilize the official REST documentation.

Scope: landing

Who 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
type

Description

scope
string

Internal scope of the landing pages. It is not related to the REST scope landing in the method name.

The value of scope must correspond to the type of site (detailed description)

lid*
integer

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
integer

Identifier of the destination site.

If the parameter is not provided or equals 0, the current site of the page is used.

The site identifier can be obtained using the method landing.site.getList

toFolderId
integer

Identifier of the destination folder in the target site.

If the parameter is not provided or equals 0, the page is moved to the root of the target site.

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 such a 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
type

Description

result
boolean

Result of the move. Returns true on success

time
time

Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error": "FOLDER_NOT_FOUND",
            "error_description": "Folder not found"
        }
        

Name
type

Description

error
string

String error code. It may consist of digits, Latin letters, and underscores

error_description
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

MISSING_PARAMS

Required parameter lid is not provided

LANDING_NOT_EXIST

Page not found, deleted, or unavailable to the current user

ACCESS_DENIED

Insufficient permissions to modify the target site

DELETE_ACCESS_DENIED

Insufficient permissions to delete the source page

FOLDER_NOT_FOUND

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

TYPE_ERROR

Data type error in method call parameters

SYSTEM_ERROR

Internal error during method execution

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

405

ERROR_BATCH_METHOD_NOT_ALLOWED
Method is not allowed for batch usage

The current method is not permitted for calls using batch

400

ERROR_BATCH_LENGTH_EXCEEDED
Max batch length exceeded

The maximum length of parameters passed to the batch method has been exceeded

401

NO_AUTH_FOUND
Wrong authorization data

Invalid access token or webhook code

400

INVALID_REQUEST
Https required

The HTTPS protocol is required for method calls

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is only available on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user associated with the access token or webhook used to call the method lacks the necessary permissions

404

ERROR_MANIFEST_IS_NOT_AVAILABLE
Manifest is not available

The manifest is not available

403

insufficient_scope
The request requires higher privileges than provided by the webhook token

The request requires higher privileges than those provided by the webhook token

401

expired_token
The access token provided has expired

The provided access token has expired

403

user_access_error
The user does not have access to the application

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

500

PORTAL_DELETED
Portal was deleted

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