You must enable javascript in order to use the Slack API Documentation. You can do this in your browser settings.
Go to Slack


Removes a star from an item.


Method URL:
Preferred HTTP method: POST
Accepted content types: application/x-www-form-urlencoded, application/json
Rate limiting: Tier 2
Works with:
Token type Required scope(s)
bot bot
user stars:write post

This method removes a star from 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.


Argument Example Required Description
token xxxx-xxxxxxxxx-xxxx Required

Authentication token bearing required scopes.

channel C1234567890 Optional

Channel to remove star from, or channel where the message to remove star from was posted (used with timestamp).

file F1234567890 Optional

File to remove star from.

file_comment Fc1234567890 Optional

File comment to remove star from.

timestamp 1234567890.123456 Optional

Timestamp of the message to remove star from.

This method supports application/json via HTTP POST. Present your token in your request's Authorization header. Learn more.


    "ok": true

After making this call, the item will be unstarred and a star_removed 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.

Error Description

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 is not currently starred by the authenticated user.


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.


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[7]). 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-8 iso-8859-1.


The 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.


The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/x-www-form-urlencoded multipart/form-data text/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.


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.

Warning Description

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.