--- title: "reactions.add API method" summary: "Adds a reaction to an item." url: "https://docs.slack.dev/reference/methods/reactions.add" type: "reference" subtype: "method" method_name: "reactions.add" http_method: "POST" rate_limit: "t3" scopes: bot: ["reactions:write"] user: ["reactions:write"] --- Source: https://docs.slack.dev/reference/methods/reactions.add # reactions.add method DocsCall generator ## Facts {#facts} **Description**Adds a reaction to an item. **Method Access** * HTTP * Slack CLI * JavaScript * Python * Java ``` POST https://slack.com/api/reactions.add ``` [![slack-cli](/img/logos/slack-cli.png)](/tools/slack-cli) ``` slack api reactions.add ``` [![bolt-js](/img/logos/bolt-js-logo.svg)](/tools/bolt-js) ``` app.client.reactions.add ``` [![bolt-py](/img/logos/bolt-py-logo.svg)](/tools/bolt-python) ``` app.client.reactions_add ``` [![bolt-java](/img/logos/bolt-java-logo.svg)](/tools/java-slack-sdk/guides/getting-started-with-bolt) ``` app.client().reactionsAdd ``` **Scopes** Bot token: [`reactions:write`](https://docs.slack.dev/reference/scopes/reactions.write.md) User token: [`reactions:write`](https://docs.slack.dev/reference/scopes/reactions.write.md) **Content types** `application/x-www-form-urlencoded` `application/json` **Rate Limits**[Tier 3: 50+ per minute](https://docs.slack.dev/apis/web-api/rate-limits.md) ## Arguments {#arguments} ### Required arguments **`channel`**`string`Required Channel where the message to add reaction to was posted. **`name`**`string`Required Reaction (emoji) name _Example:_ `thumbsup` **`timestamp`**`string`Required Timestamp of the message to add reaction to. **`token`**`string`Required Authentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter. _Example:_ `xxxx-xxxxxxxxx-xxxx` ## Usage info {#usage-info} This method adds a reaction (emoji) to a message. Now that [file threads](https://docs.slack.dev/changelog/2018-05-file-threads-soon-tread.md#what-changed) work the way you'd expect, the `file` and `file_comment` arguments are deprecated. Specify only `channel` and `timestamp` instead. For Unicode emoji that support [skin tone modifiers](https://emojipedia.org/emoji-modifier-sequence/), `name` may indicate a modifier by appending `::skin-tone-` and a number from 2 to 6, like, `thumbsup::skin-tone-6` or `wave::skin-tone-3`. This will add a reaction with the base emoji and the specified skin color. * * * ## Response {#response} #### Typical success response ``` { "ok": true} ``` #### Typical error response ``` { "error": "already_reacted", "ok": false} ``` After making this call, the reaction is saved and [a `reaction_added` event](https://docs.slack.dev/reference/events/reaction_added.md) is broadcast via the [Events](https://docs.slack.dev/apis/events-api.md) and [RTM](https://docs.slack.dev/legacy/legacy-rtm-api.md) APIs. A `not_reactable` error is thrown when we decline the opportunity to attach your app's personally selected emoji reaction to a file or file comment. It's not because of how your app feels, it's because that approach is retired. Your app can express its inner reacji for any message though, by specifying `channel` and `timestamp`. ## Errors {#errors} 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` parameter in the response. Error Description `access_denied` Access to a resource specified in the request is denied. `accesslimited` Access to this method is limited on the current network `account_inactive` Authentication token is for a deleted user or workspace when using a `bot` token. `already_reacted` The specified item already has the user/reaction combination. `bad_timestamp` Value passed for `timestamp` was invalid. `channel_not_found` Value passed for `channel` is invalid. `deprecated_endpoint` The endpoint has been deprecated. `ekm_access_denied` Administrators have suspended the ability to post a message. `enterprise_is_restricted` The method cannot be called from an Enterprise. `external_channel_migrating` The channel is in the process of being migrated. `fatal_error` 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. `internal_error` 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. `invalid_arg_name` 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. `invalid_arguments` The method was called with invalid arguments. `invalid_array_arg` The method was passed an array as an argument. Please only input valid strings. `invalid_auth` 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. `invalid_charset` 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`. `invalid_form_data` 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. `invalid_name` Value passed for `name` was invalid. `invalid_post_type` The method was called via a `POST` request, but the specified `Content-Type` was invalid. Valid types are: `application/json` `application/x-www-form-urlencoded` `multipart/form-data` `text/plain`. `is_archived` Channel specified has been archived. `message_not_found` Message specified by `channel` and `timestamp` does not exist. `method_deprecated` The method has been deprecated. `missing_argument` A required argument was not provided. The response's `arg` field names the missing argument. Arguments sent in a JSON body are ignored by methods that don't list `application/json` as a content type. `missing_post_type` The method was called via a `POST` request and included a data payload, but the request did not include a `Content-Type` header. `missing_scope` The token used is not granted the specific scope permissions required to complete this request. `no_access` User does not have access to react to this canvas. `no_item_specified` combination of `channel` and `timestamp` was not specified. `no_permission` 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. `not_allowed_token_type` The token type used in this request is not allowed. `not_authed` No authentication token provided. `not_reactable` Whatever you passed in, like a `file` or `file_comment`, can't be reacted to anymore. Your app can react to messages though. `org_login_required` The workspace is undergoing an enterprise migration and will not be available until migration is complete. `ratelimited` The request has been ratelimited. Refer to the `Retry-After` header for when to retry the request. `request_timeout` The method was called via a `POST` request, but the `POST` data was either missing or truncated. `service_unavailable` The service is temporarily unavailable `team_access_not_granted` The token used is not granted the specific workspace access required to complete this request. `team_added_to_org` 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. `thread_locked` Reactions are disabled as the specified message is part of a locked thread. `token_expired` Authentication token has expired `token_revoked` Authentication token is for a deleted user or workspace or the app has been removed when using a `user` token. `too_many_emoji` The limit for distinct reactions (i.e emoji) on the item has been reached. `too_many_reactions` The limit for reactions a person may add to the item has been reached. `two_factor_setup_required` Two factor setup is required.