telegram api method · layer 229 · #b9b2881f

stories.getStoryReactionsList

usable by users

Get the reaction and interaction list of a story posted to a channel, along with the sender of each reaction.

definition

stories.getStoryReactionsList#b9b2881f flags:# forwards_first:flags.2?true peer:InputPeer id:int reaction:flags.0?Reaction offset:flags.1?string limit:int = stories.StoryReactionsList;

parameters

nametypedescription
flags#Flags, see TL conditional fields
forwards_firstflags.2?trueIf set, returns forwards and reposts first, then reactions, then other views; otherwise returns interactions sorted just by interaction date.
peerInputPeerChannel
idintStory ID
reactionflags.0?ReactionGet only reactions of this type
offsetflags.1?stringOffset for pagination (taken from the next_offset field of the returned stories.StoryReactionsList); empty in the first request.
limitintMaximum number of results to return, see pagination

returns

stories.StoryReactionsList

errors (3)

codeerrordescription
400BUSINESS_CONNECTION_NOT_ALLOWEDThis method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we're a user, and users cannot invoke methods over a business connection; (2) we're a bot, but business mode was disabled in @botfather or (3); we're a bot, but this method cannot be invoked over a business connection.
400PEER_ID_INVALIDThe provided peer id is invalid.
401AUTH_KEY_UNREGISTEREDThe specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

history

present in layers 168–229

idlayers
#b9b2881f168–229