telegram api method · layer 229 · #3b1adf37
messages.reorderPinnedDialogs
Reorder pinned dialogs
definition
messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
parameters
| name | type | description |
|---|---|---|
flags | # | Flags, see TL conditional fields |
force | true | If set, dialogs pinned server-side but not present in the order field will be unpinned. |
folder_id | int | Peer folder ID, for more info click here |
order | Vector<InputDialogPeer> | New dialog order |
returns
errors (3)
| 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 | 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 62–229 · constructor id changed 2×
| id | layers |
|---|---|
| #959ff644 | 62–74 |
| #5b51d63f | 75–98 |
| #3b1adf37 | 99–229 |