Publish the site landing.site.publication

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

The method landing.site.publication publishes the site and its pages.
If a page is inactive (ACTIVE = "N"), it remains unpublished (PUBLIC = "N"). When the method is called, non-deleted site folders (DELETED = "N") are also activated.

For the Knowledge Base, the method manages the visibility of the site and its pages for users.

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)

id*
integer

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

Code Examples

How to Use Examples in Documentation

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "id": 1688
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.site.publication.json"
        
curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "id": 1688,
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.site.publication.json"
        
try
        {
        	const response = await $b24.callMethod(
        		'landing.site.publication',
        		{
        			id: 1688
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.error(error);
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.site.publication',
                    [
                        'id' => 1688,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error publishing site: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'landing.site.publication',
            {
                id: 1688
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'landing.site.publication',
            [
                'id' => 1688,
            ]
        );
        
        if (isset($result['error']))
        {
            echo 'Error: ' . $result['error_description'];
        }
        else
        {
            echo '<pre>';
            print_r($result['result']);
            echo '</pre>';
        }
        

Response Handling

HTTP Status: 200

{
            "result": 157,
            "time": {
                "start": 1773285117,
                "finish": 1773285117.990578,
                "duration": 0.9905779361724854,
                "processing": 0,
                "date_start": "2026-03-12T06:11:57+03:00",
                "date_finish": "2026-03-12T06:11:57+03:00",
                "operating_reset_at": 1773285717,
                "operating": 0.13959693908691406
            }
        }
        

Returned Data

Name
type

Description

result
integer

Identifier of the published site

time
time

Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error": "ACCESS_DENIED",
            "error_description": "Publishing the site is not allowed."
        }
        

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 id is missing

ACCESS_DENIED

Publishing the site is not allowed

PHONE_NOT_CONFIRMED

Phone number confirmation is required for publishing

EMAIL_NOT_CONFIRMED

E-mail confirmation is required for publishing

URLCHECKER_FAIL

Malicious content detected on the page

PUBLIC_PAGE_REACHED

There is a limit on the number of published pages in the tariff plan

LANDING_PAYMENT_FAILED

The page was added from an application; a subscription to Bitrix24 Marketplace is required for publishing

LANDING_PAYMENT_FAILED_BLOCK

The block was added from an application; a subscription to Bitrix24 Marketplace is required for publishing

PUBLIC_SITE_REACHED

There is a limit on the number of created or published sites in the tariff plan

PUBLIC_SITE_REACHED_FREE

Publishing sites is temporarily available only on paid plans

PUBLIC_HTML_DISALLOWED[...]

There is a limit on adding custom HTML code in the tariff plan

LICENSE_EXPIRED

Your product license has expired

TYPE_ERROR

Data type error in the 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