> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get current user

> The authenticated user's own profile, including the clients they belong to.



## OpenAPI

````yaml /api-reference/services_docs_mintlify_enriched/iam_api.yaml get /iam/v2/users/me
openapi: 3.1.0
info:
  title: Gcore OpenAPI – IAM API
  license:
    name: Proprietary
  description: >-
    This OpenAPI is an aggregated OpenAPI specification that unifies all Gcore
    products into a single file. It covers Cloud, CDN, DNS, WAAP, DDoS
    Protection, Object Storage, Streaming, and FastEdge services.
  version: bab38d72d5e5
servers:
  - url: https://api.gcore.com
security:
  - APIKey: []
tags:
  - name: Account
    description: >-
      Account management operations including authentication, password
      management, and account details.
  - name: API Tokens
    description: >-
      Use permanent API tokens for regular automated requests to services.

      You can either set its validity period when creating it or issue a token
      for an unlimited time.

      Please address the API documentation of the specific product in order to
      check if it supports API tokens.


      Newer endpoints under `/v2/…` issue tokens using `_` (underscore) as the
      separator

      (for example `42_a1b2c3d4e5f6...`) and are the recommended way to create
      new tokens.

      Legacy endpoints that issue `$`-separated tokens are marked deprecated and
      will be removed

      on **2026-07-17**; tokens that were already issued keep authenticating.


      Provide your APIKey in the Authorization header.


      Example: ```curl -H "Authorization: APIKey 42_a1b2c3d4e5f6..."
      https://api.gcore.com/iam/users/me```


      Please note: When authorizing via SAML SSO, our system does not have any

      information about permissions given to the user by the identity provider.

      Even if the provider revokes the user's access rights, their tokens remain
      active.

      Therefore, if necessary, the token will need to be deleted manually.
  - name: Users
paths:
  /iam/v2/users/me:
    get:
      tags:
        - Users
      summary: Get current user
      description: >-
        The authenticated user's own profile, including the clients they belong
        to.
      operationId: iamGetCurrentUserV2
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClientUserMeV2'
        '401':
          $ref: '#/components/responses/401'
components:
  schemas:
    ClientUserMeV2:
      type: object
      description: >-
        The client-tier caller's own profile, including the clients they belong
        to.
      required:
        - id
        - email
        - name
        - client
        - groups
        - activated
        - user_type
        - two_fa
        - auth_types
        - created_at
        - clients_and_roles
        - show_chat
        - can_disable_2fa
      properties:
        id:
          type: integer
          readOnly: true
        email:
          type: string
          format: email
          maxLength: 255
          description: User's email address used for login and notifications.
        name:
          type: string
          maxLength: 255
          description: Full name of the user.
        client:
          type: integer
          nullable: true
          readOnly: true
        lang:
          $ref: '#/components/schemas/LangEnumV2'
        phone:
          type: string
          maxLength: 255
          nullable: true
          description: User phone
        groups:
          type: array
          readOnly: true
          items:
            $ref: '#/components/schemas/GroupV2'
        activated:
          type: boolean
          readOnly: true
          description: Whether the user's membership in this client is activated.
        user_type:
          type: string
          readOnly: true
        two_fa:
          type: boolean
          description: >-
            Indicates whether two-factor authentication (TOTP) is enabled for
            the user.
        auth_types:
          type: array
          readOnly: true
          items:
            type: string
          description: >-
            List of authentication methods available to the user (e.g.,
            'password', 'sso').
        created_at:
          type: string
          format: date-time
          nullable: true
          readOnly: true
        clients_and_roles:
          type: array
          readOnly: true
          items:
            $ref: '#/components/schemas/ClientsAndRolesV2'
        show_chat:
          type: boolean
          readOnly: true
          description: Whether the support chat widget should be shown.
        can_disable_2fa:
          type: boolean
          readOnly: true
          description: >-
            False when the user cannot disable their own 2FA because they are an
            active member of an account that enforces 2FA. Use it to disable the
            Disable-2FA control.
    LangEnumV2:
      type: string
      enum:
        - az
        - de
        - en
        - ru
        - zh
    GroupV2:
      type: object
      required:
        - id
        - name
      properties:
        id:
          type: integer
          readOnly: true
        name:
          type: string
          maxLength: 150
    ClientsAndRolesV2:
      type: object
      required:
        - client_id
        - client_company_name
        - user_roles
        - user_id
        - auth_types
      properties:
        client_id:
          type: integer
          readOnly: true
        client_company_name:
          type: string
          readOnly: true
        user_roles:
          type: array
          readOnly: true
          items:
            type: string
        user_id:
          type: integer
          readOnly: true
        auth_types:
          type: array
          readOnly: true
          items:
            type: string
  responses:
    '401':
      description: >-
        Authentication credentials were not provided or given token not valid
        for any token type.
  securitySchemes:
    APIKey:
      description: >-
        API key for authentication. Make sure to include the word `apikey`,
        followed by a single space and then your token.

        Example: `apikey 1234_abcdef`
      type: apiKey
      in: header
      name: Authorization

````