As part of the Conversations API, this method's required scopes depend on the type of channel-like object you're working with. A corresponding channels: scope is required when working with public channels, groups: for private channels, also the same rules are applied for im: and mpim:.
This method supports application/json via HTTP POST. Present your token in your request's Authorization header. Learn more.
Typical success response
Typical error response when you attempt to kick yourself from a channel
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 can't kick themselves from a channel.
User was not in the channel.
User cannot be removed from #general.
This type of conversation cannot be used with this method.
The calling token is not granted the necessary scopes to complete this operation.
A team preference prevents the authenticated user from kicking.
No authentication token provided.
Invalid authentication token.
Authentication token is for a deleted user or workspace.
The workspace token used in this request does not have the permissions necessary to complete the request.
This method cannot be called by a bot user.
This method cannot be called by a restricted user or 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.