Remove Embedding Placement landing.repo.unbind

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: user with View access permission in the Sites section

The method landing.repo.unbind removes the embedding placement registered by the current application in the landing section.

Method Parameters

Required parameters are marked with *

Name
type

Description

code^*
string

Code of the embedding placement.

Available codes for the landing section can be found on the LANDING_SETTINGS and LANDING_BLOCK pages.

handler
string

Path of the embedding placement handler.

The handler value must match the PLACEMENT_HANDLER field that was passed during the registration of the embedding placement using the landing.repo.bind method.

For examples of passing PLACEMENT_HANDLER, refer to the LANDING_SETTINGS and LANDING_BLOCK pages.

If the parameter is not provided, the method removes all embedding placements of the current application with the specified code.

If the parameter is provided, the method removes only the embedding placement with the specified code and handler.

Code Examples

How to Use Examples in Documentation

Example of removing an embedding placement, where:

code — code of the embedding placement
handler — path of the embedding placement handler

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "code": "LANDING_SETTINGS",
            "handler": "https://your-domain.com/widgets/landing-settings-handler.php",
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/landing.repo.unbind.json"

try
        {
            const response = await $b24.callMethod(
                'landing.repo.unbind',
                {
                    code: 'LANDING_SETTINGS',
                    handler: 'https://your-domain.com/widgets/landing-settings-handler.php'
                }
            );
        
            const result = response.getData().result;
            console.info(result);
        }
        catch (error)
        {
            console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'landing.repo.unbind',
                    [
                        'code' => 'LANDING_SETTINGS',
                        'handler' => 'https://your-domain.com/widgets/landing-settings-handler.php',
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . var_export($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error unbinding landing placement: ' . $e->getMessage();
        }

BX24.callMethod(
            'landing.repo.unbind',
            {
                code: 'LANDING_SETTINGS',
                handler: 'https://your-domain.com/widgets/landing-settings-handler.php'
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'landing.repo.unbind',
            [
                'code' => 'LANDING_SETTINGS',
                'handler' => 'https://your-domain.com/widgets/landing-settings-handler.php',
            ]
        );
        
        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": 1775203200,
                "finish": 1775203200.764211,
                "duration": 0.7642109394073486,
                "processing": 0,
                "date_start": "2026-04-03T11:00:00+02:00",
                "date_finish": "2026-04-03T11:00:00+02:00",
                "operating_reset_at": 1775203800,
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `boolean`	Result of successful removal of the embedding placement
time `time`	Information about the execution time of the request

Error Handling

HTTP Status: 400

{
            "error": "PLACEMENT_NO_EXIST",
            "error_description": "Such embedding placement does not exist"
        }

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

Status	Code	Description	Value
`400`	`MISSING_PARAMS`	Not enough parameters for the call, missing: code	Method call without `code`
`400`	`PLACEMENT_NO_EXIST`	Such embedding placement does not exist	The current application does not have an embedding placement with the specified `code` and `handler`
`400`	`ACCESS_DENIED`	Insufficient permissions.	User did not pass the general access checks for the landing module

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

Block Editing Item

Overview of Methods

Remove Embedding Placement landing.repo.unbind

Method ParametersMethod Parameters

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