telegram api method · layer 229 · #f516760b

messages.getScheduledHistory

usable by users

Get scheduled messages

definition

messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;

parameters

nametypedescription
peerInputPeerPeer
hashlongHash used for caching, for more info click here. To generate the hash, populate the ids array with the id, edit_date (0 if unedited) and date (in this order) of the previously returned messages (in order, i.e. ids = [id1, (edit_date1 ?? 0), date1, id2, (edit_date2 ?? 0), date2, ...]).

returns

messages.Messages

errors (4)

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.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
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 105–229 · constructor id changed 1×

idlayers
#e2c2685b105–132
#f516760b133–229