Facts
application/x-www-form-urlencoded application/json Arguments
Required arguments
tokenstringRequiredAuthentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.
xxxx-xxxxxxxxx-xxxxusergroupstringRequiredThe encoded ID of the user group to update.
S0604QSJCusersarrayRequiredA comma separated string of encoded user IDs that represent the entire list of users for the user group.
U060R4BJ4,U060RNRCZOptional arguments
include_countbooleanOptionalInclude the number of users in the user group.
trueteam_idstringOptionalencoded team id where the user group exists, required if org token is used
additional_channelsarrayOptionalA comma separated string of encoded channel IDs for which the User Group can custom add usergroup members too.
is_sharedbooleanOptionalBoolean to identify if the API is getting called when a shared section is getting shared
Usage info
This method updates the list of users that belong to a user group. It replaces all users in a user group with the list of users provided in the users parameter.
permission_denied error.To update this setting, navigate to Tools & settings > Workspace settings > Permissions > User Groups within your workspace and update who can create, disable, or modify user groups from the drop-down menus.
If user group permissions cannot be changed and are restricted to admins only, use the user token from a user with the correct permissions. A bot token can be used only if permissions are set to everyone.
You cannot use this method to remove all members from a user group. Instead, use the usergroups.disable method. If you need to reactivate the user group later, use the usergroups.enable method.
Guests or bot users cannot be added to user groups; attempting to do so will result in an invalid_user error (or in the case of single channel guests, a single_channel_guests_cannot_be_added error).
The team_id is only relevant when using an org-level token. This field will be ignored if the API call is sent using a workspace-level token.
POST Bodies
As outlined in Using the Slack Web API, you may present your arguments as either standard POST parameters, or you may use JSON. This can be confusing in terms of the array argument type (users), so let's clarify: to call the method with a URL-encoded string, it may look something like this:
users=U0130R122E8%2C%20U0133AHT0M8
while calling it with a JSON body should be formatted as follows:
"users": [
"U0130R122E8",
"U0133AHT0M8"
]
Both will yield the same result, so it's potato, po-tah-to as far as we're concerned.
Response
Typical success response
{
"ok": true,
"usergroup": {
"id": "S0616NG6M",
"team_id": "T060R4BHN",
"is_usergroup": true,
"name": "Marketing Team",
"description": "Marketing gurus, PR experts and product advocates.",
"handle": "marketing-team",
"is_external": false,
"date_create": 1447096577,
"date_update": 1447102109,
"date_delete": 0,
"auto_type": null,
"created_by": "U060R4BJ4",
"updated_by": "U060R4BJ4",
"deleted_by": null,
"prefs": {
"channels": [],
"groups": []
},
"users": [
"U060R4BJ4",
"U060RNRCZ"
],
"user_count": 1
}
}
Typical error response
{
"ok": false,
"error": "invalid_auth"
}
Errors
This table lists the expected errors that this method could return. However, other errors can be returned in the case where the service is down or other unexpected factors affect processing. Callers should always check the value of the ok parameter in the response.
access_deniedAccess to a resource specified in the request is denied.
accesslimitedAccess to this method is limited on the current network
account_inactiveAuthentication token is for a deleted user or workspace when using a bot token.
deprecated_endpointThe endpoint has been deprecated.
ekm_access_deniedAdministrators have suspended the ability to post a message.
enterprise_is_restrictedThe method cannot be called from an Enterprise.
failed_for_some_usersUser(s) are not in the workspace where this usergroup exists
fatal_errorThe server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.
internal_errorThe server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.
invalid_arg_nameThe method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.
invalid_argumentsThe method was called with invalid arguments.
invalid_array_argThe method was passed an array as an argument. Please only input valid strings.
invalid_authSome aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.
invalid_charsetThe method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.
invalid_form_dataThe method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.
invalid_post_typeThe method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/json application/x-www-form-urlencoded multipart/form-data text/plain.
invalid_usersValue passed for users was empty or invalid.
method_deprecatedThe method has been deprecated.
missing_argumentA required argument is missing.
missing_post_typeThe method was called via a POST request and included a data payload, but the request did not include a Content-Type header.
missing_scopeThe token used is not granted the specific scope permissions required to complete this request.
no_permissionThe workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.
no_users_providedEither the users field wasn't provided or an empty value was passed.
not_allowed_token_typeThe token type used in this request is not allowed.
not_authedNo authentication token provided.
org_login_requiredThe workspace is undergoing an enterprise migration and will not be available until migration is complete.
permission_deniedThe user does not have permission to update the list of users for a user group. Check workspace settings to confirm whether the calling user has permission.
plan_upgrade_requiredThis workspace does not have access to user groups, as that feature is only available on Standard and above plans.
ratelimitedThe request has been ratelimited. Refer to the Retry-After header for when to retry the request.
request_timeoutThe method was called via a POST request, but the POST data was either missing or truncated.
service_unavailableThe service is temporarily unavailable
subteam_max_users_exceededExceeds maximum supported number of users per subteam.
team_access_not_grantedThe token used is not granted the specific workspace access required to complete this request.
team_added_to_orgThe workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.
token_expiredAuthentication token has expired
token_revokedAuthentication token is for a deleted user or workspace or the app has been removed when using a user token.
two_factor_setup_requiredTwo factor setup is required.