#!/usr/bin/env python3importzulip# Pass the path to your zuliprc file here.client=zulip.Client(config_file="~/zuliprc")request={"group_id":user_group_id,"name":"marketing","description":"The marketing team.",}result=client.update_user_group(request)print(result)
This setting cannot be set to "role:internet" and "role:owners"system groups.
Changes: In Zulip 9.0 (feature level 260), this parameter was
updated to only accept an object with the old and new fields
described below. Prior to this feature level, this parameter could be
either of the two forms of a group-setting value.
Before Zulip 9.0 (feature level 258), this parameter could only be the
integer form of a group-setting value.
Before Zulip 8.0 (feature level 198), this parameter was named
can_mention_group_id.
New in Zulip 8.0 (feature level 191). Previously, groups could be
mentioned only if they were not system groups.
can_mention_group object details:
new: integer | objectrequired
The new group-setting value for who would
have the permission to mention the group.
The list of IDs of individual users in the collection of users with this permission.
direct_subgroups: (integer)[]
The list of IDs of the groups in the collection of users with this permission.
Response
Example response(s)
Changes: As of Zulip 7.0 (feature level 167), if any
parameters sent in the request are not supported by this
endpoint, a successful JSON response will include an
ignored_parameters_unsupported array.
A typical successful JSON response may look like:
{"msg":"","result":"success"}
An example JSON response when the user group ID is invalid:
{"code":"BAD_REQUEST","msg":"Invalid user group","result":"error"}