Change Attributes of Block Elements landing.block.updateattrs

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