mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2025-03-30 04:19:24 +02:00
Update content of files
This commit is contained in:
GitHub Action
parent
a79494f07f
commit
d8f6f7d358
2 changed files with 22 additions and 22 deletions
data/web
|
|
@ -45,7 +45,7 @@
|
|||
<div id="dev_page_content"><!-- scroll_nav -->
|
||||
|
||||
<p>With <strong>Mini Apps</strong> developers can use <em>JavaScript</em> to create <strong>infinitely flexible interfaces</strong> that can be launched right inside Telegram — and can completely replace <strong>any website</strong>.</p>
|
||||
<p>Like bots, <strong>Mini Apps</strong> support <a href="https://telegram.org/blog/privacy-discussions-web-bots#meet-seamless-web-bots">seamless authorization</a>, <a href="https://core.telegram.org/bots/payments">integrated payments</a> via <strong>20</strong> payment providers (with <em>Google Pay</em> and <em>Apple Pay</em> out of the box), delivering tailored push notifications to users, and <a href="https://core.telegram.org/bots">much more</a>.</p>
|
||||
<p>Like bots, <strong>Mini Apps</strong> support <a href="https://telegram.org/blog/privacy-discussions-web-bots#meet-seamless-web-bots">seamless authorization</a>, <a href="/bots/payments">integrated payments</a> via <strong>20</strong> payment providers (with <em>Google Pay</em> and <em>Apple Pay</em> out of the box), delivering tailored push notifications to users, and <a href="/bots">much more</a>.</p>
|
||||
<div class="blog_video_player_wrap" style="max-width: 600px; margin: 20px auto 20px;">
|
||||
<video class="blog_video_player tl_blog_vid_autoplay" onclick="videoTogglePlay(this)" autoplay loop controls muted poster="/file/464001434/100bf/eWprjdgzEbE.100386/644bbea83084f44c8f" style="max-width: 600px;" title="console.log('Vive la révolution')" alt="Bot Revolution">
|
||||
<source src="/file/464001679/11aa9/KQx_BlPVXRo.4922145.mp4/c65433c8ac11a347a8" type="video/mp4">
|
||||
|
|
@ -79,27 +79,27 @@
|
|||
</ul>
|
||||
<p><strong>Emoji Status</strong></p>
|
||||
<ul>
|
||||
<li>Mini Apps can now prompt users to set their <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#emoji-status">emoji status</a> – or request access to later sync it automatically with in-game badges, third-party APIs and more.</li>
|
||||
<li>Mini Apps can now prompt users to set their <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#emoji-statuses-from-apps">emoji status</a> – or request access to later sync it automatically with in-game badges, third-party APIs and more.</li>
|
||||
<li>Added the method <em>setEmojiStatus</em> to let users manually confirm a custom emoji as their new status via a native dialog.</li>
|
||||
<li>Added the method <em>requestEmojiStatusAccess</em> for obtaining permission to later update a user's emoji status via the Bot API method <a href="https://core.telegram.org/bots#setuseremojistatus">setUserEmojiStatus</a>.</li>
|
||||
<li>Added the method <em>requestEmojiStatusAccess</em> for obtaining permission to later update a user's emoji status via the Bot API method <a href="/bots/api#setuseremojistatus">setUserEmojiStatus</a>.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>emojiStatusSet</em>, <em>emojiStatusFailed</em> and <em>emojiStatusAccessRequested</em>.</li>
|
||||
</ul>
|
||||
<p><strong>Media Sharing and File Downloads</strong></p>
|
||||
<ul>
|
||||
<li>Users can now <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#media-sharing">share media</a> directly from Mini Apps – sending <strong>referral codes</strong>, custom memes, artwork and more to <strong>any chat</strong> or posting them <a href="https://telegram.org/blog/w3-browser-mini-app-store#sharing-from-mini-apps-to-stories">as a story</a>.</li>
|
||||
<li>Added the method <em>shareMessage</em> to share media from Mini Apps to Telegram chats. Also see <a href="bots/api#preparedinlinemessage">PreparedInlineMessage</a>.</li>
|
||||
<li>Added the method <em>shareMessage</em> to share media from Mini Apps to Telegram chats. Also see <a href="/bots/api#preparedinlinemessage">PreparedInlineMessage</a>.</li>
|
||||
<li>Added the method <em>downloadFile</em>, introducing support for a <strong>native popup</strong> that prompts users to download files from the Mini App.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>shareMessageSent</em>, <em>shareMessageFailed</em> and <em>fileDownloadRequested</em>.</li>
|
||||
</ul>
|
||||
<p><strong>Geolocation Access</strong></p>
|
||||
<ul>
|
||||
<li>Mini Apps can now request <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#geolocation-options">geolocation access</a> to users, allowing them to build virtually any location-based service, from <strong>games</strong> with dynamic points of interest to <strong>interactive maps</strong> for events.</li>
|
||||
<li>Mini Apps can now request <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#geolocation-access">geolocation access</a> to users, allowing them to build virtually any location-based service, from <strong>games</strong> with dynamic points of interest to <strong>interactive maps</strong> for events.</li>
|
||||
<li>Added the field <em>LocationManager</em> to the class <a href="#initializing-mini-apps">WebApp</a>.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>locationManagerUpdated</em> and <em>locationRequested</em>.</li>
|
||||
</ul>
|
||||
<p><strong>Device Motion Tracking</strong></p>
|
||||
<ul>
|
||||
<li>Mini Apps can now track detailed <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#device-orientation-data">device motion data</a>, allowing them to implement better productivity tools, immersive <strong>VR experiences</strong> and more.</li>
|
||||
<li>Mini Apps can now track detailed <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#device-motion-tracking">device motion data</a>, allowing them to implement better productivity tools, immersive <strong>VR experiences</strong> and more.</li>
|
||||
<li>Added the fields <em>isOrientationLocked</em>, <em>Accelerometer</em>, <em>DeviceOrientation</em> and <em>Gyroscope</em> to the class <a href="#initializing-mini-apps">WebApp</a>.</li>
|
||||
<li>Added the methods <em>lockOrientation</em> and <em>unlockOrientation</em> to control the screen orientation.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>accelerometerStarted</em>, <em>accelerometerStopped</em>, <em>accelerometerChanged</em>, <em>accelerometerFailed</em>, <em>deviceOrientationStarted</em>, <em>deviceOrientationStopped</em>, <em>deviceOrientationChanged</em>, <em>deviceOrientationFailed</em>, <em>gyroscopeStarted</em>, <em>gyroscopeStopped</em>, <em>gyroscopeChanged</em>, <em>gyroscopeFailed</em>.</li>
|
||||
|
|
@ -239,7 +239,7 @@
|
|||
<blockquote>
|
||||
<p><strong>TL;DR:</strong> Mini Apps launched from a <strong>web_app</strong> type <a href="/bots/api#keyboardbutton">keyboard button</a> can send data back to the bot in a <em>service message</em> using <a href="#initializing-mini-apps">Telegram.WebApp.sendData</a>. This makes it possible for the bot to produce a response without communicating with any external servers.</p>
|
||||
</blockquote>
|
||||
<p>Users can interact with bots using <a href="https://core.telegram.org/bots#keyboards">custom keyboards</a>, <a href="https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating">buttons under bot messages</a>, as well as by sending freeform <strong>text messages</strong> or any of the <strong>attachment types</strong> supported by Telegram: photos and videos, files, locations, contacts and polls. For even more flexibility, bots can utilize the full power of <strong>HTML5</strong> to create user-friendly input interfaces.</p>
|
||||
<p>Users can interact with bots using <a href="/bots#keyboards">custom keyboards</a>, <a href="/bots#inline-keyboards-and-on-the-fly-updating">buttons under bot messages</a>, as well as by sending freeform <strong>text messages</strong> or any of the <strong>attachment types</strong> supported by Telegram: photos and videos, files, locations, contacts and polls. For even more flexibility, bots can utilize the full power of <strong>HTML5</strong> to create user-friendly input interfaces.</p>
|
||||
<p>You can send a <strong>web_app</strong> type <a href="/bots/api#keyboardbutton">KeyboardButton</a> that opens a Mini App from the specified URL.</p>
|
||||
<p>To transmit data from the user back to the bot, the Mini App can call the <a href="#initializing-mini-apps">Telegram.WebApp.sendData</a> method. Data will be transmitted to the bot as a String in a service message. The bot can continue communicating with the user after receiving it.</p>
|
||||
<p><strong>Good for:</strong></p>
|
||||
|
|
@ -263,7 +263,7 @@
|
|||
<blockquote>
|
||||
<p><strong>TL;DR:</strong> Mini Apps can be launched from a customized menu button. This simply offers a quicker way to access the app and is otherwise <strong>identical</strong> to <a href="#inline-button-mini-apps">launching a mini app from an inline button</a>.</p>
|
||||
</blockquote>
|
||||
<p>By default, chats with bots always show a convenient <strong>menu button</strong> that provides quick access to all listed <a href="/bots#commands">commands</a>. With <a href="https://core.telegram.org/bots/api-changelog#april-16-2022">Bot API 6.0</a>, this button can be used to <strong>launch a Mini App</strong> instead.</p>
|
||||
<p>By default, chats with bots always show a convenient <strong>menu button</strong> that provides quick access to all listed <a href="/bots#commands">commands</a>. With <a href="/bots/api-changelog#april-16-2022">Bot API 6.0</a>, this button can be used to <strong>launch a Mini App</strong> instead.</p>
|
||||
<div class="blog_video_player_wrap" style="max-width: 600px; margin: 20px auto 20px;">
|
||||
<video class="blog_video_player tl_blog_vid_autoplay" onclick="videoTogglePlay(this)" autoplay loop controls muted poster="/file/464001829/12247/e6LoU12o4Ng.109921/1226afb8f18f8ea8c4
|
||||
" style="max-width: 600px;" title="" alt="Menu Button">
|
||||
|
|
@ -287,7 +287,7 @@
|
|||
<p>If your bot is a mini app, you can unlock a number of features that streamline and simplify the way in which users view and interact with it. To do this, go to <a href="https://t.me/botfather">@BotFather</a> and set up your bot's <strong>Main Mini App</strong>.</p>
|
||||
<p>After setting a main mini app, you'll be able to upload detailed <strong>media preview demos</strong> to publicly highlight your app's key features on its profile. A <strong>Launch app</strong> button will also appear, allowing users to open your app directly from its profile. Bots that enabled a main mini app will be displayed in the <em>Apps</em> tab of the search for users who have launched them.</p>
|
||||
<blockquote>
|
||||
<p>Media previews support <a href="https://core.telegram.org/bots/features#mini-app-previews">multiple languages</a> – so you can upload <strong>translated versions</strong> of your previews that will be shown to users based on their <strong>app language</strong>.</p>
|
||||
<p>Media previews support <a href="/bots/features#mini-app-previews">multiple languages</a> – so you can upload <strong>translated versions</strong> of your previews that will be shown to users based on their <strong>app language</strong>.</p>
|
||||
</blockquote>
|
||||
<p>A bot's <strong>main Mini App</strong> can also be opened in the current chat by direct link in the format <code>https://t.me/botusername?startapp</code>. If a non-empty <em>startapp</em> parameter is included in the link, it will be passed to the Mini App in the <em>start_param</em> field and in the GET parameter <em>tgWebAppStartParam</em>. </p>
|
||||
<p><strong>Examples</strong></p>
|
||||
|
|
@ -301,7 +301,7 @@
|
|||
<li>The use cases are effectively <strong>unlimited</strong>.</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>Successful bots which <strong>enable</strong> a main Mini App and <strong>accept payments</strong> in <a href="https://core.telegram.org/bots/payments-stars">Telegram Stars</a> may be featured in the Telegram <a href="https://t.me/BotNews/99">Mini App Store</a>. To increase the chances of being featured, we recommend uploading high-quality media showcasing your app on your bot's profile and following our <a href="#design-guidelines">design guidelines</a>.</p>
|
||||
<p>Successful bots which <strong>enable</strong> a main Mini App and <strong>accept payments</strong> in <a href="/bots/payments-stars">Telegram Stars</a> may be featured in the Telegram <a href="https://t.me/BotNews/99">Mini App Store</a>. To increase the chances of being featured, we recommend uploading high-quality media showcasing your app on your bot's profile and following our <a href="#design-guidelines">design guidelines</a>.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="inline-mode-mini-apps" href="#inline-mode-mini-apps"><i class="anchor-icon"></i></a>Inline Mode Mini Apps</h4>
|
||||
<blockquote>
|
||||
|
|
@ -1956,7 +1956,7 @@ if (Ed25519_verify(public_key, data_check_string, signature)) {
|
|||
</tr>
|
||||
<tr>
|
||||
<td><code>invoiceClosed</code></td>
|
||||
<td><mark>Bot API 6.1+</mark> Occurrs when the opened invoice is closed.<br><em>eventHandler</em> receives an object with the two fields: <em>url</em> – invoice link provided and <em>status</em> – one of the invoice statuses:<br>- <strong>paid</strong> – invoice was paid successfully,<br>- <strong>cancelled</strong> – user closed this invoice without paying,<br>- <strong>failed</strong> – user tried to pay, but the payment was failed,<br>- <strong>pending</strong> – the payment is still processing. The bot will receive a service message about a <a href="https://core.telegram.org/bots/api#successfulpayment">successful payment</a> when the payment is successfully paid.</td>
|
||||
<td><mark>Bot API 6.1+</mark> Occurrs when the opened invoice is closed.<br><em>eventHandler</em> receives an object with the two fields: <em>url</em> – invoice link provided and <em>status</em> – one of the invoice statuses:<br>- <strong>paid</strong> – invoice was paid successfully,<br>- <strong>cancelled</strong> – user closed this invoice without paying,<br>- <strong>failed</strong> – user tried to pay, but the payment was failed,<br>- <strong>pending</strong> – the payment is still processing. The bot will receive a service message about a <a href="/bots/api#successfulpayment">successful payment</a> when the payment is successfully paid.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>popupClosed</code></td>
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@
|
|||
<div id="dev_page_content"><!-- scroll_nav -->
|
||||
|
||||
<p>With <strong>Mini Apps</strong> developers can use <em>JavaScript</em> to create <strong>infinitely flexible interfaces</strong> that can be launched right inside Telegram — and can completely replace <strong>any website</strong>.</p>
|
||||
<p>Like bots, <strong>Mini Apps</strong> support <a href="https://telegram.org/blog/privacy-discussions-web-bots#meet-seamless-web-bots">seamless authorization</a>, <a href="https://core.telegram.org/bots/payments">integrated payments</a> via <strong>20</strong> payment providers (with <em>Google Pay</em> and <em>Apple Pay</em> out of the box), delivering tailored push notifications to users, and <a href="https://core.telegram.org/bots">much more</a>.</p>
|
||||
<p>Like bots, <strong>Mini Apps</strong> support <a href="https://telegram.org/blog/privacy-discussions-web-bots#meet-seamless-web-bots">seamless authorization</a>, <a href="/bots/payments">integrated payments</a> via <strong>20</strong> payment providers (with <em>Google Pay</em> and <em>Apple Pay</em> out of the box), delivering tailored push notifications to users, and <a href="/bots">much more</a>.</p>
|
||||
<div class="blog_video_player_wrap" style="max-width: 600px; margin: 20px auto 20px;">
|
||||
<video class="blog_video_player tl_blog_vid_autoplay" onclick="videoTogglePlay(this)" autoplay loop controls muted poster="/file/464001434/100bf/eWprjdgzEbE.100386/644bbea83084f44c8f" style="max-width: 600px;" title="console.log('Vive la révolution')" alt="Bot Revolution">
|
||||
<source src="/file/464001679/11aa9/KQx_BlPVXRo.4922145.mp4/c65433c8ac11a347a8" type="video/mp4">
|
||||
|
|
@ -79,27 +79,27 @@
|
|||
</ul>
|
||||
<p><strong>Emoji Status</strong></p>
|
||||
<ul>
|
||||
<li>Mini Apps can now prompt users to set their <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#emoji-status">emoji status</a> – or request access to later sync it automatically with in-game badges, third-party APIs and more.</li>
|
||||
<li>Mini Apps can now prompt users to set their <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#emoji-statuses-from-apps">emoji status</a> – or request access to later sync it automatically with in-game badges, third-party APIs and more.</li>
|
||||
<li>Added the method <em>setEmojiStatus</em> to let users manually confirm a custom emoji as their new status via a native dialog.</li>
|
||||
<li>Added the method <em>requestEmojiStatusAccess</em> for obtaining permission to later update a user's emoji status via the Bot API method <a href="https://core.telegram.org/bots#setuseremojistatus">setUserEmojiStatus</a>.</li>
|
||||
<li>Added the method <em>requestEmojiStatusAccess</em> for obtaining permission to later update a user's emoji status via the Bot API method <a href="/bots/api#setuseremojistatus">setUserEmojiStatus</a>.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>emojiStatusSet</em>, <em>emojiStatusFailed</em> and <em>emojiStatusAccessRequested</em>.</li>
|
||||
</ul>
|
||||
<p><strong>Media Sharing and File Downloads</strong></p>
|
||||
<ul>
|
||||
<li>Users can now <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#media-sharing">share media</a> directly from Mini Apps – sending <strong>referral codes</strong>, custom memes, artwork and more to <strong>any chat</strong> or posting them <a href="https://telegram.org/blog/w3-browser-mini-app-store#sharing-from-mini-apps-to-stories">as a story</a>.</li>
|
||||
<li>Added the method <em>shareMessage</em> to share media from Mini Apps to Telegram chats. Also see <a href="bots/api#preparedinlinemessage">PreparedInlineMessage</a>.</li>
|
||||
<li>Added the method <em>shareMessage</em> to share media from Mini Apps to Telegram chats. Also see <a href="/bots/api#preparedinlinemessage">PreparedInlineMessage</a>.</li>
|
||||
<li>Added the method <em>downloadFile</em>, introducing support for a <strong>native popup</strong> that prompts users to download files from the Mini App.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>shareMessageSent</em>, <em>shareMessageFailed</em> and <em>fileDownloadRequested</em>.</li>
|
||||
</ul>
|
||||
<p><strong>Geolocation Access</strong></p>
|
||||
<ul>
|
||||
<li>Mini Apps can now request <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#geolocation-options">geolocation access</a> to users, allowing them to build virtually any location-based service, from <strong>games</strong> with dynamic points of interest to <strong>interactive maps</strong> for events.</li>
|
||||
<li>Mini Apps can now request <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#geolocation-access">geolocation access</a> to users, allowing them to build virtually any location-based service, from <strong>games</strong> with dynamic points of interest to <strong>interactive maps</strong> for events.</li>
|
||||
<li>Added the field <em>LocationManager</em> to the class <a href="#initializing-mini-apps">WebApp</a>.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>locationManagerUpdated</em> and <em>locationRequested</em>.</li>
|
||||
</ul>
|
||||
<p><strong>Device Motion Tracking</strong></p>
|
||||
<ul>
|
||||
<li>Mini Apps can now track detailed <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#device-orientation-data">device motion data</a>, allowing them to implement better productivity tools, immersive <strong>VR experiences</strong> and more.</li>
|
||||
<li>Mini Apps can now track detailed <a href="https://telegram.org/blog/fullscreen-miniapps-and-more#device-motion-tracking">device motion data</a>, allowing them to implement better productivity tools, immersive <strong>VR experiences</strong> and more.</li>
|
||||
<li>Added the fields <em>isOrientationLocked</em>, <em>Accelerometer</em>, <em>DeviceOrientation</em> and <em>Gyroscope</em> to the class <a href="#initializing-mini-apps">WebApp</a>.</li>
|
||||
<li>Added the methods <em>lockOrientation</em> and <em>unlockOrientation</em> to control the screen orientation.</li>
|
||||
<li>Added the <a href="#events-available-for-mini-apps">events</a> <em>accelerometerStarted</em>, <em>accelerometerStopped</em>, <em>accelerometerChanged</em>, <em>accelerometerFailed</em>, <em>deviceOrientationStarted</em>, <em>deviceOrientationStopped</em>, <em>deviceOrientationChanged</em>, <em>deviceOrientationFailed</em>, <em>gyroscopeStarted</em>, <em>gyroscopeStopped</em>, <em>gyroscopeChanged</em>, <em>gyroscopeFailed</em>.</li>
|
||||
|
|
@ -239,7 +239,7 @@
|
|||
<blockquote>
|
||||
<p><strong>TL;DR:</strong> Mini Apps launched from a <strong>web_app</strong> type <a href="/bots/api#keyboardbutton">keyboard button</a> can send data back to the bot in a <em>service message</em> using <a href="#initializing-mini-apps">Telegram.WebApp.sendData</a>. This makes it possible for the bot to produce a response without communicating with any external servers.</p>
|
||||
</blockquote>
|
||||
<p>Users can interact with bots using <a href="https://core.telegram.org/bots#keyboards">custom keyboards</a>, <a href="https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating">buttons under bot messages</a>, as well as by sending freeform <strong>text messages</strong> or any of the <strong>attachment types</strong> supported by Telegram: photos and videos, files, locations, contacts and polls. For even more flexibility, bots can utilize the full power of <strong>HTML5</strong> to create user-friendly input interfaces.</p>
|
||||
<p>Users can interact with bots using <a href="/bots#keyboards">custom keyboards</a>, <a href="/bots#inline-keyboards-and-on-the-fly-updating">buttons under bot messages</a>, as well as by sending freeform <strong>text messages</strong> or any of the <strong>attachment types</strong> supported by Telegram: photos and videos, files, locations, contacts and polls. For even more flexibility, bots can utilize the full power of <strong>HTML5</strong> to create user-friendly input interfaces.</p>
|
||||
<p>You can send a <strong>web_app</strong> type <a href="/bots/api#keyboardbutton">KeyboardButton</a> that opens a Mini App from the specified URL.</p>
|
||||
<p>To transmit data from the user back to the bot, the Mini App can call the <a href="#initializing-mini-apps">Telegram.WebApp.sendData</a> method. Data will be transmitted to the bot as a String in a service message. The bot can continue communicating with the user after receiving it.</p>
|
||||
<p><strong>Good for:</strong></p>
|
||||
|
|
@ -263,7 +263,7 @@
|
|||
<blockquote>
|
||||
<p><strong>TL;DR:</strong> Mini Apps can be launched from a customized menu button. This simply offers a quicker way to access the app and is otherwise <strong>identical</strong> to <a href="#inline-button-mini-apps">launching a mini app from an inline button</a>.</p>
|
||||
</blockquote>
|
||||
<p>By default, chats with bots always show a convenient <strong>menu button</strong> that provides quick access to all listed <a href="/bots#commands">commands</a>. With <a href="https://core.telegram.org/bots/api-changelog#april-16-2022">Bot API 6.0</a>, this button can be used to <strong>launch a Mini App</strong> instead.</p>
|
||||
<p>By default, chats with bots always show a convenient <strong>menu button</strong> that provides quick access to all listed <a href="/bots#commands">commands</a>. With <a href="/bots/api-changelog#april-16-2022">Bot API 6.0</a>, this button can be used to <strong>launch a Mini App</strong> instead.</p>
|
||||
<div class="blog_video_player_wrap" style="max-width: 600px; margin: 20px auto 20px;">
|
||||
<video class="blog_video_player tl_blog_vid_autoplay" onclick="videoTogglePlay(this)" autoplay loop controls muted poster="/file/464001829/12247/e6LoU12o4Ng.109921/1226afb8f18f8ea8c4
|
||||
" style="max-width: 600px;" title="" alt="Menu Button">
|
||||
|
|
@ -287,7 +287,7 @@
|
|||
<p>If your bot is a mini app, you can unlock a number of features that streamline and simplify the way in which users view and interact with it. To do this, go to <a href="https://t.me/botfather">@BotFather</a> and set up your bot's <strong>Main Mini App</strong>.</p>
|
||||
<p>After setting a main mini app, you'll be able to upload detailed <strong>media preview demos</strong> to publicly highlight your app's key features on its profile. A <strong>Launch app</strong> button will also appear, allowing users to open your app directly from its profile. Bots that enabled a main mini app will be displayed in the <em>Apps</em> tab of the search for users who have launched them.</p>
|
||||
<blockquote>
|
||||
<p>Media previews support <a href="https://core.telegram.org/bots/features#mini-app-previews">multiple languages</a> – so you can upload <strong>translated versions</strong> of your previews that will be shown to users based on their <strong>app language</strong>.</p>
|
||||
<p>Media previews support <a href="/bots/features#mini-app-previews">multiple languages</a> – so you can upload <strong>translated versions</strong> of your previews that will be shown to users based on their <strong>app language</strong>.</p>
|
||||
</blockquote>
|
||||
<p>A bot's <strong>main Mini App</strong> can also be opened in the current chat by direct link in the format <code>https://t.me/botusername?startapp</code>. If a non-empty <em>startapp</em> parameter is included in the link, it will be passed to the Mini App in the <em>start_param</em> field and in the GET parameter <em>tgWebAppStartParam</em>. </p>
|
||||
<p><strong>Examples</strong></p>
|
||||
|
|
@ -301,7 +301,7 @@
|
|||
<li>The use cases are effectively <strong>unlimited</strong>.</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>Successful bots which <strong>enable</strong> a main Mini App and <strong>accept payments</strong> in <a href="https://core.telegram.org/bots/payments-stars">Telegram Stars</a> may be featured in the Telegram <a href="https://t.me/BotNews/99">Mini App Store</a>. To increase the chances of being featured, we recommend uploading high-quality media showcasing your app on your bot's profile and following our <a href="#design-guidelines">design guidelines</a>.</p>
|
||||
<p>Successful bots which <strong>enable</strong> a main Mini App and <strong>accept payments</strong> in <a href="/bots/payments-stars">Telegram Stars</a> may be featured in the Telegram <a href="https://t.me/BotNews/99">Mini App Store</a>. To increase the chances of being featured, we recommend uploading high-quality media showcasing your app on your bot's profile and following our <a href="#design-guidelines">design guidelines</a>.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="inline-mode-mini-apps" href="#inline-mode-mini-apps"><i class="anchor-icon"></i></a>Inline Mode Mini Apps</h4>
|
||||
<blockquote>
|
||||
|
|
@ -1956,7 +1956,7 @@ if (Ed25519_verify(public_key, data_check_string, signature)) {
|
|||
</tr>
|
||||
<tr>
|
||||
<td><code>invoiceClosed</code></td>
|
||||
<td><mark>Bot API 6.1+</mark> Occurrs when the opened invoice is closed.<br><em>eventHandler</em> receives an object with the two fields: <em>url</em> – invoice link provided and <em>status</em> – one of the invoice statuses:<br>- <strong>paid</strong> – invoice was paid successfully,<br>- <strong>cancelled</strong> – user closed this invoice without paying,<br>- <strong>failed</strong> – user tried to pay, but the payment was failed,<br>- <strong>pending</strong> – the payment is still processing. The bot will receive a service message about a <a href="https://core.telegram.org/bots/api#successfulpayment">successful payment</a> when the payment is successfully paid.</td>
|
||||
<td><mark>Bot API 6.1+</mark> Occurrs when the opened invoice is closed.<br><em>eventHandler</em> receives an object with the two fields: <em>url</em> – invoice link provided and <em>status</em> – one of the invoice statuses:<br>- <strong>paid</strong> – invoice was paid successfully,<br>- <strong>cancelled</strong> – user closed this invoice without paying,<br>- <strong>failed</strong> – user tried to pay, but the payment was failed,<br>- <strong>pending</strong> – the payment is still processing. The bot will receive a service message about a <a href="/bots/api#successfulpayment">successful payment</a> when the payment is successfully paid.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>popupClosed</code></td>
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue