diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index 0154543e8b..a5c3ce716e 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -58,7 +58,7 @@
These links should be handled as follows:
bot_username
is indeed a bot username, if so thenshort_name
contained in the appname
query string parametershort_name
contained in the appname
query string parameter.peer
; otherwise pass the bot's peer information, instead.inactive
flag is set, ask confirmation from the user before opening the web app.startapp
query string parameter is present, pass it to start_param
when invoking messages.requestAppWebView.request_write_access
flag is set, the bot is asking permission to send messages to the user: if the user agrees, set the write_allowed
flag when invoking messages.requestAppWebView.Open a bot web app from a bot web app deep link, sending over user information after user confirmation.
+After calling this method, until the user closes the webview, messages.prolongWebView must be called every 60 seconds.
+startapp
query string parameter is present in the bot web app deep link, pass it to start_param
.Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
+Bots can offer users interactive HTML5 web apps to completely replace any website.
+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.