Call via Internal Communication BX24.im.callTo
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.
The application runs in an iframe
An application runs inside its own iframe on a different origin. The Bitrix24 runtime is not available there — neither Messenger.* nor BX.Runtime.loadExtension can be reached from the application.
The only channel outward is the parent bridge: the BX24.im.* methods, or their equivalents $b24.parent.imCallTo, $b24.parent.imPhoneTo, $b24.parent.imOpenMessenger, and $b24.parent.imOpenHistory in the b24jssdk library.
Calling these methods prints a deprecation notice in the Bitrix24 console that recommends Messenger.startVideoCall, Messenger.startPhoneCall, or Messenger.openChat. Disregard it: those are top-window methods, available only to code running on the Bitrix24 page itself, and they are not reachable from an application.
The im.public.iframe extension that the notice names is meant for an iframe on the Bitrix24 domain, not for an application frame. For that case, see Passing Context to the Bot When Opening a Chat.
The method BX24.im.callTo sends a command to call a Bitrix24 user via internal communication.
void BX24.im.callTo(Integer userId[, Boolean video])
Parameters
Required parameters are marked with *
|
Name |
Description |
|
userId* |
The identifier of the Bitrix24 user to be called |
|
video |
Type of call: |
Code Example
How to Use Examples in Documentation
BX24.init(function () {
BX24.im.callTo(1, true);
});
Response Handling
The method does not return data (void).