curl --request POST \
--url https://api.example.com/v1/groups \
--header 'Content-Type: application/json' \
--data '
{
"title": "<string>",
"description": "<string>",
"members": [
{
"member": "<string>",
"role": "ROLE_UNSPECIFIED"
}
],
"source": "<string>",
"email": "<string>"
}
'{
"name": "<string>",
"title": "<string>",
"description": "<string>",
"members": [
{
"member": "<string>",
"role": "ROLE_UNSPECIFIED"
}
],
"source": "<string>",
"email": "<string>"
}Creates a new group. Permissions required: bb.groups.create
curl --request POST \
--url https://api.example.com/v1/groups \
--header 'Content-Type: application/json' \
--data '
{
"title": "<string>",
"description": "<string>",
"members": [
{
"member": "<string>",
"role": "ROLE_UNSPECIFIED"
}
],
"source": "<string>",
"email": "<string>"
}
'{
"name": "<string>",
"title": "<string>",
"description": "<string>",
"members": [
{
"member": "<string>",
"role": "ROLE_UNSPECIFIED"
}
],
"source": "<string>",
"email": "<string>"
}The email to use for the group, which will become the final component of the group's resource name.
A group of users within the workspace.
OK
A group of users within the workspace.
The name of the group to retrieve. Format: groups/{group}, the group should be email or uuid.
The display title of the group.
The description of the group.
The members of the group.
Show child attributes
The source system where the group originated (e.g., Entra ID for SCIM sync).
The unique email for the group.
Was this page helpful?