One change
List Compliance Group Members
api/compliance/groups/members/list
Nearest release: v2.1.245, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
api/compliance/groups/members/list Changed · +12 / -15 lines
# List Compliance Group Members ## Path parameters ## Query parameters ## Headers ## Returns ## Example ### Response (200) ## List Compliance Group Members ### Path Parameters ### Query Parameters ### Header Parameters ### Returns ### Example #### Response
from line 1
---- -title: List Compliance Group Members -url: https://platform.claude.com/docs/en/api/compliance/groups/members/list ---- +# List Compliance Group Members -## List Compliance Group Members +**GET** `/v1/compliance/groups/{group_id}/members` -**get** `/v1/compliance/groups/{group_id}/members` - List Compliance Group Members -### Path Parameters +## Path parameters - `group_id: string` The group ID (tagged ID, e.g., rbac_group_abc123) -### Query Parameters +## Query parameters - `limit: optional number` Maximum results (default: 500, max: 1000) + default: 500, maximum: 1000, minimum: 1 + - `page: optional string` Opaque pagination token from a previous response's `next_page` field. 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. -### Header Parameters +## Headers - `"x-api-key": optional string` -### Returns +## Returns -- `data: array of object { created_at, email, updated_at, user_id }` +- `data: array of object` List of group members
from line 56
Token to retrieve the next page. Use this as the 'page' parameter in your next request -### Example +## Example -```http +```bash curl https://api.anthropic.com/v1/compliance/groups/$GROUP_ID/members \ -H "Authorization: Bearer $ANTHROPIC_COMPLIANCE_API_KEY" ``` -#### Response +### Response (200) ```json {