update_group
modify a group. Note that only one modification action may be performed at once
auto-generated example may not be a valid request. Seev1.UpdateGroupRequest
for all fields.
{
"account": "0cc10e61-d64c-4dbc-b51c-334f7dd45a4a",
"addMembers": [
{
"number": "+13215551234"
}
],
"avatar": "/tmp/image.jpg",
"description": "A club for running in Parkdale",
"groupID": "EdSqI90cS0UomDpgUXOlCoObWvQOXlH5G3Z2d3f4ayE=",
"removeMembers": [
{
"number": "+13215551234"
}
],
"title": "Parkdale Run Club",
"type": "update_group",
"updateAccessControl": {
"link": "ANY"
},
"updateRole": {
"role": "DEFAULT",
"uuid": "aeed01f0-a234-478e-8cf7-261c283151e7"
},
"version": "v1"
}
- Request Type:
v1.UpdateGroupRequest
- Success Response Type:
v1.GroupInfo
- Error response types:
v1.InternalError
v1.InvalidProxyError
v1.ServerNotFoundError
v1.NoSuchAccountError
v1.UnknownGroupError
v1.GroupVerificationError
v1.InvalidRequestError
v1.AuthorizationFailedError
- Can be caused if signald is setup as a linked device that has been removed by the primary device. If trying to update a group, this can also be caused if group permissions don’t allow the update (e.g. current role insufficient or not a member).v1.UnregisteredUserError
v1.SQLError
v1.GroupPatchNotAcceptedError
- Caused when server rejects the group update, e.g. trying to add a user that’s already in the groupv1.UnsupportedGroupError