Skip to main content
GET
Get a user

Authorizations

Authorization
string
header
required

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

user_id
string
required

The unique user identifier (base64) A universally unique identifier (base64-encoded opaque string).

Example:

"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. Invitations in the acceptance flow appear as users with INVITED or EXPIRED status. Their IDs identify the invitation until acceptance; refresh the user list after acceptance to obtain the member ID.

id
string
required

A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

name
string
required

Display name of the user. Pending invitations in the acceptance flow use the email address until acceptance.

email
string<email>
required

An email address

Example:

"user@example.com"

created_at
string<date-time>
required

Timestamp for when the user or invitation was created

status
enum<string>
required

Current status of the user in the account.

  • ACTIVE: User has verified their email and can access the platform.
  • INVITED: User has a pending invitation whose link is still valid.
  • EXPIRED: The invitation link has expired or is missing. A new invite is required.
Available options:
ACTIVE,
INVITED,
EXPIRED
role
object
required

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.

is_developer
boolean
required

Whether the user has developer permissions (can use the Arize API)