This method adds a star to an item (message, file, file comment, channel, private group, or DM) on behalf of the authenticated user.
One of file, file_comment, channel, or the combination of channel and timestamp must be specified.
Channel to add star to, or channel where the message to add star to was posted (used with timestamp).
File to add star to.
File comment to add star to.
Timestamp of the message to add star to.
After making this call, the item will be starred and a star_added event is broadcast through the RTM API for the calling user.
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 timestamp was invalid.
Message specified by channel and timestamp does not exist.
File specified by file does not exist.
File comment specified by file_comment does not exist.
Channel, private group, or DM specified by channel does not exist
file, file_comment, channel and timestamp was not specified.
The specified item has already been starred by the authenticated user.
No authentication token provided.
Invalid authentication token.
Authentication token is for a deleted user or team.
The method was passed an argument whose name falls outside the bounds of common decency. 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 team 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.