Get a List of Registered Placement Handlers placement.get
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:
placement,depending on the placementWho can execute the method: administrator
The method placement.get retrieves a list of registered widget placement handlers.
Method Parameters
The method has no parameters.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/placement.get
try
{
const response = await $b24.callMethod(
"placement.get",
{}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'placement.get',
[]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Info: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting placements: ' . $e->getMessage();
}
BX24.callMethod(
"placement.get",
{},
function(result)
{
if(result.error())
console.error(result.error());
else
console.info(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'placement.get',
[]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": [
{
"placement": "CRM_DEAL_LIST_TOOLBAR",
"userId": 0,
"handler": "https://myapp.com/?handler=1",
"options": [],
"title": "Add invoice",
"description": "",
"langAll": {
"de": {
"TITLE": "Add invoice",
"DESCRIPTION": "",
"GROUP_NAME": "Documents"
}
}
},
{
"placement": "CRM_DEAL_LIST_TOOLBAR",
"userId": 0,
"handler": "https://myapp.com/?handler=1",
"options": [],
"title": "Import invoice",
"description": "",
"langAll": {
"de": {
"TITLE": "Import invoice",
"DESCRIPTION": "",
"GROUP_NAME": "Documents"
}
}
},
{
"placement": "IM_CONTEXT_MENU",
"userId": 0,
"handler": "https://myapp.com/?handler=2",
"options": {
"extranet": "N",
"context": "ALL",
"role": "USER"
},
"title": "My App 1",
"description": "",
"langAll": {
"de": {
"TITLE": "My App 1",
"DESCRIPTION": "",
"GROUP_NAME": ""
}
}
},
{
"placement": "PAGE_BACKGROUND_WORKER",
"userId": 1,
"handler": "https://myapp.com/?handler=3",
"options": {
"errorHandlerUrl": "https://myapp.com/?handler=3"
},
"title": "My App 2",
"description": "",
"langAll": {
"de": {
"TITLE": "My App 2",
"DESCRIPTION": "",
"GROUP_NAME": ""
}
}
}
],
"time": {
"start": 1712132792.910734,
"finish": 1712132793.530359,
"duration": 0.6196250915527344,
"processing": 0.032338857650756836,
"date_start": "2024-04-03T10:26:32+02:00",
"date_finish": "2024-04-03T10:26:33+02:00",
"operating_reset_at": 1705765533,
"operating": 3.3076241016387939
}
}
Returned Data
|
Name |
Description |
|
result |
Returns a list of registered widget handlers. The structure of each element corresponds to the parameters of the handler registration method |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400, 403, 200
{
"error": "INVALID_REQUEST",
"error_description": "Https 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
|
Code |
Description |
Status |
|
|
Current authorization type is denied for this method. Application context required |
403 |
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
- Remove Registered Automation Rule Handler placement.unbind
- Interaction with UI: Overview of Methods