Add a comment to the message log.blogcomment.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:
logWho can execute the method: any user
The method log.blogcomment.add adds a comment to a News Feed message.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
POST_ID* |
Identifier of the News Feed message. The message identifier can be obtained using the method log.blogpost.get |
|
TEXT* |
The text of the comment. It is considered during duplication checks and is saved in the |
|
FILES |
An array of files described according to the file handling rules. Files will be uploaded to the user's Drive and linked to the comment |
|
USER_ID |
Identifier of the user on behalf of whom the comment is published. Available only to administrators. By default, the current user initiating the method call is used. The user identifier can be obtained using the method user.get or user.search |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"POST_ID":403,"TEXT":"Comment on the post","USER_ID":27,"FILES":[["example.txt","SXQncyBhIHRlc3QgZmlsZSBmb3IgQml0cml4IFJlc3QgQVBJLg=="]]}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/log.blogcomment.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"POST_ID":403,"TEXT":"Comment on the post","USER_ID":27,"FILES":[["example.txt","SXQncyBhIHRlc3QgZmlsZSBmb3IgQml0cml4IFJlc3QgQVBJLg=="]],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/log.blogcomment.add
try {
const response = await $b24.callMethod(
'log.blogcomment.add',
{
POST_ID: 403,
TEXT: 'Comment on the post',
USER_ID: 27,
FILES: [
[
'example.txt',
'SXQncyBhIHRlc3QgZmlsZSBmb3IgQml0cml4IFJlc3QgQVBJLg==',
],
],
}
);
const { result } = response.getData();
console.log('Created comment:', result);
} catch (error) {
console.error('Error adding comment:', error);
}
try {
$response = $b24Service
->core
->call(
'log.blogcomment.add',
[
'POST_ID' => 403,
'TEXT' => 'Comment on the post',
'USER_ID' => 27,
'FILES' => [
[
'example.txt',
'SXQncyBhIHRlc3QgZmlsZSBmb3IgQml0cml4IFJlc3QgQVBJLg==',
],
],
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
echo 'Created comment ID: ' . $result->data();
}
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error adding blog comment: ' . $exception->getMessage();
}
BX24.callMethod('log.blogcomment.add', {
POST_ID: 403,
TEXT: 'Comment on the post',
USER_ID: 27,
FILES: [
[
'example.txt',
'SXQncyBhIHRlc3QgZmlsZSBmb3IgQml0cml4IFJlc3QgQVBJLg==',
],
]
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'log.blogcomment.add',
[
'POST_ID' => 403,
'TEXT' => 'Comment on the post',
'USER_ID' => 27,
'FILES' => [
[
'example.txt',
'SXQncyBhIHRlc3QgZmlsZSBmb3IgQml0cml4IFJlc3QgQVBJLg==',
],
],
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Created comment ID: ' . $result['result'];
}
Response Handling
HTTP status: 200
{
"result": 312,
"time": {
"start": 1728904800.123456,
"finish": 1728904800.398112,
"duration": 0.2746560573577881,
"processing": 0.10234594345092773,
"date_start": "2025-10-14T12:40:00+02:00",
"date_finish": "2025-10-14T12:40:00+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Identifier of the created comment |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400
{
"error": "",
"error_description": "No blog module installed"
}
|
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 Errors
|
Code |
Description |
Value |
|
|
|
The |
|
|
|
The News Feed message with the provided |
|
|
|
Failed to retrieve the blog associated with the message |
|
|
|
A similar comment has already been published, checked only for posts without attachments |
|
|
|
The user does not have permission to add a comment to the message |
|
|
|
Internal error while saving the comment |
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 |