Remove Registered Automation Rule Handler placement.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:
placementWho can execute the method: administrator, authorized in the application
The method placement.unbind removes the registered Automation rule handler.
The method works only in the context of the application.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
PLACEMENT* |
Identifier of the Automation rule placement.
|
|
HANDLER |
URL of the Automation rule handler.
If the parameter is not provided or is empty, the method removes all handlers for the specified Automation rule registered by the application. |
|
USER_ID |
Identifier of the Bitrix24 user for whom the handler was registered.
If the parameter is provided, the method removes only the handlers for the specified user. |
Code Examples
How to Use Examples in Documentation
Example of removing a registered Automation rule handler, where:
PLACEMENT— identifier of the Automation rule placementHANDLER— URL of the Automation rule handler
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"PLACEMENT": "CRM_LEAD_DETAIL_TAB",
"HANDLER": "https://www.myapplicationhost.com/placement/",
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/placement.unbind.json"
try
{
const response = await $b24.callMethod(
'placement.unbind',
{
PLACEMENT: 'CRM_LEAD_DETAIL_TAB',
HANDLER: 'https://www.myapplicationhost.com/placement/'
}
);
const result = response.getData().result;
console.info(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'placement.unbind',
[
'PLACEMENT' => 'CRM_LEAD_DETAIL_TAB',
'HANDLER' => 'https://www.myapplicationhost.com/placement/',
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error unbinding placement: ' . $e->getMessage();
}
BX24.callMethod(
'placement.unbind',
{
PLACEMENT: 'CRM_LEAD_DETAIL_TAB',
HANDLER: 'https://www.myapplicationhost.com/placement/'
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
$result = CRest::call(
'placement.unbind',
[
'PLACEMENT' => 'CRM_LEAD_DETAIL_TAB',
'HANDLER' => 'https://www.myapplicationhost.com/placement/',
]
);
echo '<pre>';
print_r($result);
echo '</pre>';
Response Handling
HTTP Status: 200
{
"result": {
"count": 4
},
"time": {
"start": 1775058296,
"finish": 1775058296.998083,
"duration": 0.9980831146240234,
"processing": 0,
"date_start": "2026-04-01T18:44:56+02:00",
"date_finish": "2026-04-01T18:44:56+02:00",
"operating_reset_at": 1775058896,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with the result of the removal:
|
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 403
{
"error": "WRONG_AUTH_TYPE",
"error_description": "Current authorization type is denied for this method Application context required"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
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 |
|
|
|
Current authorization type is denied for this method Application context required |
Method call not from application context |
|
|
|
Access denied! |
User is not an administrator |
|
|
|
Argument 'PLACEMENT' is null or empty |
'PLACEMENT' not provided or empty value passed |
|
|
|
The value of an argument 'PLACEMENT' must be of type string |
'PLACEMENT' parameter passed 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 |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
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 |
|
|
|
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
- Widget Embedding Locations
- Get a List of Available Application Embed Locations placement.list
- Set Up the Widget Handler placement.bind
- Get a List of Registered Placement Handlers placement.get
- Interaction with UI: Overview of Methods