Change Attributes of Block Elements landing.block.updateattrs

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.updateattrs updates the attributes of HTML elements within a block in the draft of a page.

This method does not change the text, the entire HTML code of the block, or styles. It only updates the attribute values of already existing elements, such as href, target, alt, title, data-*, and aria-*.

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 version of the page for editing. 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
data* `object`	Set of attributes to update (detailed description)

Parameter data

Key
type

Description

object

The key must match the CSS selector from the block's manifest. The value must be an object of the form { '<attribute>': <value> }.

The method finds elements by the selector and assigns them new attribute values. If the selector appears multiple times, you can specify the position using @, for example, .landing-block-node-text@1. Positions are numbered starting from 0.

If the position is not specified, the method updates all found elements with that selector

The allowed selectors and attributes are taken from the style.nodes, attrs, cards, and style.block sections of the block's manifest. You can check them using the landing.block.getmanifest method. If you are checking a block from the version of the page for editing, pass the parameter params.edit_mode = 1 to landing.block.getmanifest.

If the required attribute is described only in the nodes section of the manifest, use landing.block.updatenodes. If the selector or attribute is not present in the supported sections of the manifest, the method will ignore it without an error.

Use the method when you need to change the settings of an element through attributes, rather than its content. For example, you can change the link of a button, the target for opening in a new tab, the alt for an image, or data-* for a form.

For instance, in the CRM form block, the method allows you to change the data-b24form attribute of the .bitrix24forms element and connect a different form. The acceptable values for such an attribute should be taken from the manifest of the specific block.

Strings, numbers, and boolean values are saved as HTML attributes. If you pass an array or object, the method converts them into a JSON string. The data format must match the type of the attribute specified in the block's manifest. The method does not check whether the passed value is suitable for the logic of a specific block, so it is better to refer to the manifest. Examples of formats for different types of attributes can be found in the article Attribute Types.

For example, if a repeating element in the manifest allows the attribute data-test-checkbox, the request for the second card might look like this:

{
            ".container-fluid@1": {
                "data-test-checkbox": [1, 2, 3]
            }
        }

For example, if there is a button in the block:

<a class="landing-block-node-button" href="/old/" target="_self">Buy</a>

If you pass the following data:

{
            ".landing-block-node-button": {
                "href": "/catalog/",
                "target": "_blank"
            }
        }

The button text will not change, but the method will update its attributes. After the call, the button will link to /catalog/ and open in a new tab.

To change the attributes of the block wrapper, pass the actual identifier in the format #block<blockId>, for example, #block6058. You cannot pass #wrapper as a key in data: such a request will not work.

For dynamic block and component parameters, use landing.block.updatenodes.

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": 313,
            "block": 6134,
            "data": {
              ".bitrix24forms": {
                "data-b24form": "#crmFormInline45",
                "data-b24form-use-style": "N"
              }
            }
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.block.updateattrs.json"

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 313,
            "block": 6134,
            "data": {
              ".bitrix24forms": {
                "data-b24form": "#crmFormInline45",
                "data-b24form-use-style": "N"
              }
            },
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.block.updateattrs.json"

try
        {
        	const response = await $b24.callMethod(
        		'landing.block.updateattrs',
        		{
        			lid: 313,
        			block: 6134,
        			data: {
        				'.bitrix24forms': {
        					'data-b24form': '#crmFormInline45',
        					'data-b24form-use-style': 'N'
        				}
        			}
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.block.updateattrs',
                    [
                        'lid' => 313,
                        'block' => 6134,
                        'data' => [
                            '.bitrix24forms' => [
                                'data-b24form' => '#crmFormInline45',
                                'data-b24form-use-style' => 'N',
                            ],
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error updating block attributes: ' . $e->getMessage();
        }

BX24.callMethod(
            'landing.block.updateattrs',
            {
                lid: 313,
                block: 6134,
                data: {
                    '.bitrix24forms': {
                        'data-b24form': '#crmFormInline45',
                        'data-b24form-use-style': 'N'
                    }
                }
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'landing.block.updateattrs',
            [
                'lid' => 313,
                'block' => 6134,
                'data' => [
                    '.bitrix24forms' => [
                        'data-b24form' => '#crmFormInline45',
                        'data-b24form-use-style' => 'N',
                    ],
                ],
            ]
        );
        
        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": 1774442460,
                "finish": 1774442460.28751,
                "duration": 0.2875099182128906,
                "processing": 0,
                "date_start": "2026-03-25T11:01:00+01:00",
                "date_finish": "2026-03-25T11:01:00+01:00",
                "operating_reset_at": 1774443060,
                "operating": 0.09410285949707031
            }
        }

Returned Data

Name `type`	Description
result `boolean`	The result of updating the attributes. Upon successful execution, the method returns `true`
time `time`	Information about the execution time of the request

Error Handling

HTTP status: 400

{
            "error": "BLOCK_NOT_FOUND",
            "error_description": "Block not found"
        }

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 `data` is missing
`ACCESS_DENIED`	Insufficient permissions to edit the site
`LANDING_NOT_EXIST`	The page with identifier `lid` is not found or is not accessible to the current user
`BLOCK_NOT_FOUND`	The block with identifier `block` is not found on the page `lid` or is not accessible in the version of the page for editing

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 Content

Add Card with Updated Content

Change Attributes of Block Elements landing.block.updateattrs

Method ParametersMethod Parameters

Parameter dataParameter data

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