Skip to main content
PUT
Update Group

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Workspace-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access.
  • Manage a restricted group: A second check requires a user owner, an organization-admin user, or permission to manage groups on a manager workspace. Organization-scoped API keys cannot manage restricted groups.
  • Manage a group your workspace manages: A workspace-scoped key can change only groups managed by a workspace it allows, never organization-wide groups. A synced group cannot be renamed or have its members replaced, and members must be people rather than agent identities. Changing scoped_id requires the group to be configured for a workspace the key allows. A workspace-scoped key cannot replace the members of a group that grants a workspace role. The key must hold groups:manage; a full-access workspace key cannot.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Body

application/json
name
string | null
userIds
string[]
members
members · object
scopedId
string | null
teamId
string | null

Response

200 - application/json

Success

data
data · object