Update Cards in landing.block.updateCards
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:
landingWho can execute the method: a user with "edit" access permission for the site
The method landing.block.updateCards updates a set of cards in a block and the nodes within those cards in the draft of the 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 publication through the interface or by using the landing.landing.publication method.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
scope |
Internal scope of landings. It is not related to the REST scope The value of |
|
lid* |
Identifier of the page. The page identifier can be obtained using the landing.landing.getlist method |
|
block* |
Identifier of the block in the draft of the page. The block identifier can be obtained using the landing.block.getlist method with the parameter |
|
data* |
Set of changes for the block cards (detailed description) |
Parameter data
|
Key |
Description |
|
Card selector from the cards section of the block manifest. The value describes the final set of cards for this selector and the changes to their nodes (detailed description). To find available card selectors and presets for a specific block, retrieve the manifest using the landing.block.getmanifest method |
Object
|
Name |
Description |
|
source |
Defines the final order and number of cards (detailed description) |
|
values |
Updates nodes within cards after applying |
Element of the source array
|
Name |
Description |
|
type |
Type of the card source. Possible values: Default - |
|
Value of the card source. For For |
If the source element does not contain type, the method uses the value card. If value is not provided, the method uses index 0.
To create a new card from a preset, specify type with the value preset and pass the preset code from the block manifest in value. For example:
"source": [
{
"type": "card",
"value": 0
},
{
"type": "preset",
"value": "preset_code"
}
]
Element of the values array
Each element of the values array must be an object that contains one or more node changes.
|
Key |
Description |
|
Node selector within the card with position indicated by The position is numbered from The format of the value is the same as the One object in the |
If an element of the values array is not an object, the method will skip it without error. For example, in one element of the array, you can change multiple cards at once:
"values": [
{
".landing-block-node-title@0": "First Card",
".landing-block-node-title@1": "Card from Preset"
}
]
For detailed information on value formats for different node types, refer to the article landing.block.updatenodes and the overview Node Types.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"lid": 311,
"block": 6058,
"data": {
".landing-block-card": {
"source": [
{
"type": "card",
"value": 0
},
{
"type": "preset",
"value": "preset_code"
}
],
"values": [
{
".landing-block-node-title@0": "First Card",
".landing-block-node-title@1": "Card from Preset"
}
]
}
}
}' \
"https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.block.updateCards.json"
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"lid": 311,
"block": 6058,
"data": {
".landing-block-card": {
"source": [
{
"type": "card",
"value": 0
},
{
"type": "preset",
"value": "preset_code"
}
],
"values": [
{
".landing-block-node-title@0": "First Card",
".landing-block-node-title@1": "Card from Preset"
}
]
}
},
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/landing.block.updateCards.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.updateCards',
params: {
lid: 311,
block: 6058,
data: {
'.landing-block-card': {
source: [
{
type: 'card',
value: 0,
},
{
type: 'preset',
value: 'preset_code',
},
],
values: [
{
'.landing-block-node-title@0': 'First card',
'.landing-block-node-title@1': 'Card from preset',
},
],
},
},
},
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('Cards updated:', 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 updateBlockCards() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'landing.block.updateCards',
params: {
lid: 311,
block: 6058,
data: {
'.landing-block-card': {
source: [
{
type: 'card',
value: 0,
},
{
type: 'preset',
value: 'preset_code',
},
],
values: [
{
'.landing-block-node-title@0': 'First card',
'.landing-block-node-title@1': 'Card from preset',
},
],
},
},
},
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('Cards updated:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', updateBlockCards)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.landing.block.update_cards(
lid=351,
block=6428,
data={
".landing-block-card": {
"source": [
{
"type": "card",
"value": 0,
},
{
"type": "preset",
"value": "preset_code",
},
],
"values": [
{
".landing-block-node-title@0": "First card",
},
{
".landing-block-node-title@1": "Card from preset",
},
],
},
},
).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.updateCards',
[
'lid' => 311,
'block' => 6058,
'data' => [
'.landing-block-card' => [
'source' => [
[
'type' => 'card',
'value' => 0,
],
[
'type' => 'preset',
'value' => 'preset_code',
],
],
'values' => [
[
'.landing-block-node-title@0' => 'First Card',
'.landing-block-node-title@1' => 'Card from Preset',
],
],
],
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . var_export($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating block cards: ' . $e->getMessage();
}
BX24.callMethod(
'landing.block.updateCards',
{
lid: 311,
block: 6058,
data: {
'.landing-block-card': {
source: [
{
type: 'card',
value: 0
},
{
type: 'preset',
value: 'preset_code'
}
],
values: [
{
'.landing-block-node-title@0': 'First Card',
'.landing-block-node-title@1': 'Card from Preset'
}
]
}
}
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'landing.block.updateCards',
[
'lid' => 311,
'block' => 6058,
'data' => [
'.landing-block-card' => [
'source' => [
[
'type' => 'card',
'value' => 0,
],
[
'type' => 'preset',
'value' => 'preset_code',
],
],
'values' => [
[
'.landing-block-node-title@0' => 'First Card',
'.landing-block-node-title@1' => 'Card from Preset',
],
],
],
],
]
);
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.updateCards", b24.Params{
"lid": 311,
"block": 6058,
"data": b24.Params{
".landing-block-card": b24.Params{
"source": []b24.Params{
{
"type": "card",
"value": 0,
},
{
"type": "preset",
"value": "preset_code",
},
},
"values": []b24.Params{
{
".landing-block-node-title@0": "First card",
".landing-block-node-title@1": "Card from the preset",
},
},
},
},
})
if err != nil {
return fmt.Errorf("landing.block.updateCards: %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": 1774525085,
"finish": 1774525085.858169,
"duration": 0.8581690788269043,
"processing": 0,
"date_start": "2026-03-26T14:38:05+02:00",
"date_finish": "2026-03-26T14:38:05+02:00",
"operating_reset_at": 1774525685,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Result of the card update. Returns |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error": "MISSING_PARAMS",
"error_description": "Not enough call parameters, missing: data"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
|
|
Required parameter |
|
|
Page with identifier |
|
|
Block with identifier |
|
|
User does not have permission to edit the site |
|
|
The server could not confirm that the changes were applied correctly. The error depends on server settings and is not related to the request parameters |
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 |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
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 |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
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 — |
|
|
|
No active webhook with the specified user identifier and secret code was 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 |
|
|
|
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 |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
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 |