Users
List organization users
GET /v1/compliance/organizations/\{org_uuid\}/users
List current user members of an organization.
Path parameters
org_uuid: stringThe organization UUID
Query parameters
limit: optional numberMaximum results (default: 500, max: 1000)
default: 500, maximum: 1000, minimum: 1
page: optional stringOpaque pagination token from a previous response's
next_pagefield. Pass this to retrieve the next page of results. Clients should treat this value as an opaque string and not attempt to parse or interpret its contents, as the format may change without notice.
Headers
"anthropic-version": optional stringThe version of the Claude API you want to use.
Read more about versioning and our version history here.
"x-api-key": optional string
Returns
data: array of objectList of current organization members sorted by organization join date ascending
id: stringUser identifier (tagged ID)
created_at: stringUser account creation timestamp
format: date-time
email: stringUser's current email address
full_name: stringUser's current full name
organization_role: "admin" or "billing" or "claude_code_user" or 6 moreUser's built-in role within the organization. This is distinct from any custom RBAC roles that may also be assigned.
"admin""billing""claude_code_user""developer""managed""membership_admin""owner""primary_owner""user"
has_more: booleanWhether more records exist beyond the current result set
next_page: string or nullToken to retrieve the next page. Use this as the 'page' parameter in your next request
Example
curl https://api.anthropic.com/v1/compliance/organizations/$ORG_UUID/users \
-H "Authorization: Bearer $ANTHROPIC_COMPLIANCE_API_KEY"Response (200)
{
"data": [
{
"id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
"created_at": "2025-03-12T18:22:41.123456Z",
"email": "jane.doe@example.com",
"full_name": "Jane Doe",
"organization_role": "admin"
}
],
"has_more": true,
"next_page": "cGFnZV90b2tlbl9leGFtcGxlXzE3MzQ1Njc4OTA="
}Domain types
User List Response
UserListResponse objectUser member information for compliance responses.
id: stringUser identifier (tagged ID)
created_at: stringUser account creation timestamp
format: date-time
email: stringUser's current email address
full_name: stringUser's current full name
organization_role: "admin" or "billing" or "claude_code_user" or 6 moreUser's built-in role within the organization. This is distinct from any custom RBAC roles that may also be assigned.
"admin""billing""claude_code_user""developer""managed""membership_admin""owner""primary_owner""user"