Reactions

Retrieve reaction

Retrieves the details of an existing reaction.

Required permissions (one of):

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

Path parameters

idstring required
Example:reac_xxxxxxxxxxxxxxxxxxxxxx

The unique identifier of the reaction to retrieve.

Response

A successful response

emojistring nullable required

The emoji used for this reaction in shortcode format. Null if the reaction type is not emoji.

idstring required

The unique identifier for the entity

resource_idstring required

The unique identifier of the post this reaction was left on.

Example response

{
  "emoji": ":heart:",
  "id": "reac_xxxxxxxxxxxxxxxxxxxxxx",
  "user": {
    "id": "user_xxxxxxxxxxxxx",
    "name": "John Doe",
    "username": "johndoe42"
  }
}

Changes

Changed in 19 of the 41 revisions of this API.38

    • 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

    This revision also has 42 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

    This revision also has 6 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

    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