Add Card to Block landing.block.addcard

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.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 -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"
        
// 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.block.addcard',
            params: {
              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>',
            },
            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('Card added successfully:', 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 addBlockCard() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'landing.block.addcard',
                params: {
                  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>',
                },
                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('Card added successfully:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', addBlockCard)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.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>',
            ).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.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>';
        }
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "landing.block.addcard", b24.Params{
        	"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 err != nil {
        	return fmt.Errorf("landing.block.addcard: %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": 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 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 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: 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