telegram api method · layer 229 · #8107455c
messages.toggleSuggestedPostApproval
Approve or reject a suggested post ».
definition
messages.toggleSuggestedPostApproval#8107455c flags:# reject:flags.1?true peer:InputPeer msg_id:int schedule_date:flags.0?int reject_comment:flags.2?string = Updates;
parameters
| name | type | description |
|---|---|---|
flags | # | Flags, see TL conditional fields |
reject | true | Reject the suggested post. |
peer | InputPeer | Both for users and channels, must contain the ID of the direct messages monoforum » (for channels, the topic ID is extracted automatically from the msg_id). |
msg_id | int | ID of the suggestion message. |
schedule_date | int | Custom scheduling date. |
reject_comment | string | Optional comment for rejections (can only be used if reject is set). |
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 206–229
| id | layers |
|---|---|
| #8107455c | 206–229 |