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

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 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 (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

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"

try
        {
        	const response = await $b24.callMethod(
        		'landing.block.changeNodeName',
        		{
        			lid: 311,
        			block: 6058,
        			data: {
        				'.landing-block-node-title@0': 'h1',
        				'.landing-block-node-text@2': 'p'
        			},
        			preventHistory: true
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.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>';
        }

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 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
`LANDING_NOT_EXIST`	Page with identifier `lid` not found or not accessible to the current user
`ACCESS_DENIED`	Insufficient rights to edit the site
`TYPE_ERROR`	Parameter `data` is passed in an incorrect format or tag value is not a string

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

Change Anchor Symbol Code

Get Block Content from Repository

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

Method ParametersMethod Parameters

Parameter dataParameter data

Allowed Tag ValuesAllowed Tag Values

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