Users and organisationGet the calling user (v2)

Get the calling user (v2)

Returns the user the access token belongs to — IDs, name, initials, e-mail, user type, picture URL and legal entity.

"Who am I" for v2 clients. Always the caller; there is no parameter. Returns the caller's own personal data (name, initials, e-mail, profile-picture URL) plus the legal entity ID and name. For a client-credentials token this is the system user the token maps to.

Use it to:

  • Check that a token works (200)

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Changes are visible to the next read immediately.

See also: GET /v1/user/me, GET /v2

curl -X GET "https://app3.timelog.com/your-account/api/v2/users/me" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "UserId": 123,
    "Id": "123e4567-e89b-12d3-a456-426614174000",
    "FullName": "John Doe",
    "FirstName": "John Doe",
    "LastName": "John Doe",
    "Initials": "example_string",
    "Email": "user@example.com",
    "IsActive": true,
    "UserType": "Employee",
    "ProfilePicture": "null",
    "LegalEntityId": 123,
    "LegalEntityName": "John Doe"
  },
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ],
  "Actions": [
    {}
  ]
}
GET
/v2/users/me
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).

The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.

Not yet documented: how to obtain a token.

Not yet documented: token lifetime.

Responses

Propertiesobject

The calling user as REST v2 returns it: identifiers, name, initials, e-mail, active flag, user type, a profile-picture URL and the legal entity with its name. Only ever the caller (there is no v2 user lookup by id). See UserRead for the user/employee distinction.

Linksarray
Actionsobject[]