Get User Comments log.blogcomment.user.get
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
logWho can execute the method: any user
The method log.blogcomment.user.get returns a list of comments on a News Feed post for the specified user and information about attached files.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
USER_ID |
The identifier of the user whose comments need to be retrieved. If the identifier is not specified, the method will return comments from the current user. If the request is made by an administrator on behalf of another user, the The user identifier can be obtained using the user.get or user.search methods. |
|
FIRST_ID |
The method will return comments with identifiers greater than the specified value. |
|
LAST_ID |
The method will return comments with identifiers less than the specified value. |
|
LIMIT |
The number of records in the response. The acceptable value is from |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":28,"FIRST_ID":215,"LAST_ID":216}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/log.blogcomment.user.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"USER_ID":28,"FIRST_ID":215,"LAST_ID":216,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/log.blogcomment.user.get
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame, ISODate } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type BlogCommentUserGetResult = {
comments: {
id: number
comment_id: number
log_id: number
date: ISODate
text: string
attach: number[]
}[]
files: Record<string, {
id: number
date: ISODate
type: string
name: string
size: number
image?: {
width: number
height: number
}
authorId: number
authorName: string
urlPreview: string
urlShow: string
urlDownload: string
}>
}
try {
const response = await $b24.actions.v2.call.make<BlogCommentUserGetResult>({
method: 'log.blogcomment.user.get',
params: {
USER_ID: 28,
FIRST_ID: 215,
LAST_ID: 216,
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Comments:', result.comments, 'Files:', result.files)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function getBlogCommentsForUser() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'log.blogcomment.user.get',
params: {
USER_ID: 28,
FIRST_ID: 215,
LAST_ID: 216,
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Comments:', result.comments, 'Files:', result.files)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', getBlogCommentsForUser)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.log.blogcomment.user.get(
user_id=28,
first_id=215,
last_id=216,
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$response = $b24Service
->core
->call(
'log.blogcomment.user.get',
[
'USER_ID' => 28,
'FIRST_ID' => 215,
'LAST_ID' => 216,
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
echo 'Comments: ' . print_r($result->data(), true);
}
} catch (Throwable $exception) {
error_log($exception->getMessage());
echo 'Error getting blog comments: ' . $exception->getMessage();
}
BX24.callMethod('log.blogcomment.user.get', {
USER_ID: 28,
FIRST_ID: 215,
LAST_ID: 216
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'log.blogcomment.user.get',
[
'USER_ID' => 28,
'FIRST_ID' => 215,
'LAST_ID' => 216,
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
echo 'Comments: ' . print_r($result['result'], true);
}
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "log.blogcomment.user.get", b24.Params{
"USER_ID": 28,
"FIRST_ID": 215,
"LAST_ID": 216,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("log.blogcomment.user.get: %w", err)
}
// The response shape is shown below on this page.
fmt.Printf("%s\n", res.Result)
Response Handling
HTTP Status: 200
{
"result": {
"comments": [
{
"id": 4821,
"comment_id": 4821,
"log_id": 13579,
"date": "2025-01-28T11:05:42+02:00",
"text": "I support the idea!",
"attach": [
90210
]
}
],
"files": {
"90210": {
"id": 90210,
"date": "2025-01-28T11:02:18+02:00",
"type": "image",
"name": "diagram.png",
"size": 184320,
"image": {
"width": 1280,
"height": 720
},
"authorId": 28,
"authorName": "John Smith",
"urlPreview": "https://example.bitrix24.com/disk/showPreview/90210",
"urlShow": "https://example.bitrix24.com/disk/showFile/90210",
"urlDownload": "https://example.bitrix24.com/disk/downloadFile/90210"
}
}
},
"time": {
"start": 1728905100.112233,
"finish": 1728905100.498321,
"duration": 0.38608813285827637,
"processing": 0.14598798751831055,
"date_start": "2025-10-14T12:45:00+02:00",
"date_finish": "2025-10-14T12:45:00+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
The root object of the response. Contains an array of comments and information about attached files. |
|
time |
Information about the execution time of the request. |
Structure of the result Object
|
Name |
Description |
|
comments |
An array of comments. Each element contains fields:
|
|
files |
An associative array describing the files, where the key is the identifier of the Drive object. For each file, |
Error Handling
If the user identifier is not specified or an incorrect value is provided, the method returns comments from the current user.
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |