---
title: "Getting authenticated User details"
method: GET
path: "/v1/users/current"
tags: ["Users", "User Preferences"]
---

# Getting authenticated User details

`GET /v1/users/current`

Typically, you would get User details by the User's numeric Actor ID.

However, if you only have a Bearer token, for example, you don't have any information about the user attached to that session, including even the ID with which to get more information. So you can instead supply the text `current` to get the user information associated with the authenticated session.

If you _do_ use `current`, you may request extended metadata. Supply an `X-Extended-Metadata` header value of `true` to additionally receive:
- an array of strings of the `verbs` the authenticated User/Actor is allowed to perform server-wide
- an object containing the preferences of the authenticated User/Actor

## Response `200`

This is the Extended Metadata response, if requested via the appropriate header:

- object
  - `createdAt` string — ISO date format
  - `displayName` string — All `Actor`s, regardless of type, have a display name
  - `id` number
  - `type` 'user' | 'field_key' | 'public_link' | 'singleUse' — the Type of this Actor; typically this will be `user`.
  - `updatedAt` string — ISO date format
  - `deletedAt` string — ISO date format
  - `email` string — Only `User`s have email addresses associated with them

---

[API](https://skmtc.net/getodk/apis/odk-central-api.md) · [All operations](https://skmtc.net/getodk/apis/odk-central-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/getodk/odk-central-api/versions/d8f5a0886a8b/schema)