Remove Card from Block landing.block.removecard

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.block.removecard removes a card from a block in the draft of a page.

This method only works with cards described in the cards key of the block manifest. If the page is already published, the change will be visible to visitors after publication through the interface or by using the landing.landing.publication method.

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 page. The page identifier can be obtained using the landing.landing.getlist method
block* `integer`	Identifier of the block in the editable version of the page. The block identifier can be obtained using the landing.block.getlist method with the parameter `params.edit_mode = 1`. If you pass the block identifier from the published version of the page, the method may return an error
selector* `string`	Selector of the card from the cards section of the block manifest The method searches for cards using this selector and removes the one whose index is specified after `@<index>`. The index is counted only among the found cards. The numbering starts from `0`: `.landing-block-card@0` removes the first found card, `.landing-block-card@2` removes the third found card. If the index is not specified and only `.landing-block-card` is passed, the method will return an error. If a blank or non-numeric value is specified after `@`, the method will interpret it as `0` and attempt to remove the first card. The method will also return an error if the selector is not present in the manifest, if there are no cards in the block with that selector, or if the index is out of bounds of the list
preventHistory `boolean`	Do not add the action to the page change history. Possible values: `true` - do not save the action in the change history, `false` - save the action in the 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,
            "selector": ".landing-block-card@0"
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.block.removecard.json"

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

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

try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.block.removecard',
                    [
                        'lid' => 351,
                        'block' => 6428,
                        'selector' => '.landing-block-card@0',
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error removing block card: ' . $e->getMessage();
        }

BX24.callMethod(
            'landing.block.removecard',
            {
                lid: 351,
                block: 6428,
                selector: '.landing-block-card@0'
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'landing.block.removecard',
            [
                'lid' => 351,
                'block' => 6428,
                'selector' => '.landing-block-card@0',
            ]
        );
        
        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": 1774505673,
                "finish": 1774505673.578092,
                "duration": 0.578092098236084,
                "processing": 0,
                "date_start": "2026-03-26T09:14:33+01:00",
                "date_finish": "2026-03-26T09:14:33+01:00",
                "operating_reset_at": 1774506273,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `boolean`	Result of the card removal. Returns `true` upon successful execution
time `time`	Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error": "CARD_NOT_FOUND",
            "error_description": "Card not found in the block"
        }

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`, `block`, or `selector` is missing
`LANDING_NOT_EXIST`	Page with identifier `lid` not found or not accessible to the current user
`ACCESS_DENIED`	User does not have permission to edit the page and block
`BLOCK_NOT_FOUND`	Block with identifier `block` not found on page `lid` or not accessible in the editable version of the page
`CARD_NOT_FOUND`	No card found in the block with the selector `selector`. This error is returned if the position is not specified, the selector is not in `manifest.cards`, no cards are found for it, or the index is out of bounds of the found cards

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

Clone Block Card

Update Block Content

Remove Card from Block landing.block.removecard

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