As part of the Conversations API, this method's required scopes depend on the type of channel-like object you're working with. For example, a corresponding channels: scope is required when working with public channels.
This Conversations API method invites 1-30 users to a public or private channel. The calling user must be a member of the channel.
The ID of the public or private channel to invite user(s) to.
A comma separated list of user IDs. Up to 30 users may be listed.
"value": "For public discussion of generalities",
"value": "This part of the workspace is for fun. Make fun here.",
"previous_names": [ "specifics", "abstractions", "etc" ],
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 params in the response.
Value passed for channel was invalid.
Value passed for user was invalid.
Authenticated user cannot invite themselves to a channel.
Authenticated user is not in the channel.
Invited user is already in the channel.
Channel has been archived.
User cannot be invited to this channel.
This type of conversation cannot be used with this method.
The calling token is not granted the necessary scopes to complete this operation.
URA is already in the maximum number of channels.
No authentication token provided.
Invalid authentication token.
Authentication token is for a deleted user or workspace.
This method cannot be called by a bot user.
This method cannot be called by a single channel guest.
The 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.
The method was passed a PHP-style array argument (e.g. with a name like foo). These are never valid with the Slack API.
The method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8iso-8859-1.
The method was called via a POST request with Content-Typeapplication/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.
The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/x-www-form-urlencodedmultipart/form-datatext/plain.
The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.
The 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.
The method was called via a POST request, but the POST data was either missing or truncated.
This table lists the expected warnings that this method will return.
However, other warnings can be returned in the case where the service
is experiencing unexpected trouble.
The method was called via a POST request, and recommended practice for the specified Content-Type is to include a charset parameter. However, no charset was present. Specifically, non-form-data content types (e.g. text/plain) are the ones for which charset is recommended.
The method was called via a POST request, and the specified Content-Type is not defined to understand the charset parameter. However, charset was in fact present. Specifically, form-data content types (e.g. multipart/form-data) are the ones for which charset is superfluous.