Add Card to Block landing.block.addcard

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

The method landing.block.addcard adds a card to a block in the draft of a page.

This method works with cards described in the cards key of the block manifest. If the page is already published, changes will be visible to visitors after re-publishing through the interface or 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`
selector* `string`	Selector of the card from the key `cards` of the block manifest After the selector, you can specify an index using `@<index>`. For example, `@0` will add a new card after the first found one, while `@2` will add it after the third. If an index is specified, the method inserts the new card after the selected one. If this card is the last one, the new card will appear at the end of the container. If no index is specified, the method takes the first card matching this selector and inserts the new card at the beginning of the container. After adding a card, the indices change. If you are adding multiple cards in succession, specify a new index in `selector` for each subsequent call. If the selector is not present in the manifest, there are no cards in the block for this selector, or a non-existent index is specified, the method will return an error. For more details on card selectors and the structure of the manifest, refer to the article Block Manifest
content* `string`	HTML of the new card. If you need to use existing markup from the block as a basis, obtain the HTML using the landing.block.getcontent method and use the card structure from the current block. If an empty string is passed or the content becomes empty after filtering, the method will behave like landing.block.clonecard and create a copy of the card specified in `selector`
preventHistory `boolean`	Do not add the action to the page change history. Possible values: `true` - do not save the action in history, `false` - save the action in 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-node-menu-list-item@0",
            "content": "<li class=\"landing-block-node-menu-list-item nav-item\"><a href=\"#services\" class=\"landing-block-node-menu-list-item-link nav-link\">Services</a></li>"
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.block.addcard.json"

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 351,
            "block": 6428,
            "selector": ".landing-block-node-menu-list-item@0",
            "content": "<li class=\"landing-block-node-menu-list-item nav-item\"><a href=\"#services\" class=\"landing-block-node-menu-list-item-link nav-link\">Services</a></li>",
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.block.addcard.json"

try
        {
            const response = await $b24.callMethod(
                'landing.block.addcard',
                {
                    lid: 351,
                    block: 6428,
                    selector: '.landing-block-node-menu-list-item@0',
                    content: '<li class="landing-block-node-menu-list-item nav-item"><a href="#services" class="landing-block-node-menu-list-item-link nav-link">Services</a></li>'
                }
            );
        
            const result = response.getData().result;
            console.info(result);
        }
        catch (error)
        {
            console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.block.addcard',
                    [
                        'lid' => 351,
                        'block' => 6428,
                        'selector' => '.landing-block-node-menu-list-item@0',
                        'content' => '<li class="landing-block-node-menu-list-item nav-item"><a href="#services" class="landing-block-node-menu-list-item-link nav-link">Services</a></li>',
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error adding block card: ' . $e->getMessage();
        }

BX24.callMethod(
            'landing.block.addcard',
            {
                lid: 351,
                block: 6428,
                selector: '.landing-block-node-menu-list-item@0',
                content: '<li class="landing-block-node-menu-list-item nav-item"><a href="#services" class="landing-block-node-menu-list-item-link nav-link">Services</a></li>'
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'landing.block.addcard',
            [
                'lid' => 351,
                'block' => 6428,
                'selector' => '.landing-block-node-menu-list-item@0',
                'content' => '<li class="landing-block-node-menu-list-item nav-item"><a href="#services" class="landing-block-node-menu-list-item-link nav-link">Services</a></li>',
            ]
        );
        
        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": 1774524862,
                "finish": 1774524862.61318,
                "duration": 0.6131799221038818,
                "processing": 0,
                "date_start": "2026-03-26T14:34:22+01:00",
                "date_finish": "2026-03-26T14:34:22+01:00",
                "operating_reset_at": 1774525462,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `boolean`	Result of adding the card. Returns `true` upon successful execution; the identifier of the new card is not returned in the response
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`, `selector`, or `content` 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 site
`BLOCK_NOT_FOUND`	Block with identifier `block` not found on page `lid` or not accessible in the draft of the page
`CARD_NOT_FOUND`	No card found in the block for selector `selector`

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

Update Block Node Attributes

Change Anchor Symbol Code

Add Card to Block landing.block.addcard

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