Widget in the CONTACT_CENTER
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:
contact_center
The CONTACT_CENTER placement adds an item to the Contact Center application list.
The placement code is specified in the PLACEMENT parameter of the placement.bind method.
The widget will not be displayed in the interface until the application installation is complete. Check the application installation
Where the widget is embedded
|
Widget Code |
Location |
|
|
Item in the Contact Center list |
Where to find it in the interface
Open the Contact Center page at https://your_site.com/contact_center/. The application item with PLACEMENT=CONTACT_CENTER appears at the bottom of the page in the Partner Solutions section.
What the handler receives
Data is transmitted as a POST request
Array
(
[DOMAIN] => example.bitrix24.com
[PROTOCOL] => 1
[LANG] => de
[APP_SID] => 0123456789abcdef0123456789abcdef
[APPLICATION_SCOPE] => crm,placement,contact_center,imopenlines
[APPLICATION_TOKEN] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[AUTH_ID] => 6061e72600631fcd00005a4b00000001f0f1076700000000f69dd5fc643d9ce2fdbc1
[AUTH_EXPIRES] => 3600
[PLACEMENT_OPTIONS] => {"ID":"19"}
[REFRESH_ID] => 50e00aa340631fcd00005a4b00000001f0f1071111116580a5b83c2de639ef28c12
[SERVER_ENDPOINT] => https://oauth.bitrix24.info/rest/
[member_id] => abcdef1234567890abcdef1234567890
[status] => F
[PLACEMENT] => CONTACT_CENTER
)
Required parameters are marked with *
|
Parameter |
Description |
|
DOMAIN* |
The Bitrix24 address where the widget handler was invoked |
|
PROTOCOL* |
Secure or non-secure HTTP protocol:
|
|
LANG* |
The user interface language of Bitrix24 that invoked the widget. You can localize the interface language in your widget based on this value |
|
APP_SID |
String identifier of the application that registered the widget handler |
|
AUTH_ID |
Authorization token OAuth 2 issued for the user who invoked the widget. Can be used for REST API calls on behalf of this user |
|
AUTH_EXPIRES |
Time in seconds after which the authorization token will become invalid |
|
REFRESH_ID |
Refresh token OAuth 2 issued for the user who invoked the widget. Can be used to refresh the authorization token on behalf of this user |
|
member_id* |
Unique string identifier of Bitrix24 where the widget handler was invoked. |
|
status |
Type of application that registered the handler for this widget. Accepts values:
|
|
PLACEMENT* |
Code for the widget embedding location. You can use the same handler URL for all your widgets. The value that Bitrix24 will report in the |
|
PLACEMENT_OPTIONS |
Additional data in the form of a JSON string that defines the context of the widget execution. For example, this could be an array containing the numeric identifier of the CRM entity in the detail form where the widget handler was invoked, etc. The |
Additional Data
|
Parameter |
Description |
|
APPLICATION_SCOPE |
List of scopes available to the application |
|
APPLICATION_TOKEN |
Application token for secure event handling |
|
SERVER_ENDPOINT |
Bitrix24 authorization server address required for updating OAuth 2.0 tokens |
PLACEMENT_OPTIONS
The value of PLACEMENT_OPTIONS is passed as a JSON string with the context of the call.
For CONTACT_CENTER, the context includes the key:
ID— identifier of the Contact Center entity for which the widget was opened
Continue your exploration
- Set Up the Widget Handler placement.bind
- Interaction with UI: Overview of Methods
- Interactivity in Applications: Overview of Scenarios and Methods
- Methods of BX24 SDK for Widgets