telegram api method · layer 229 · #f516760b
messages.getScheduledHistory
Get scheduled messages
definition
messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
parameters
| name | type | description |
|---|---|---|
peer | InputPeer | Peer |
hash | long | Hash 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
errors (4)
| code | error | description |
|---|---|---|
| 400 | BUSINESS_CONNECTION_NOT_ALLOWED | This 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. |
| 400 | CHAT_ADMIN_REQUIRED | You must be an admin in this chat to do this. |
| 400 | PEER_ID_INVALID | The provided peer id is invalid. |
| 401 | AUTH_KEY_UNREGISTERED | The 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×
| id | layers |
|---|---|
| #e2c2685b | 105–132 |
| #f516760b | 133–229 |