Copy Page landing.landing.copy

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" access permission for the site

The method landing.landing.copy copies a page and returns the identifier of the new page. This method can also copy a page marked as deleted and located in the trash.

Method Parameters

Required parameters are marked with *

Name
type

Description

scope
string

Internal scope of landings. 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 source page.

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

toSiteId
integer

Identifier of the target site. If this parameter is not provided or set to 0, the copy will be created in the same site where the source page is located.

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

toFolderId
integer

Identifier of the target folder. If this parameter is provided, the copy is created in the specified folder. The folder must belong to the target site toSiteId.

If this parameter is not provided or set to 0, the copy is created in the root of the target site. If the folder is not found or belongs to another site, the method does not return an error and creates the copy in the root of the target site.

The folder identifier can be obtained using the method landing.site.getFolders

skipSystem
boolean

Flag for copying the system attribute of the page. Default is false.

If set to true, the new page is created as non-system (SYS = N)

Code Examples

How to Use Examples in Documentation

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 1688,
            "toSiteId": 305,
            "toFolderId": 95
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.landing.copy.json"
        
curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 1688,
            "toSiteId": 305,
            "toFolderId": 95,
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.landing.copy.json"
        
try
        {
        	const response = await $b24.callMethod(
        		'landing.landing.copy',
        		{
        			lid: 1688,
        			toSiteId: 305,
        			toFolderId: 95
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.error(error);
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.landing.copy',
                    [
                        'lid' => 1688,
                        'toSiteId' => 305,
                        'toFolderId' => 95,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error copying landing page: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'landing.landing.copy',
            {
                lid: 1688,
                toSiteId: 305,
                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.copy',
            [
                'lid' => 1688,
                'toSiteId' => 305,
                '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": 2237,
            "time": {
                "start": 1773706491,
                "finish": 1773706492.91233,
                "duration": 1.912329912185669,
                "processing": 1,
                "date_start": "2026-03-17T03:14:51+01:00",
                "date_finish": "2026-03-17T03:14:52+01:00",
                "operating_reset_at": 1773707091,
                "operating": 0.9924919605255127
            }
        }
        

Returned Data

Name
type

Description

result
integer

Identifier of the created copy of the page

time
time

Information about the execution time of the request

Error Handling

HTTP Status: 400 Bad Request

{
            "error": "LANDING_NOT_EXIST",
            "error_description": "Landing 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

LANDING_NOT_EXIST

Landing not found. If the source page does not exist or is not accessible to the current user. Being in the trash does not trigger this error by itself

SITE_NOT_FOUND

Site not found. If toSiteId points to a non-existent site

ACCESS_DENIED

Access to create the page is denied. If the user does not have "edit" access permission for the site

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