diff --git a/data/web/corefork.telegram.org/api/bots/webapps.html b/data/web/corefork.telegram.org/api/bots/webapps.html index 16c51d7c8e..87dd25f6ae 100644 --- a/data/web/corefork.telegram.org/api/bots/webapps.html +++ b/data/web/corefork.telegram.org/api/bots/webapps.html @@ -153,7 +153,7 @@ The webview must be closed after invoking the messages.requestWebView, and then open a webview using the url contained in the returned webViewResultUrl.

After loading the webview, until it is closed by a web_app_close event, the user client must invoke messages.prolongWebView every 60 seconds: if the method call returns QUERY_ID_INVALID, the webview must be closed.

The opened URL's fragment parameters already contain basic information about the user and a query_id parameter, that is exposed by the bot web apps JS library: this query_id can then be used by the bot to invoke messages.sendWebViewResultMessage, passing an InputBotInlineResult constructor that will automatically send a message with optionally attached media, and even inline buttons on behalf of the user.

-

Bot web apps

+

Named bot web apps

Schema:

inputBotAppID#a920bd7a id:long access_hash:long = InputBotApp;
 inputBotAppShortName#908c0407 bot_id:InputUser short_name:string = InputBotApp;
@@ -172,7 +172,7 @@ The webview must be closed after invoking the bot web app links ».  

+
Another way to open web apps is by using named bot web app links ».  

 
These links are different from bot attachment menu deep links », because they don't require the user to install an attachment menu, and a single bot can offer multiple web apps, distinguished by their short_name.  

 
These links should be handled as follows:  

 
 
New Constructors