messages.deleteMessages

messages.deleteMessages

No description provided by the pinned schema.

Signature

messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;

Result type

messages.AffectedMessages

Parameters

Name	Type	Flag	Default	Description
flags	#	flag word	—	No description provided by the pinned schema.
revoke	flags.0?true	flags.0	—	No description provided by the pinned schema.
id	Vector	—	—	No description provided by the pinned schema.

Flags

Parameter	Bit	Meaning
revoke	0	Controlled by flags; present when this bit is set.

Python binding

from miniproto.raw.functions import MessagesDeleteMessages

Public access: miniproto.raw.functions.MessagesDeleteMessages.

Safe usage shape

from miniproto.raw.functions import MessagesDeleteMessages

# Naming the raw request class is local only; it performs no I/O or network request.
request_type = MessagesDeleteMessages

Result family

messages.AffectedMessages

RPC errors

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.

Accepted types

No non-primitive type relationships were found.

Returned types

messages.AffectedMessages Known selected constructors: messages.affectedMessages

Related methods

channels.deleteMessages, messages.readHistory, messages.readMessageContents

Availability evidence

• business supported

Provenance

• layer: 228
• structural source: tdlib
• canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
• prose merge precedence: TDLib → Telegram Desktop → Core JSON
• source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 228 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.

Source-diff notes

• tdlib_vs_core: changed_count=68; core_only_count=1; overlap_count=2302; tdlib_only_count=158
• tdlib_vs_tdesktop: changed_count=0; overlap_count=2448; tdesktop_only=null; tdlib_only=accessPointRule, ephemeral.editMessage, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret, updateEphemeralBotCallbackQuery