telegram api method · layer 229 · #e58e95d2
messages.deleteMessages
Deletes messages by their identifiers.
definition
messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
parameters
| name | type | description |
|---|---|---|
flags | # | Flags, see TL conditional fields |
revoke | true | Whether to delete messages for all participants of the chat |
id | Vector<int> | Message ID list |
returns
errors (7)
| code | error | description |
|---|---|---|
| 400 | BUSINESS_CONNECTION_INVALID | The connection_id passed to the wrapping invokeWithBusinessConnection call is invalid. |
| 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 | MESSAGE_ID_INVALID | The provided message id is invalid. |
| 400 | SELF_DELETE_RESTRICTED | Business bots can't delete messages just for the user, revoke must be set. |
| 401 | AUTH_KEY_UNREGISTERED | The specified authorization key is not registered in the system (for example, a PFS temporary key has expired). |
| 403 | BOT_ACCESS_FORBIDDEN | The specified method *can* be used over a business connection for some operations, but the specified query attempted an operation that is not allowed over a business connection. |
| 403 | MESSAGE_DELETE_FORBIDDEN | You can't delete one of the messages you tried to delete, most likely because it is a service message. |
history
present in layers 2–229 · constructor id changed 2×
| id | layers |
|---|---|
| #14f2dd0a | 2–23 |
| #a5f18925 | 46 |
| #e58e95d2 | 62–229 |