List the user's active sessions..

GET

/v1/iam/users/{userId}/sessions

Code sample: Shell / cURL

curl --request GET \
  --url https://stratum.example.com/v1/iam/users/example/sessions \
  --header 'Authorization: Bearer <token>'

• A Stratum cluster endpoint.

Returns the user’s active (non-revoked, non-expired) session tokens with createdAt, lastSeenAt, and the sourceIp + userAgent captured at login. The session whose token made this request is flagged current: true.

Self-action: gated by iam:ListSession. Admin-acting-on-someone- else: iam:ListSessionAdmin (covered by the blanket bootstrap- admin / platform-admin permits).

Authorizations

• bearerAuth

Parameters

Path Parameters

userId

required

string

/^u-[a-z0-9-]+$/

Responses

200

Active sessions.

Media typeapplication/json

object

items

required

Array<object>

An active session token in the “active sessions” view.

object

id

required

string

/^tok-[a-z0-9]+$/

createdAt

required

string format: date-time

lastSeenAt

string format: date-time

sourceIp

string

userAgent

string

expiresAt

string format: date-time

current

required

True for the session whose token made this request.

boolean

method

How the session was established: password, install-automation, or oidc:<provider> for an external identity provider.

string

amr

. The authentication methods the identity provider reported (the id_token amr claim, RFC 8176), for example ["pwd", "otp"]. Absent for sessions that did not come from an external provider.

Array<string>

mfa

The session was established with a second factor (request.mfaPresent).

boolean

nextPageToken

string

Example ^generated

{
  "items": [
    {
      "id": "example",
      "createdAt": "2026-04-15T12:00:00Z",
      "lastSeenAt": "2026-04-15T12:00:00Z",
      "sourceIp": "example",
      "userAgent": "example",
      "expiresAt": "2026-04-15T12:00:00Z",
      "current": true,
      "method": "example",
      "amr": [
        "example"
      ],
      "mfa": true
    }
  ],
  "nextPageToken": "example"
}

401

Missing or invalid token.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}

Headers

WWW-Authenticate

string

403

Authenticated but not authorized.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}