Method: spaces.messages.reactions.list

Lists reactions to a message. For an example, see List reactions for a message. Requires user authentication.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Required. The message users reacted to.

Format: spaces/{space}/messages/{message}

Query parameters



Optional. The maximum number of reactions returned. The service can return fewer reactions than this value. If unspecified, the default value is 25. The maximum value is 200; values above 200 are changed to 200.



Optional. (If resuming from a previous query.)

A page token received from a previous list reactions call. Provide this to retrieve the subsequent page.

When paginating, the filter value should match the call that provided the page token. Passing a different value might lead to unexpected results.



Optional. A query filter.

You can filter reactions by emoji (either emoji.unicode or emoji.custom_emoji.uid) and user (

To filter reactions for multiple emojis or users, join similar fields with the OR operator, such as emoji.unicode = "🙂" OR emoji.unicode = "👍" and = "users/AAAAAA" OR = "users/BBBBBB".

To filter reactions by emoji and user, use the AND operator, such as emoji.unicode = "🙂" AND = "users/AAAAAA".

If your query uses both AND and OR, group them with parentheses.

For example, the following queries are valid: = "users/{user}"
emoji.unicode = "🙂"
emoji.custom_emoji.uid = "{uid}"
emoji.unicode = "🙂" OR emoji.unicode = "👍"
emoji.unicode = "🙂" OR emoji.custom_emoji.uid = "{uid}"
emoji.unicode = "🙂" AND = "users/{user}"
(emoji.unicode = "🙂" OR emoji.custom_emoji.uid = "{uid}")
AND = "users/{user}"

The following queries are invalid:

emoji.unicode = "🙂" AND emoji.unicode = "👍"
emoji.unicode = "🙂" AND emoji.custom_emoji.uid = "{uid}"
emoji.unicode = "🙂" OR = "users/{user}"
emoji.unicode = "🙂" OR emoji.custom_emoji.uid = "{uid}" OR = "users/{user}"
emoji.unicode = "🙂" OR emoji.custom_emoji.uid = "{uid}"
AND = "users/{user}"

Invalid queries are rejected by the server with an INVALID_ARGUMENT error.

Request body

The request body must be empty.

Response body

Response to a list reactions request.

If successful, the response body contains data with the following structure:

JSON representation
  "reactions": [
      object (Reaction)
  "nextPageToken": string

object (Reaction)

List of reactions in the requested (or first) page.



Continuation token to retrieve the next page of results. It's empty for the last page of results.

Authorization scopes

Requires one of the following OAuth scopes:


For more information, see the Authorization guide.