Remove Blocks and Clear Image File Bindings on Page landing.landing.removeEntities

Choose a tool for developing with an AI agent:

  • use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
  • use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

Scope: landing

Who can execute the method: a user with "edit" access permission for the site

The method landing.landing.removeEntities removes specified blocks and their associated images from the page. It can also clear file bindings for individual images without deleting the blocks themselves.

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 method landing.landing.getList, as well as from the results of the methods landing.landing.add, landing.landing.addByTemplate, and landing.landing.copy

data*
object

Set of objects to be deleted (detailed description).

If no blocks or images are specified for deletion, the page will remain unchanged. However, the method will still return true if the page exists

Parameter data

Name
type

Description

blocks
integer[]

Identifiers of the page blocks to be completely removed.

For each block, the method also deletes all associated images.

If the list includes blocks that are not on the page or blocks that the user cannot delete, the method will skip them. For an existing accessible page, it may return true even if some or all blocks from the list were not deleted

images
object[]

Pairs of block and image identifiers for deleting file bindings. The content of the block remains unchanged — use this when the image has already been removed from the block and you need to clear the remaining service record. (detailed description).

The method will not return a separate error in three cases: if the block is not found, if it is already specified in the blocks parameter, or if the image is not associated with this block

Parameter images

Required parameters are marked with *

Name
type

Description

block*
integer

Identifier of the block associated with the image file binding

image*
integer

Internal identifier of the image file binding (FILE_ID) associated with the block block.

For existing images, FILE_ID can be obtained using the method landing.block.getcontent. In the response, you need to find the HTML of the block in the content field and check the value of the data-fileid attribute for the required image

Code Examples

How to Use Examples in Documentation

This example demonstrates a mixed scenario: blocks from blocks are completely removed, while images elements clear file bindings for images in other blocks.

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 648,
            "data": {
              "blocks": [12167, 123],
              "images": [
                {
                  "block": 12269,
                  "image": 6866
                },
                {
                  "block": 12268,
                  "image": 6861
                }
              ]
            }
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.landing.removeEntities.json"
        
curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 648,
            "data": {
              "blocks": [12167, 123],
              "images": [
                {
                  "block": 12269,
                  "image": 6866
                },
                {
                  "block": 12268,
                  "image": 6861
                }
              ]
            },
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.landing.removeEntities.json"
        
// This snippet is an ES module: top-level await requires type="module" or a bundler.
        // $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
        import { Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        try {
          const response = await $b24.actions.v2.call.make<boolean>({
            method: 'landing.landing.removeEntities',
            params: {
              lid: 648,
              data: {
                blocks: [12167, 123],
                images: [
                  {
                    block: 12269,
                    image: 6866,
                  },
                  {
                    block: 12268,
                    image: 6861,
                  },
                ],
              },
            },
            requestId: Text.getUuidRfc4122()
          })
        
          // The payload is available only on a successful response
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('removeEntities result:', result)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }
        
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
        <script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function removeEntities() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'landing.landing.removeEntities',
                params: {
                  lid: 648,
                  data: {
                    blocks: [12167, 123],
                    images: [
                      {
                        block: 12269,
                        image: 6866,
                      },
                      {
                        block: 12268,
                        image: 6861,
                      },
                    ],
                  },
                },
                requestId: B24Js.Text.getUuidRfc4122()
              })
        
              // The payload is available only on a successful response
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('removeEntities result:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', removeEntities)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.landing.landing.remove_entities(
                lid=648,
                data={
                    "blocks": [
                        12167,
                        123,
                    ],
                    "images": [
                        {
                            "block": 12269,
                            "image": 6866,
                        },
                        {
                            "block": 12268,
                            "image": 6861,
                        },
                    ],
                },
            ).response
            result = bitrix_response.result
            print(result)
        except BitrixAPIError as error:
            print(
                "Bitrix API error",
                f"error: {error.error}",
                f"error_description: {error.error_description}",
                sep="\n",
            )
        except BitrixSDKException as error:
            print(f"Bitrix SDK error: {error.message}")
        except Exception as error:
            print(f"Unexpected error: {error}")
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.landing.removeEntities',
                    [
                        'lid' => 648,
                        'data' => [
                            'blocks' => [12167, 123],
                            'images' => [
                                [
                                    'block' => 12269,
                                    'image' => 6866,
                                ],
                                [
                                    'block' => 12268,
                                    'image' => 6861,
                                ],
                            ],
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error removing blocks and images: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'landing.landing.removeEntities',
            {
                lid: 648,
                data: {
                    blocks: [12167, 123],
                    images: [
                        {
                            block: 12269,
                            image: 6866
                        },
                        {
                            block: 12268,
                            image: 6861
                        }
                    ]
                }
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'landing.landing.removeEntities',
            [
                'lid' => 648,
                'data' => [
                    'blocks' => [12167, 123],
                    'images' => [
                        [
                            'block' => 12269,
                            'image' => 6866,
                        ],
                        [
                            'block' => 12268,
                            'image' => 6861,
                        ],
                    ],
                ],
            ]
        );
        
        if (isset($result['error']))
        {
            echo 'Error: ' . $result['error_description'];
        }
        else
        {
            echo '<pre>';
            print_r($result['result']);
            echo '</pre>';
        }
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "landing.landing.removeEntities", b24.Params{
        	"lid": 648,
        	"data": b24.Params{
        		"blocks": []int{12167, 123},
        		"images": []b24.Params{
        			{
        				"block": 12269,
        				"image": 6866,
        			},
        			{
        				"block": 12268,
        				"image": 6861,
        			},
        		},
        	},
        })
        if err != nil {
        	return fmt.Errorf("landing.landing.removeEntities: %w", err)
        }
        
        var ok bool
        if err := json.Unmarshal(res.Result, &ok); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        fmt.Println("done:", ok)
        

Response Handling

HTTP Status: 200

{
            "result": true,
            "time": {
                "start": 1773796328,
                "finish": 1773796328.413521,
                "duration": 0.41352105140686035,
                "processing": 0,
                "date_start": "2026-03-18T04:12:08+01:00",
                "date_finish": "2026-03-18T04:12:08+01:00",
                "operating_reset_at": 1773796928,
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
boolean

Result of the deletion, 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 consists of digits, Latin letters, and underscores. It may arrive empty — in that case only error_description shows the reason

error_description
string

Error message for the developer. Do not show it to the end user without processing

Possible Error Codes

Code

Description

MISSING_PARAMS

Required parameters are not set: lid, data, or both parameters are missing in the request

LANDING_NOT_EXIST

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

TYPE_ERROR

Data type error in the method call parameters

SYSTEM_ERROR

Internal error during method execution

Statuses and System Error Codes

HTTP Status: 4xx, 5xx

The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

429

OPERATION_TIME_LIMIT
Method is blocked due to operation time limit

The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit

401

NO_AUTH_FOUND
Wrong authorization data

The request contains no authorization data: neither an access token nor a webhook code was passed

401

INVALID_REQUEST
Https required

Methods are called over the HTTPS protocol only

401

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support

401

ACCESS_DENIED
REST is available only on commercial plans

REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — REST is available only by subscription

401

INVALID_CREDENTIALS
Invalid request credentials

No active webhook with the specified user identifier and secret code was found

404

ERROR_METHOD_NOT_FOUND
Method not found!

No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope

401

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

The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with provided by the access token

401

expired_token
The access token provided has expired

The access token has expired

401

user_access_error
The user does not have access to the application

The application is installed, but the Bitrix24 administrator has granted access to it only to specific users

403

PORTAL_DELETED
Portal was deleted

The public part of the site is closed. To open it 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