Reactions

Delete reaction

Remove an emoji reaction from a message or forum post. Only the reaction author or a channel admin can remove a reaction.

Required permissions (one of):

  • chat:read
  • dms:read
  • forum:read
  • livestream:chat:read
  • support_chat:read
delete/reactions/{id}

Path parameters

idstring required
Example:reac_xxxxxxxxxxxxxxxxxxxxxx

The unique identifier of the reaction to remove, or the identifier of the message or forum post to remove a reaction from. When passing a message or post ID, you must also provide the emoji argument.

Query parameters

emojistring

The emoji to remove, in shortcode or unicode format. For example, ':heart:' or a unicode emoji. Required when the id refers to a message or post instead of a reaction.

Response

A successful response

boolean required

Represents true or false values.

Changes

Changed in 50 of the 74 revisions of this API.100

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

    • ○

      the security scope chat:read was added to the endpoint's security scheme bearerAuth

      api-security-scope-added

    • ○

      the security scope support_chat:read was removed from the endpoint's security scheme bearerAuth

      api-security-scope-removed

Of the 74 revisions, 1 has no diff computed.