Change HTML Tag of a Block Element landing.block.changeNodeName

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 containing the page.

The method landing.block.changeNodeName changes the HTML tag of a block element in the draft of a page.

If the page is already published, changes will be visible to visitors after re-publishing through the interface or using the method landing.landing.publication.

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 method landing.landing.getList

block*
integer

Identifier of the block in the draft of the page

The block identifier can be obtained using the method landing.block.getlist with the parameter params.edit_mode = 1.

Use the identifier specifically from the draft of the page. If you pass the identifier of a block from the published version or another version of the page, the changes will not be applied

data*
object

Set of changes for block elements (detailed description)

preventHistory
boolean

If true is passed, the method will not add the action to the page change history

By default, it is false

Parameter data

The data parameter is passed in the format:

{
            selector_1: tag_1,
            selector_2: tag_2,
            ...,
            selector_n: tag_n
        }
        

where:

  • selector_n — selector of the element from the block manifest
  • tag_n — new name of the HTML tag

Key
type

Description


string

New name of the HTML tag for the element specified in the key

The key must match the selector of the element from the block manifest.

For repeating elements, you can specify the position after the selector using @, for example, .landing-block-node-title@1. Positions are numbered starting from 0.

If the position is not specified, the method will change the first found element, which means it will work the same as @0.

If you pass a selector that does not exist in the block manifest or specify a position that does not exist in the block, the method will complete without an error but will not change anything.

Allowed Tag Values

The tag value is passed as a string. Leading and trailing spaces in the value are removed, and case is ignored.

Value

Description

h1

First-level heading

h2

Second-level heading

h3

Third-level heading

h4

Fourth-level heading

h5

Fifth-level heading

h6

Sixth-level heading

div

Block container

p

Paragraph

a

Link

span

Inline container

For example, if you pass H1, the method will save the tag as h1. If another value is passed, the method will use div.

Code Examples

How to Use Examples in Documentation

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 311,
            "block": 6058,
            "data": {
              ".landing-block-node-title@0": "h1",
              ".landing-block-node-text@2": "p"
            },
            "preventHistory": true
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.block.changeNodeName.json"
        
curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "lid": 311,
            "block": 6058,
            "data": {
              ".landing-block-node-title@0": "h1",
              ".landing-block-node-text@2": "p"
            },
            "preventHistory": true,
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.block.changeNodeName.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.changeNodeName',
            params: {
              lid: 311,
              block: 6058,
              data: {
                '.landing-block-node-title@0': 'h1',
                '.landing-block-node-text@2': 'p',
              },
              preventHistory: true,
            },
            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('Node name changed:', 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 changeNodeName() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'landing.block.changeNodeName',
                params: {
                  lid: 311,
                  block: 6058,
                  data: {
                    '.landing-block-node-title@0': 'h1',
                    '.landing-block-node-text@2': 'p',
                  },
                  preventHistory: true,
                },
                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('Node name changed:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', changeNodeName)
        </script>
        
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.landing.block.change_node_name(
                lid=311,
                block=6058,
                data={
                    ".landing-block-node-title@0": "h1",
                    ".landing-block-node-text@2": "p",
                },
                prevent_history=True,
            ).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.changeNodeName',
                    [
                        'lid' => 311,
                        'block' => 6058,
                        'data' => [
                            '.landing-block-node-title@0' => 'h1',
                            '.landing-block-node-text@2' => 'p',
                        ],
                        'preventHistory' => true,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error changing node name: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'landing.block.changeNodeName',
            {
                lid: 311,
                block: 6058,
                data: {
                    '.landing-block-node-title@0': 'h1',
                    '.landing-block-node-text@2': 'p'
                },
                preventHistory: true
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'landing.block.changeNodeName',
            [
                'lid' => 311,
                'block' => 6058,
                'data' => [
                    '.landing-block-node-title@0' => 'h1',
                    '.landing-block-node-text@2' => 'p',
                ],
                'preventHistory' => true,
            ]
        );
        
        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.changeNodeName", b24.Params{
        	"lid":   311,
        	"block": 6058,
        	"data": b24.Params{
        		".landing-block-node-title@0": "h1",
        		".landing-block-node-text@2":  "p",
        	},
        	"preventHistory": true,
        })
        if err != nil {
        	return fmt.Errorf("landing.block.changeNodeName: %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": 1774510990,
                "finish": 1774510990.1045,
                "duration": 0.10450005531311035,
                "processing": 0,
                "date_start": "2026-03-26T10:43:10+02:00",
                "date_finish": "2026-03-26T10:43:10+02:00",
                "operating_reset_at": 1774511590,
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
boolean

Result of the tag change. If the request is successful, the method returns true

time
time

Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error": "ACCESS_DENIED",
            "error_description": "Operation is forbidden"
        }
        

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

LANDING_NOT_EXIST

Page with identifier lid not found or not accessible to the current user

ACCESS_DENIED

Insufficient rights to edit the site

BLOCK_NOT_FOUND

The block with identifier block was not found on page lid or is not available in the editable page version

NODES_NOT_FOUND

No block changes are passed in the data parameter

TYPE_ERROR

An incorrect type of one of the method parameters was passed, for example data in an invalid format

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