messages.prolongWebView

`messages.prolongWebView`

No description provided by the pinned schema.

Signature

messages.prolongWebView#b0d81a83 flags:# silent:flags.5?true peer:InputPeer bot:InputUser query_id:long reply_to:flags.0?InputReplyTo send_as:flags.13?InputPeer = Bool;

Result type

Bool

Parameters

Name	Type	Flag	Default	Description
flags	#	flag word	—	No description provided by the pinned schema.
silent	flags.5?true	flags.5	—	No description provided by the pinned schema.
peer	InputPeer	—	—	No description provided by the pinned schema.
bot	InputUser	—	—	No description provided by the pinned schema.
query_id	long	—	—	No description provided by the pinned schema.
reply_to	flags.0?InputReplyTo	flags.0	—	No description provided by the pinned schema.
send_as	flags.13?InputPeer	flags.13	—	No description provided by the pinned schema.

Flags

Parameter	Bit	Meaning
silent	5	Controlled by `flags`; present when this bit is set.
reply_to	0	Controlled by `flags`; present when this bit is set.
send_as	13	Controlled by `flags`; present when this bit is set.

Python binding

from miniproto.raw.functions import MessagesProlongWebView

Public access: miniproto.raw.functions.MessagesProlongWebView.

Safe usage shape

from miniproto.raw.functions import MessagesProlongWebView

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

Result family

Bool

RPC errors

Code	Error	Description
400	`BOT_INVALID`	This is not a valid bot.
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.
401	`AUTH_KEY_UNREGISTERED`	The specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

Accepted types

InputPeer, InputReplyTo, InputUser Known selected constructors: inputPeerChannel, inputPeerChannelFromMessage, inputPeerChat, inputPeerEmpty, inputPeerSelf, inputPeerUser, inputPeerUserFromMessage, inputReplyToEphemeralMessage, inputReplyToMessage, inputReplyToMonoForum, inputReplyToStory, inputUser, inputUserEmpty, inputUserFromMessage, inputUserSelf

Returned types

Bool Known selected constructors: boolFalse, boolTrue

Availability evidence

user only

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

messages.prolongWebView

messages.prolongWebView

Signature

Result type

Parameters

Flags

Python binding

Safe usage shape

Result family

RPC errors

Accepted types

Returned types

Related methods

Availability evidence

Provenance

Source-diff notes

`messages.prolongWebView`