Get Event Log Entry main.eventlog.get
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:
mainWho can execute the method: administrator
The method main.eventlog.get returns an event log entry by its identifier.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the log entry |
|
select |
List of fields to return in the response. Available fields:
|
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the parameter /api/ in the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/main.eventlog.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1250}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/main.eventlog.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1250,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/main.eventlog.get
The SDK does not currently support the address /rest/api/ in calls. Use direct HTTP requests, for example, via curl or fetch.
try
{
const response = await $b24.callMethod(
'main.eventlog.get',
{
id: 1250
}
);
const result = response.getData().result;
console.log('Event log item:', result);
}
catch( error )
{
console.error('Error:', error);
}
The SDK does not currently support the address /rest/api/ in calls. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'main.eventlog.get',
[
'id' => 1250
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
The SDK does not currently support the address /rest/api/ in calls. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'main.eventlog.get',
{
id: 1250
},
function(result){
console.info(result.data());
console.log(result);
}
);
The SDK does not currently support the address /rest/api/ in calls. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'main.eventlog.get',
[
'id' => 1250
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"item": {
"id": 839,
"timestampX": "2026-01-30T15:50:24+03:00",
"severity": "SECURITY",
"auditTypeId": "USER_AUTHORIZE",
"moduleId": "main",
"itemId": "1",
"remoteAddr": "3.75.32.66",
"userAgent": "Mozilla\/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/144.0.0.0 Safari\/537.36",
"requestUri": "\/bitrix\/tools\/oauth\/bitrix24net.php?code=2da97c6900ddfdfd01b8d0b200000000000000eda156e035f598dcc2f2927de6c527dc\u0026state=s1.0.79b6f9ab2822c2482d1b15948602b656e8a1722ce4a4ff265297d59d\u0026domain=www.bitrix24.net\u0026user_lang=en\u0026analytics_session_id=pru9c9jdehq31u2v",
"siteId": "s1",
"userId": 1,
"guestId": 0,
"description": "{\u0022userId\u0022:1,\u0022requestId\u0022:\u00220fbda8a91117ccbb8e2205446c18cac9\\\u0022-\\\u00220\u0022,\u0022method\u0022:\u0022external\u0022,\u0022externalAuthId\u0022:\u0022Bitrix24Net\u0022,\u0022externalId\u0022:\u002228889266\u0022}"
}
},
"time": {
"start": 1769777553,
"finish": 1769777553.749127,
"duration": 0.7491269111633301,
"processing": 0,
"date_start": "2026-01-30T15:52:33+03:00",
"date_finish": "2026-01-30T15:52:33+03:00",
"operating_reset_at": 1769778153,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with response data |
|
item |
Log entry object |
|
id |
Identifier of the log entry |
|
timestampX |
Date and time of the event |
|
severity |
Importance level of the event |
|
auditTypeId |
Type of event |
|
moduleId |
Module identifier |
|
itemId |
Object identifier |
|
remoteAddr |
IP address |
|
userAgent |
User-Agent of the request |
|
requestUri |
Request URI |
|
siteId |
Site identifier |
|
userId |
User identifier |
|
guestId |
Guest identifier |
|
description |
Event description |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION",
"message": "Entry with ID = `999999` not found"
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
Description of the error related to the specified field |
Possible Error Codes
Access Errors
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
No administrator rights or missing scope main |
Data Not Found Errors
Error Code: BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Entry with ID = |
Specify |
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
- Get the list of event log entries main.eventlog.list
- Get New Log Entries main.eventlog.tail
- Event Log: Overview of Methods