messages.prolongWebView

Indicate to the server (from the user side) that the user is still using a web app.If the method returns a QUERY_ID_INVALID error, the webview must be closed.

API section: Working with Mini Bot Apps »

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;

Parameters

NameTypeDescription
flags # Bit mask: a field written flags.N?T is present only when bit N is set.
silent flags.5?true Send without sound: the recipient gets no notification.
peer InputPeer The user or chat the request is about.
bot InputUser Bot.
query_id long Query identifier — return it with the answer.
reply_to flags.0?InputReplyTo What the message replies to.
send_as flags.13?InputPeer Which identity to send as — a channel or another profile.

Result

Bool

Possible errors

Read out of the handler itself — this is what the server actually returns for this method.

CodeTypeWhat it means
400 QUERY_ID_INVALID The query identifier was not recognised or has expired.

Common to every call

CodeTypeWhat it means
401 AUTH_KEY_UNREGISTERED The server does not know this session: the key was revoked, expired, or the call was made before authorisation.
401 API_ID_INVALID This api_id was never issued or has been blocked. Keys come from my.ansible.su.
400 CONNECTION_LAYER_INVALID The client did not declare a layer, or declared one the server does not know.
420 FLOOD_WAIT_X Too often. Do not retry for X seconds — the number arrives in the error text.
500 INTERNAL A failure on our side. The request may be retried; if it keeps failing, it is a bug of ours.

Related pages

Types used here