Setting this parameter to 1 triggers a testing mode where the specified token will not actually be revoked.
Present arguments as parameters in application/x-www-form-urlencoded querystring or POST body. This method does not currently accept application/json.
The response indicates whether the token was actually revoked, using a boolean revoked field.
Typical success response
Typical error response
For a workspace app, you may revoke either a long-lived refresh token or a short-lived access token. In both cases, the token is revoked without further side effects: the app is not uninstalled. To uninstall a workspace app, use the app.uninstall method.
Revoking all user tokens an app has for a workspace will result in the app becoming uninstalled.
Revoking a bot user token will not uninstall the bot user or the app. It essentially resets the token value and you can obtain it again through another run through of the OAuth process. Internal integrations and apps installed only on your team offer the new bot user token in your app management console.
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.
Incompatible token type provided
The 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.
No authentication token provided.
Some 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.
Authentication token is for a deleted user or workspace.
Authentication token is for a deleted user or workspace or the app has been removed.
The 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.
The workspace is undergoing an enterprise migration and will not be available until migration is complete.
Administrators have suspended the ability to post a message.
The token used is not granted the specific scope permissions required to complete this request.
The token type used in this request is not allowed.
The method has been deprecated.
The endpoint has been deprecated.
Two factor setup is required.
The method cannot be called from an Enterprise.
The method was either called with invalid arguments or some detail about the arguments passed are invalid, which is more likely when using complex arguments like blocks or attachments.
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 an array as an argument. Please only input valid strings.
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/jsonapplication/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 request has been ratelimited. Refer to the Retry-After header for when to retry the request.
Access to this method is limited on the current network
The method was called via a POST request, but the POST data was either missing or truncated.
The service is temporarily unavailable
The 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.
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.