Skip to main content
GET
Get a user identity
A member may read only their own identity; an admin key may read any member of the same org. Ids the caller cannot see return 404 rather than 403, so identities cannot be probed.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • Self or admin. A member may read only their own identity. An admin key may read any member of the same organization. Anything else is 404, so identities cannot be probed by id.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

user_id
string
required

Response

The user's derived identity snapshot.

The response is of type Response Get User Identity V1 Identity User User Id Get · object.