Get User Data im.user.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:
imWho can execute the method: any user
The method im.user.get retrieves data about the current user or a user by ID.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
ID |
User identifier. If not provided, the method will return data for the current user. You can obtain the user identifier using the methods user.get, user.search, or im.chat.user.list |
|
AVATAR_HR |
Parameter to request the Currently, the |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":5,"AVATAR_HR":"Y"}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/im.user.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":5,"AVATAR_HR":"Y","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/im.user.get
try {
const response = await $b24.callMethod('im.user.get', {
ID: 5,
AVATAR_HR: 'Y',
});
const { result } = response.getData();
console.log(result);
} catch (error) {
console.error(error);
}
try {
$response = $b24Service->core->call(
'im.user.get',
[
'ID' => 5,
'AVATAR_HR' => 'Y',
]
);
$result = $response->getResponseData()->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
var_dump($result->data());
}
} catch (Throwable $exception) {
echo $exception->getMessage();
}
BX24.callMethod(
'im.user.get',
{
ID: 5,
AVATAR_HR: 'Y',
},
function(result) {
if (result.error()) {
console.error(result.error().ex);
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'im.user.get',
[
'ID' => 5,
'AVATAR_HR' => 'Y',
]
);
if (!empty($result['error'])) {
echo 'Error: ' . $result['error_description'];
} else {
var_dump($result['result']);
}
Response Handling
HTTP Code: 200
{
"result": {
"id": 5,
"active": true,
"name": "John Smith",
"first_name": "John",
"last_name": "Smith",
"work_position": "Manager",
"color": "#048bd0",
"avatar": "https://example.bitrix24.com/upload/main/avatar.png",
"avatar_hr": "https://example.bitrix24.com/upload/main/avatar_hr.png",
"gender": "M",
"birthday": "",
"extranet": false,
"network": false,
"bot": false,
"connector": false,
"external_auth_id": "default",
"status": "online",
"idle": false,
"last_activity_date": "2026-03-02T09:30:00+01:00",
"mobile_last_date": false,
"desktop_last_date": false,
"absent": false,
"departments": [10],
"phones": {
"work_phone": "+11234567890",
"personal_mobile": "+11234567890",
"inner_phone": "21"
},
"website": "example.com",
"email": "user@example.com",
"bot_data": null,
"type": "user"
},
"time": {
"start": 1760000000.0,
"finish": 1760000000.2,
"duration": 0.2,
"processing": 0.08,
"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 |
|
result |
Object containing user data. The structure of the object is described in detail below |
|
time |
Information about the request execution time |
Result Object
|
Name |
Description |
|
id |
User identifier |
|
active |
User activity status |
|
name |
User's full name |
|
first_name |
User's first name |
|
last_name |
User's last name |
|
work_position |
User's job title |
|
color |
User's color in hex format |
|
avatar |
Link to the avatar |
|
avatar_hr |
Link to the high-resolution avatar |
|
gender |
User's gender |
|
birthday |
Birthday in |
|
extranet |
External user status |
|
network |
Bitrix24 Network user status |
|
bot |
Bot status |
|
connector |
Open Channels user status |
|
external_auth_id |
External authorization code |
|
status |
User status |
|
idle |
User's idle date or |
|
last_activity_date |
User's last activity date |
|
mobile_last_date |
Last activity date in the mobile app or |
|
desktop_last_date |
Last activity date in the desktop app or |
|
absent |
User's absence end date or |
|
departments |
Array of department identifiers |
|
phones |
User's phones or |
|
bot_data |
Bot data or |
|
type |
User type |
|
website |
User's website |
|
email |
User's email |
Phones Object
|
Name |
Description |
|
personal_mobile |
Mobile phone |
|
inner_phone |
Internal phone |
Error Handling
HTTP Status: 400
{
"error": "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 |
|
|
User ID can't be empty |
Provided |
|
|
User does not exist |
User with the specified |
|
|
You can request only users who are part of your extranet group |
The current extranet user is requesting a user not from their extranet group |
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 User Data with im.user.list.get
- Set User Status im.user.status.set
- Get User Status im.user.status.get
- Enable Automatic Status "Away" im.user.status.idle.start
- Disable Automatic Status "Away" im.user.status.idle.end