Get Information About the Current User user.current

Scope: user, user_brief, user_basic

Who can execute the method: any user

The method user.current retrieves information about the [current](current_key) user.

The list of user fields in Bitrix24 that will be obtained as a result of executing the method depends on the application's/webhook's scope. Details about user data access can be found in the article.

The method has no parameters. However, by making a REST request using data from $_REQUEST to the domain DOMAIN and adding AUTH_ID to the request for access to Bitrix24, you can find out which user opened the page in the context of Bitrix24.

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/user.current
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{}' \
        https://**put_your_bitrix24_address**/rest/user.current
        
try
        {
        	const response = await $b24.callMethod(
        		"user.current",
        		{}
        	);
        	
        	const result = response.getData().result;
        	console.dir(result);
        }
        catch( error )
        {
        	console.error('Error:', error);
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'user.current',
                    []
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result->error()) {
                error_log($result->error());
            } else {
                echo 'Current user data: ' . print_r($result->data(), true);
            }
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error getting current user data: ' . $e->getMessage();
        }
        
BX24.callMethod(
            "user.current",
            {},
            function(result)
            {
                if(result.error())
                    console.error(result.error());
                else
                    console.dir(result.data());
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'user.current',
            []
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        

Response Handling

HTTP Status: 200

    {
                "result": {
                    "ID": "3",
                    "ACTIVE": true,
                    "NAME": "John",
                    "LAST_NAME": "Doe",
                    "EMAIL": "test@gmail.com",
                    "LAST_LOGIN": "2024-07-23T08:07:26+00:00",
                    "DATE_REGISTER": "2024-07-22T00:00:00+00:00",
                    "IS_ONLINE": "Y",
                    "LAST_ACTIVITY_DATE": "2024-07-23 08:08:50",
                    "PERSONAL_GENDER": "",
                    "PERSONAL_BIRTHDAY": "",
                    "WORK_POSITION": "",
                    "UF_EMPLOYMENT_DATE": "",
                    "UF_DEPARTMENT": [1]
                },
                "time": {
                    "start": 1721722262.960948,
                    "finish": 1721722262.985244,
                    "duration": 0.024296045303344727,
                    "processing": 0.0012989044189453125,
                    "date_start": "2024-07-23T08:11:02+00:00",
                    "date_finish": "2024-07-23T08:11:02+00:00",
                    "operating": 0
                }
            }
        

Returned Data

Name
type

Description

result
object

The root element of the response that contains information about the user

time
time

Information about the request execution time

Error Handling

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred, please contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

An internal server error has occurred, please contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

405

ERROR_BATCH_METHOD_NOT_ALLOWED
Method is not allowed for batch usage

The current method is not allowed to be called using batch

400

ERROR_BATCH_LENGTH_EXCEEDED
Max batch length exceeded

The maximum length of parameters passed to the batch method has been exceeded

401

NO_AUTH_FOUND
Wrong authorization data

Invalid access token or webhook code

400

INVALID_REQUEST
Https required

The methods must be called using the HTTPS protocol

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is available only on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user whose access token or webhook was used to call the method lacks permissions

404

ERROR_MANIFEST_IS_NOT_AVAILABLE
Manifest is not available

The manifest is not available

403

insufficient_scope
The request requires higher privileges than provided by the webhook token

The request requires higher privileges than those provided by the webhook token

401

expired_token
The access token provided has expired

The provided access token has expired

403

user_access_error
The user does not have access to the application

The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users

500

PORTAL_DELETED
Portal was deleted

The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning

The one whose token you used when calling REST. If you use a saved admin token, the administrator will be displayed. If you use the token that comes in the POST request in the application frame, it will be the user who logged into the application.