Mark a Block as Deleted `landing.landing.markdeletedblock`

If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to 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.markdeletedblock marks a page block as deleted but does not remove it from the database. The marked block can be restored using the method landing.landing.markundeletedblock.

If the page is already published, changes will be visible to visitors after the "Publish Changes" command in the interface or after calling the method landing.landing.publication.

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`	Identifier of the page. 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
block* `integer`	Identifier of the block. The block identifier can be obtained using the method landing.block.getList with the parameter `params.edit_mode = 1`
mark `boolean`	Indicator for marking the block as deleted. Default is `true`. If `false` is passed, the method will remove the deletion mark. This scenario typically uses landing.landing.markundeletedblock
preventHistory `boolean`	If `true`, the method does not add the action to the page change history. Default is `false`

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,
            "block": 6428
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.landing.markdeletedblock.json"

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

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

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

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

require_once('crest.php');
        
        $result = CRest::call(
            'landing.landing.markdeletedblock',
            [
                'lid' => 351,
                'block' => 6428,
            ]
        );
        
        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": 1773970028,
                "finish": 1773970028.158387,
                "duration": 0.1583869457244873,
                "processing": 0,
                "date_start": "2026-03-20T04:27:08+01:00",
                "date_finish": "2026-03-20T04:27:08+01:00",
                "operating_reset_at": 1773970628,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `boolean`	Result of marking the block. Returns `true` on successful execution
time `time`	Information about the request execution time

Error Handling

HTTP Status: 400

{
            "error": "BLOCK_NOT_FOUND",
            "error_description": "Block not found in the landing"
        }

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` or `block` is missing
`LANDING_NOT_EXIST`	Page with identifier `lid` not found or not accessible to the current user
`ACCESS_DENIED`	Insufficient permissions to call `landing` methods or to modify the block
`BLOCK_NOT_FOUND`	Block with identifier `block` does not exist or does not belong to page `lid`
`TYPE_ERROR`	Incorrect type passed in parameter `lid`, `block`, `mark`, or `preventHistory`

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

Hide Block on Page

Unmark Block as Deleted

Mark a Block as Deleted landing.landing.markdeletedblock

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