Send Personal Notification im.notify.personal.add
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:
imWho can execute the method: any user
The method im.notify.personal.add sends a personal notification on behalf of the current user.
The method is only available when called through an application.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
USER_ID* |
Identifier of the user receiving the notification. You can obtain the user ID using the methods user.get, user.search, or im.user.get |
|
MESSAGE* |
The text of the notification. The method trims whitespace from the edges of the string before sending. Supports BB codes — see more in the Message Formatting section |
|
MESSAGE_OUT |
The text of the notification for external channels, such as email. If not provided, an empty value is sent |
|
TAG |
A unique tag for the notification within the application. When adding a notification with an existing tag, other notifications will be removed. Pass with |
|
SUB_TAG |
An additional tag for the notification without uniqueness checks. Pass with |
|
Attachment for the notification in object format or JSON string. See more in the Attachments section |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":5,"MESSAGE":"Task Reminder","MESSAGE_OUT":"Task Reminder (email)","TAG":"TASK_REMINDER_42","SUB_TAG":"TASK_REMINDER|42"}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/im.notify.personal.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":5,"MESSAGE":"Task Reminder","MESSAGE_OUT":"Task Reminder (email)","TAG":"TASK_REMINDER_42","SUB_TAG":"TASK_REMINDER|42","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/im.notify.personal.add
try {
const response = await $b24.callMethod('im.notify.personal.add', {
USER_ID: 5,
MESSAGE: 'Task Reminder',
MESSAGE_OUT: 'Task Reminder (email)',
TAG: 'TASK_REMINDER_42',
SUB_TAG: 'TASK_REMINDER|42',
});
const { result } = response.getData();
console.log('Notification ID:', result);
} catch (error) {
console.error('Error:', error);
}
try {
$response = $b24Service->core->call(
'im.notify.personal.add',
[
'USER_ID' => 5,
'MESSAGE' => 'Task Reminder',
'MESSAGE_OUT' => 'Task Reminder (email)',
'TAG' => 'TASK_REMINDER_42',
'SUB_TAG' => 'TASK_REMINDER|42',
]
);
$result = $response->getResponseData()->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
echo 'Notification ID: ' . $result->data();
}
} catch (Throwable $exception) {
echo $exception->getMessage();
}
BX24.callMethod(
'im.notify.personal.add',
{
USER_ID: 5,
MESSAGE: 'Task Reminder',
MESSAGE_OUT: 'Task Reminder (email)',
TAG: 'TASK_REMINDER_42',
SUB_TAG: 'TASK_REMINDER|42',
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'im.notify.personal.add',
[
'USER_ID' => 5,
'MESSAGE' => 'Task Reminder',
'MESSAGE_OUT' => 'Task Reminder (email)',
'TAG' => 'TASK_REMINDER_42',
'SUB_TAG' => 'TASK_REMINDER|42',
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Notification ID: ' . $result['result'];
}
Response Handling
HTTP Code: 200
{
"result": 12345,
"time": {
"start": 1760000000.0,
"finish": 1760000000.1,
"duration": 0.1,
"processing": 0.04,
"date_start": "2026-03-02T09:30:00+01:00",
"date_finish": "2026-03-02T09:30:00+01:00",
"operating_reset_at": 1760030000,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
Identifier of the created notification. If the notification is not created, it may return |
|
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400, 403
{
"error": "USER_ID_EMPTY",
"error_description": "User ID can't be empty"
}
|
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 |
Value |
|
|
Access for this method not allowed by session authorization |
Method called with session authorization, which is prohibited for it |
|
|
User ID can't be empty |
Parameter |
|
|
Message can't be empty |
Message text not provided |
|
|
You have exceeded the maximum allowable size of attach |
Exceeded the allowable size of attachment |
|
|
Incorrect attach params |
Incorrect format of attachment |
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
- Send Notification im.notify
- Send System Notification im.notify.system.add
- Get Notifications im.notify.get
- Get Notification Type Schema im.notify.schema.get
- Read the list of notifications im.notify.read.list
- Read or Mark Notification as Unread im.notify.read
- Read All Notifications im.notify.read.all
- Responding to Notifications with Quick Response im.notify.answer
- Interacting with Notification Buttons im.notify.confirm
- Delete Notification im.notify.delete
- Searching Notification History im.notify.history.search