Get a user
Get a specific user by their ID.
Requires account admin role, account member role, or USER_READ permission at the account level.
Returns 404 if the user does not exist, does not belong to the caller’s account, or the caller lacks read permission.
Authorizations
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
Path Parameters
The unique user identifier (base64) A universally unique identifier (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
Response
An account user object
An account user represents a member of the account. Users can be listed, updated, or removed from the account.
A universally unique identifier (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
Display name of the user
An email address
"user@example.com"
Timestamp for when the user was created
Current status of the user in the account.
active: User has verified their email and can access the platform.invited: User has been invited and their verification token is still valid.expired: User was invited but their verification token has expired or is missing. A new invite is required.
active, invited, expired An account-level role assignment. Discriminated by type:
predefined: one of the predefined roles (admin,member,annotator)custom: a custom RBAC role identified by its ID
Note: custom role assignments are not yet supported and are reserved for future use.
- Option 1
- Option 2
Whether the user has developer permissions (can use the Arize API)