Publish the landing.landing.publication page

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

The method landing.landing.publication publishes the page and makes it active.

If the page is located in a folder, the method will publish that folder and all parent folders. After this, the site will become active.

For Knowledge Base pages, the method manages the visibility of the page: making it available or hidden from users.

Method Parameters

Required parameters are marked with *

Name
type

Description

scope
string

Internal scope of the landing. 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

Page identifier.

The page identifier can be obtained using the landing.landing.getList method, as well as from the results of the landing.landing.add, landing.landing.addByTemplate, and landing.landing.copy methods

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 351
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.landing.publication.json"

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 351,
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.landing.publication.json"

try
        {
        	const response = await $b24.callMethod(
        		'landing.landing.publication',
        		{
        			lid: 351
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.landing.publication',
                    [
                        'lid' => 351,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error publishing page: ' . $e->getMessage();
        }

BX24.callMethod(
            'landing.landing.publication',
            {
                lid: 351
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'landing.landing.publication',
            [
                'lid' => 351,
            ]
        );
        
        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": 1773794655,
                "finish": 1773794655.622698,
                "duration": 0.6226980686187744,
                "processing": 0,
                "date_start": "2026-03-18T03:44:15+01:00",
                "date_finish": "2026-03-18T03:44:15+01:00",
                "operating_reset_at": 1773795255,
                "operating": 0.2789781093597412
            }
        }

Returned Data

Name `type`	Description
result `boolean`	Publication result. Returns `true` on success
time `time`	Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "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
`MISSING_PARAMS`	Required parameter `lid` is missing
`LANDING_NOT_EXIST`	Page not found: the `lid` contains the identifier of a non-existent, deleted, or inaccessible page. For Knowledge Base pages, groups, and vibes, ensure that the `scope` parameter is provided
`PUBLIC_PAGE_REACHED`	The tariff plan has a limit on the number of published pages
`LANDING_PAYMENT_FAILED`	The page was added from an application; a subscription to Bitrix24 Marketplace is required for publication
`LANDING_PAYMENT_FAILED_BLOCK`	The page contains a block from an application; a subscription to Bitrix24 Marketplace is required for publication
`PUBLIC_SITE_REACHED`	The tariff plan has a limit on the number of created or published sites
`PUBLIC_SITE_REACHED_FREE`	Publishing sites is temporarily available only on paid plans
`PUBLIC_HTML_DISALLOWED[...]`	The tariff plan has a limit on adding custom HTML code. In square brackets, the method returns the type of object and its identifier: `S<site_id>` for the site or `L<landing_id>` for the page
`PHONE_NOT_CONFIRMED`	Phone number confirmation is required for publication
`EMAIL_NOT_CONFIRMED`	E-mail confirmation is required for publication
`URLCHECKER_FAIL`	Malicious content detected on the page
`LICENSE_EXPIRED`	Your product license has expired
`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

Moving a Page

Remove Page Blocks and Images

Publish the landing.landing.publication page

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning