errors - All error messages and codes for each method (object).- Keys: Error codes as strings (numeric strings) diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index 017f2a189b..6f13f39f03 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -83,6 +83,11 @@ Layer…">
- Added thumb_document_id parameter in stickerSet
- Added additional_methods parameter, changed type of saved_credentials from flags.1?PaymentSavedCredentials to flags.1?Vector<PaymentSavedCredentials> in payments.paymentForm
PUSH notification changes
+New PUSH notifications
+-
+
- Added MESSAGE_RECURRING_PAY -
{1} were charged {2}
+
Schema
userFull#c4b1fc3f flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true voice_messages_forbidden:flags.20?true id:long about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string private_forward_name:flags.16?string bot_group_admin_rights:flags.17?ChatAdminRights bot_broadcast_admin_rights:flags.18?ChatAdminRights premium_gifts:flags.19?Vector<PremiumGiftOption> = UserFull;
stickerSet#2dd14edc flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true emojis:flags.7?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int thumb_document_id:flags.8?long count:int hash:int = StickerSet;
diff --git a/data/web/corefork.telegram.org/api/push-updates.html b/data/web/corefork.telegram.org/api/push-updates.html
index 26cb2cb3e9..074870bfa5 100644
--- a/data/web/corefork.telegram.org/api/push-updates.html
+++ b/data/web/corefork.telegram.org/api/push-updates.html
@@ -692,6 +692,11 @@
1. User name
2. Quiz name
+MESSAGE_RECURRING_PAY
+{1} were charged {2}
+1.
2.
+
+
MESSAGE_ROUND
{1} sent you a video message
1. User name
diff --git a/data/web/corefork.telegram.org/bots/webapps.html b/data/web/corefork.telegram.org/bots/webapps.html
index da4d44c922..ba519fc66d 100644
--- a/data/web/corefork.telegram.org/bots/webapps.html
+++ b/data/web/corefork.telegram.org/bots/webapps.html
@@ -49,14 +49,15 @@
+
+
To see a Web App in action, try our sample @DurgerKingBot.
-Recent changes
-June 20, 2022
+Recent changes
+June 20, 2022
Bot API 6.1
- Added the ability to use bots added to the attachment menu in group, supergroup and channel chats.
@@ -68,18 +69,19 @@
- Added the events backButtonClicked, settingsButtonClicked, invoiceClosed.
-Designing Web Apps
-Color Schemes
-Web Apps always receive data about the user's current color theme in real time, so you can adjust the appearance of your interfaces to match it. For example, when users switch between Day and Night modes or use various custom themes.
+Designing Web Apps
+Color Schemes
+Web Apps always receive data about the user's current color theme in real time, so you can adjust the appearance of your interfaces to match it. For example, when users switch between Day and Night modes or use various custom themes.
+
+
-Design Guidelines
+Design Guidelines
Telegram apps are known for being snappy, smooth and following a consistent cross-platform design. Your Web App should ideally reflect these principles.
- All elements should be responsive and designed with a mobile-first approach.
@@ -89,12 +91,13 @@
- The app should deliver a seamless experience by monitoring the dynamic theme-based colors provided by the API and using them accordingly.
-Implementing Web Apps
-Telegram currently supports four different ways of launching Web Apps: from a keyboard button, from an inline button, from the bot menu button – and even from the attachment menu.
+Implementing Web Apps
+Telegram currently supports four different ways of launching Web Apps: from a keyboard button, from an inline button, from the bot menu button – and even from the attachment menu.
- 
+
-Keyboard Button Web Apps
+
+Keyboard Button Web Apps
TL;DR: Web Apps launched from a web_app type keyboard button can send data back to the bot in a service message using Telegram.WebApp.sendData. This makes it possible for the bot to produce a response without communicating with any external servers.
@@ -103,22 +106,22 @@
To transmit data from the user back to the bot, the Web App can call the Telegram.WebApp.sendData 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.
Good for:
-- Custom data input interfaces (a personalized calendar for selecting dates; selecting data from a list with advanced search options; a randomizer that lets the user "spin a wheel" and chooses one of the available options, etc.)
+- Custom data input interfaces (a personalized calendar for selecting dates; selecting data from a list with advanced search options; a randomizer that lets the user “spin a wheel” and chooses one of the available options, etc.)
- Reusable components that do not depend on a particular bot.
-Inline Button Web Apps
+Inline Button Web Apps
TL;DR: For more interactive Web Apps like @DurgerKingBot, use a web_app type Inline KeyboardButton, which gets basic user information and can be used to send a message on behalf of the user to the chat with the bot.
If receiving text data alone is insufficient or you need a more advanced and personalized interface, you can open a Web App using a web_app type Inline KeyboardButton.
-From the button, a Web App will open with the URL specified in the button. In addition to the user's theme settings, it will receive basic user information (ID, name, username, language_code) and a unique identifier for the session, query_id, which allows messages on behalf of the user to be sent back to the bot.
+From the button, a Web App will open with the URL specified in the button. In addition to the user's theme settings, it will receive basic user information (ID, name, username, language_code) and a unique identifier for the session, query_id, which allows messages on behalf of the user to be sent back to the bot.
The bot can call the Bot API method answerWebAppQuery to send an inline message from the user back to the bot and close the Web App. After receiving the message, the bot can continue communicating with the user.
Good for:
- Fully-fledged web services and integrations of any kind.
- The use cases are effectively unlimited.
-Launching Web Apps from the Menu Button
+Launching Web Apps from the Menu Button
TL;DR: Web Apps can be launched from a customized menu button. This simply offers a quicker way to access the app and is otherwise identical to launching a Web App from an inline button.
@@ -127,34 +130,35 @@
+
+
To configure the menu button, you must specify the text it should show and the Web App URL. There are two ways to set these parameters:
- To customize the button for all users, use @BotFather (the
/setmenubutton command or Bot Settings > Menu Button).
-- To customize the button for both all users and specific users, use the setChatMenuButton method in the Bot API. For example, change the button text according to the user's language, or show links to different Web Apps based on a user's settings in your bot.
+- To customize the button for both all users and specific users, use the setChatMenuButton method in the Bot API. For example, change the button text according to the user's language, or show links to different Web Apps based on a user's settings in your bot.
Apart from this, Web Apps opened via the menu button work in the exact same way as when using inline buttons.
@DurgerKingBot allows launching its Web App both from an inline button and from the menu button.
-Launching Web Apps from the Attachment Menu
+Launching Web Apps from the Attachment Menu
-TL;DR: Web App Bots can request to be added directly to a user's attachment menu, allowing them to be quickly launched from any chat. To try this mode, open this attachment menu link for @DurgerKingBot, then use the 
menu in any type of chat.
+TL;DR: Web App Bots can request to be added directly to a user's attachment menu, allowing them to be quickly launched from any chat. To try this mode, open this attachment menu link for @DurgerKingBot, then use the menu in any type of chat.
-Web App Bots can request to be added directly to a user's attachment menu, allowing them to be quickly launched from any type of chat. ^==NEW==^ You can configure in which types of chats your web app can be started from the attachment menu (private, groups, supergroups or channels).
-Attachment menu integration is currently only available for major advertisers on the Telegram Ad Platform. However, all bots can use it in the test server environment.
-To enable this feature for your bot, open @BotFather from an account on the test server and send the /setattach command – or go to Bot Settings > Configure Attachment Menu. Then specify the URL that will be opened to launch the bot's Web App via its icon in the attachment menu.
-^==NEW==^ You can add a 'Settings' item to the context menu of your Web App using @BotFather. When users select this option from the menu, your bot will receive a settingsButtonClicked event.
-In addition to the user's theme settings, the bot will receive basic user information (ID, name, username, language_code, photo), as well as public info about the chat partner (ID, name, username, photo) or the chat info (ID, type, title, username, photo) and a unique identifier for the web view session query_id, which allows messages of any type to be sent to the chat on behalf of the user that opened the bot.
+Web App Bots can request to be added directly to a user's attachment menu, allowing them to be quickly launched from any type of chat. NEW You can configure in which types of chats your web app can be started from the attachment menu (private, groups, supergroups or channels).
+Attachment menu integration is currently only available for major advertisers on the Telegram Ad Platform. However, all bots can use it in the test server environment.
+To enable this feature for your bot, open @BotFather from an account on the test server and send the /setattach command – or go to Bot Settings > Configure Attachment Menu. Then specify the URL that will be opened to launch the bot's Web App via its icon in the attachment menu.
+NEW You can add a 'Settings' item to the context menu of your Web App using @BotFather. When users select this option from the menu, your bot will receive a settingsButtonClicked event.
+In addition to the user's theme settings, the bot will receive basic user information (ID, name, username, language_code, photo), as well as public info about the chat partner (ID, name, username, photo) or the chat info (ID, type, title, username, photo) and a unique identifier for the web view session query_id, which allows messages of any type to be sent to the chat on behalf of the user that opened the bot.
The bot can call the Bot API method answerWebAppQuery, which sends an inline message from the user via the bot to the chat where it was launched and closes the Web App.
You can read more about adding bots to the attachment menu here.
-Initializing Web Apps
+Initializing Web Apps
To connect your Web App to the Telegram client, place the script telegram-web-app.js in the <head> tag before any other scripts, using this code:
-<script src="https://telegram.org/js/telegram-web-app.js"></script>
+<script src="https://telegram.org/js/telegram-web-app.js"></script>
Once the script is connected, a window.Telegram.WebApp object will become available with the following fields:
@@ -168,22 +172,22 @@
initData
String
-A string with raw data transferred to the Web App, convenient for validating data.
WARNING: Validate data from this field before using it on the bot's server.
+A string with raw data transferred to the Web App, convenient for validating data.
WARNING: Validate data from this field before using it on the bot's server.
initDataUnsafe
WebAppInitData
-An object with input data transferred to the Web App.
WARNING: Data from this field should not be trusted. You should only use data from initData on the bot's server and only after it has been validated.
+An object with input data transferred to the Web App.
WARNING: Data from this field should not be trusted. You should only use data from initData on the bot's server and only after it has been validated.
-version ^==NEW==^
+version NEW
String
-The version of the Bot API available in the user's Telegram app.
+The version of the Bot API available in the user's Telegram app.
colorScheme
String
-The color scheme currently used in the Telegram app. Either “light” or “dark”.
Also available as the CSS variable var(--tg-color-scheme).
+The color scheme currently used in the Telegram app. Either “light” or “dark”.
Also available as the CSS variable var(--tg-color-scheme).
themeParams
@@ -198,25 +202,25 @@
viewportHeight
Float
-The current height of the visible area of the Web App. Also available in CSS as the variable var(--tg-viewport-height).
The application can display just the top part of the Web App, with its lower part remaining outside the screen area. From this position, the user can "pull" the Web App to its maximum height, while the bot can do the same by calling the expand() method. As the position of the Web App changes, the current height value of the visible area will be updated in real time.
Please note that the refresh rate of this value is not sufficient to smoothly follow the lower border of the window. It should not be used to pin interface elements to the bottom of the visible area. It's more appropriate to use the value of the viewportStableHeight field for this purpose.
+The current height of the visible area of the Web App. Also available in CSS as the variable var(--tg-viewport-height).
The application can display just the top part of the Web App, with its lower part remaining outside the screen area. From this position, the user can “pull” the Web App to its maximum height, while the bot can do the same by calling the expand() method. As the position of the Web App changes, the current height value of the visible area will be updated in real time.
Please note that the refresh rate of this value is not sufficient to smoothly follow the lower border of the window. It should not be used to pin interface elements to the bottom of the visible area. It's more appropriate to use the value of the viewportStableHeight field for this purpose.
viewportStableHeight
Float
-The height of the visible area of the Web App in its last stable state. Also available in CSS as a variable var(--tg-viewport-stable-height).
The application can display just the top part of the Web App, with its lower part remaining outside the screen area. From this position, the user can "pull" the Web App to its maximum height, while the bot can do the same by calling the expand() method. Unlike the value of viewportHeight, the value of viewportStableHeight does not change as the position of the Web App changes with user gestures or during animations. The value of viewportStableHeight will be updated after all gestures and animations are completed and the Web App reaches its final size.
Note the event viewportChanged with the passed parameter isStateStable=true, which will allow you to track when the stable state of the height of the visible area changes.
+The height of the visible area of the Web App in its last stable state. Also available in CSS as a variable var(--tg-viewport-stable-height).
The application can display just the top part of the Web App, with its lower part remaining outside the screen area. From this position, the user can “pull” the Web App to its maximum height, while the bot can do the same by calling the expand() method. Unlike the value of viewportHeight, the value of viewportStableHeight does not change as the position of the Web App changes with user gestures or during animations. The value of viewportStableHeight will be updated after all gestures and animations are completed and the Web App reaches its final size.
Note the event viewportChanged with the passed parameter isStateStable=true, which will allow you to track when the stable state of the height of the visible area changes.
-headerColor ^==NEW==^
+headerColor NEW
String
Current header color in the #RRGGBB format.
-backgroundColor ^==NEW==^
+backgroundColor NEW
String
Current background color in the #RRGGBB format.
-BackButton ^==NEW==^
+BackButton NEW
BackButton
An object for controlling the back button which can be displayed in the header of the Web App in the Telegram interface.
@@ -226,24 +230,24 @@
An object for controlling the main button, which is displayed at the bottom of the Web App in the Telegram interface.
-HapticFeedback ^==NEW==^
+HapticFeedback NEW
HapticFeedback
An object for controlling haptic feedback.
-isVersionAtLeast(version) ^==NEW==^
+isVersionAtLeast(version) NEW
Function
-Returns true if the user's app supports a version of the Bot API that is equal to or higher than the version passed as the parameter.
+Returns true if the user's app supports a version of the Bot API that is equal to or higher than the version passed as the parameter.
-setHeaderColor(color) ^==NEW==^
+setHeaderColor(color) NEW
Function
-==Bot API 6.1+== A method that sets the app header color. You can only pass Telegram.WebApp.themeParams.bg_color or Telegram.WebApp.themeParams.secondary_bg_color as a color or you can use keywords bg_color, secondary_bg_color instead.
+Bot API 6.1+ A method that sets the app header color. You can only pass Telegram.WebApp.themeParams.bg_color or Telegram.WebApp.themeParams.secondary_bg_color as a color or you can use keywords bg_color, secondary_bg_color instead.
-setBackgroundColor(color) ^==NEW==^
+setBackgroundColor(color) NEW
Function
-==Bot API 6.1+== A method that sets the app background color in the #RRGGBB format or you can use keywords bg_color, secondary_bg_color instead.
+Bot API 6.1+ A method that sets the app background color in the #RRGGBB format or you can use keywords bg_color, secondary_bg_color instead.
onEvent(eventType, eventHandler)
@@ -261,24 +265,24 @@
A method used to send data to the bot. When this method is called, a service message is sent to the bot containing the data data of the length up to 4096 bytes, and the Web App is closed. See the field web_app_data in the class Message.
This method is only available for Web Apps launched via a Keyboard button.
-openLink(url) ^==NEW==^
+openLink(url) NEW
Function
-A method that opens a link in an external browser. The Web App will not be closed.
Note that this method can be called only in response to the user interaction with the Web App interface (e.g. click inside the Web App or on the main button)
+A method that opens a link in an external browser. The Web App will not be closed.
Note that this method can be called only in response to the user interaction with the Web App interface (e.g. click inside the Web App or on the main button)
-openTelegramLink(url) ^==NEW==^
+openTelegramLink(url) NEW
Function
A method that opens a telegram link inside Telegram app. The Web App will be closed.
-openInvoice(url[, callback]) ^==NEW==^
+openInvoice(url[, callback]) NEW
Function
-==Bot API 6.1+== A method that opens an invoice using the link url. The Web App will receive the event invoiceClosed when the invoice is closed. If an optional callback parameter was passed, the callback function will be called and the invoice status will be passed as the first argument.
+Bot API 6.1+ A method that opens an invoice using the link url. The Web App will receive the event invoiceClosed when the invoice is closed. If an optional callback parameter was passed, the callback function will be called and the invoice status will be passed as the first argument.
ready()
Function
-A method that informs the Telegram app that the Web App is ready to be displayed.
It is recommended to call this method as early as possible, as soon as all essential interface elements are loaded. Once this method is called, the loading placeholder is hidden and the Web App is shown.
If the method is not called, the placeholder will be hidden only when the page is fully loaded.
+A method that informs the Telegram app that the Web App is ready to be displayed.
It is recommended to call this method as early as possible, as soon as all essential interface elements are loaded. Once this method is called, the loading placeholder is hidden and the Web App is shown.
If the method is not called, the placeholder will be hidden only when the page is fully loaded.
expand()
@@ -292,8 +296,8 @@
-ThemeParams
-Web Apps can adjust the appearance of the interface to match the Telegram user's app in real time. This object contains the user's current theme settings:
+ThemeParams
+Web Apps can adjust the appearance of the interface to match the Telegram user's app in real time. This object contains the user's current theme settings:
@@ -306,45 +310,46 @@
bg_color
String
-Optional. Background color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-bg-color).
+Optional. Background color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-bg-color).
text_color
String
-Optional. Main text color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-text-color).
+Optional. Main text color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-text-color).
hint_color
String
-Optional. Hint text color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-hint-color).
+Optional. Hint text color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-hint-color).
link_color
String
-Optional. Link color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-link-color).
+Optional. Link color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-link-color).
button_color
String
-Optional. Button color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-button-color).
+Optional. Button color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-button-color).
button_text_color
String
-Optional. Button text color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-button-text-color).
+Optional. Button text color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-button-text-color).
-secondary_bg_color ^==NEW==^
+secondary_bg_color NEW
String
-Optional. ==Bot API 6.1+== Secondary background color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-secondary-bg-color).
+Optional. Bot API 6.1+ Secondary background color in the #RRGGBB format.
Also available as the CSS variable var(--tg-theme-secondary-bg-color).
- 
+
-BackButton
-^==NEW==^ This object controls the back button, which can be displayed in the header of the Web App in the Telegram interface.
+
+BackButton
+NEW This object controls the back button, which can be displayed in the header of the Web App in the Telegram interface.
@@ -362,27 +367,27 @@
onClick(callback)
Function
-==Bot API 6.1+== A method that sets the button press event handler. An alias for Telegram.WebApp.onEvent('backButtonClicked', callback)
+Bot API 6.1+ A method that sets the button press event handler. An alias for Telegram.WebApp.onEvent('backButtonClicked', callback)
offClick(callback)
Function
-==Bot API 6.1+== A method that removes the button press event handler. An alias for Telegram.WebApp.offEvent('backButtonClicked', callback)
+Bot API 6.1+ A method that removes the button press event handler. An alias for Telegram.WebApp.offEvent('backButtonClicked', callback)
show()
Function
-==Bot API 6.1+== A method to make the button active and visible.
+Bot API 6.1+ A method to make the button active and visible.
hide()
Function
-==Bot API 6.1+== A method to hide the button.
+Bot API 6.1+ A method to hide the button.
All these methods return the BackButton object so they can be chained.
-MainButton
+MainButton
This object controls the main button, which is displayed at the bottom of the Web App in the Telegram interface.
@@ -431,17 +436,17 @@
onClick(callback)
Function
-A method that sets the button press event handler. An alias for Telegram.WebApp.onEvent('mainButtonClicked', callback)
+A method that sets the button press event handler. An alias for Telegram.WebApp.onEvent('mainButtonClicked', callback)
-offClick(callback) ^==NEW==^
+offClick(callback) NEW
Function
-A method that removes the button press event handler. An alias for Telegram.WebApp.offEvent('mainButtonClicked', callback)
+A method that removes the button press event handler. An alias for Telegram.WebApp.offEvent('mainButtonClicked', callback)
show()
Function
-A method to make the button visible.
Note that opening the Web App from the attachment menu hides the main button until the user interacts with the Web App interface.
+A method to make the button visible.
Note that opening the Web App from the attachment menu hides the main button until the user interacts with the Web App interface.
hide()
@@ -461,7 +466,7 @@
showProgress(leaveActive)
Function
-A method to show a loading indicator on the button.
It is recommended to display loading progress if the action tied to the button may take a long time. By default, the button is disabled while the action is in progress. If the parameter leaveActive=true is passed, the button remains enabled.
+A method to show a loading indicator on the button.
It is recommended to display loading progress if the action tied to the button may take a long time. By default, the button is disabled while the action is in progress. If the parameter leaveActive=true is passed, the button remains enabled.
hideProgress()
@@ -471,13 +476,13 @@
setParams(params)
Function
-A method to set the button parameters. The params parameter is an object containing one or several fields that need to be changed:
text - button text;
color - button color;
text_color - button text color;
is_active - enable the button;
is_visible - show the button.
+A method to set the button parameters. The params parameter is an object containing one or several fields that need to be changed:
text - button text;
color - button color;
text_color - button text color;
is_active - enable the button;
is_visible - show the button.
All these methods return the MainButton object so they can be chained.
-HapticFeedback
-^==NEW==^ This object controls haptic feedback.
+HapticFeedback
+NEW This object controls haptic feedback.
@@ -490,22 +495,22 @@
impactOccurred(style)
Function
-==Bot API 6.1+== A method tells that an impact occurred. The Telegram app may play the appropriate haptics based on style value passed. Style can be one of these values:
- light, indicates a collision between small or lightweight UI objects,
- medium, indicates a collision between medium-sized or medium-weight UI objects,
- heavy, indicates a collision between large or heavyweight UI objects,
- rigid, indicates a collision between hard or inflexible UI objects,
- soft, indicates a collision between soft or flexible UI objects.
+Bot API 6.1+ A method tells that an impact occurred. The Telegram app may play the appropriate haptics based on style value passed. Style can be one of these values:
- light, indicates a collision between small or lightweight UI objects,
- medium, indicates a collision between medium-sized or medium-weight UI objects,
- heavy, indicates a collision between large or heavyweight UI objects,
- rigid, indicates a collision between hard or inflexible UI objects,
- soft, indicates a collision between soft or flexible UI objects.
notificationOccurred(type)
Function
-==Bot API 6.1+== A method tells that a task or action has succeeded, failed, or produced a warning. The Telegram app may play the appropriate haptics based on type value passed. Type can be one of these values:
- error, indicates that a task or action has failed,
- success, indicates that a task or action has completed successfully,
- warning, indicates that a task or action produced a warning.
+Bot API 6.1+ A method tells that a task or action has succeeded, failed, or produced a warning. The Telegram app may play the appropriate haptics based on type value passed. Type can be one of these values:
- error, indicates that a task or action has failed,
- success, indicates that a task or action has completed successfully,
- warning, indicates that a task or action produced a warning.
selectionChanged()
Function
-==Bot API 6.1+== A method tells that the user has changed a selection. The Telegram app may play the appropriate haptics.
Do not use this feedback when the user makes or confirms a selection; use it only when the selection changes.
+Bot API 6.1+ A method tells that the user has changed a selection. The Telegram app may play the appropriate haptics.
Do not use this feedback when the user makes or confirms a selection; use it only when the selection changes.
All these methods return the HapticFeedback object so they can be chained.
-WebAppInitData
+WebAppInitData
This object contains data that is transferred to the Web App when it is opened. It is empty if the Web App was launched from a keyboard button.
@@ -532,17 +537,17 @@
Optional. An object containing data about the chat partner of the current user in the chat where the bot was launched via the attachment menu. Returned only for private chats and only for Web Apps launched via the attachment menu.
-chat ^==NEW==^
+chat NEW
WebAppChat
Optional. An object containing data about the chat where the bot was launched via the attachment menu. Returned for supergroups, channels and group chats – only for Web Apps launched via the attachment menu.
start_param
String
-Optional. The value of the startattach parameter, passed via link. Only returned for Web Apps when launched from the attachment menu via link.
The value of the start_param parameter will also be passed in the GET-parameter tgWebAppStartParam, so the Web App can load the correct interface right away.
+Optional. The value of the startattach parameter, passed via link. Only returned for Web Apps when launched from the attachment menu via link.
The value of the start_param parameter will also be passed in the GET-parameter tgWebAppStartParam, so the Web App can load the correct interface right away.
-can_send_after ^==NEW==^
+can_send_after NEW
Integer
Optional. Time in seconds, after which a message can be sent via the answerWebAppQuery method.
@@ -558,7 +563,7 @@
-WebAppUser
+WebAppUser
This object contains the data of the Web App user.
@@ -597,7 +602,7 @@
language_code
String
-Optional. IETF language tag of the user's language. Returns in user field only.
+Optional. IETF language tag of the user's language. Returns in user field only.
photo_url
@@ -606,8 +611,8 @@
-WebAppChat
-^==NEW==^ This object represents a chat.
+WebAppChat
+NEW This object represents a chat.
@@ -625,7 +630,7 @@
type
String
-Type of chat, can be either "group", "supergroup" or "channel"
+Type of chat, can be either “group”, “supergroup” or “channel”
title
@@ -644,19 +649,19 @@
-Validating data received via the Web App
-To validate data received via the Web App, one should send the data from the Telegram.WebApp.initData field to the bot's backend. The data is a query string, which is composed of a series of field-value pairs.
-You can verify the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the secret key, which is the HMAC-SHA-256 signature of the bot's token with the constant string WebAppData used as a key.
-Data-check-string is a chain of all received fields, sorted alphabetically, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nquery_id=<query_id>\nuser=<user>'.
+Validating data received via the Web App
+To validate data received via the Web App, one should send the data from the Telegram.WebApp.initData field to the bot's backend. The data is a query string, which is composed of a series of field-value pairs.
+You can verify the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the secret key, which is the HMAC-SHA-256 signature of the bot's token with the constant string WebAppData used as a key.
+Data-check-string is a chain of all received fields, sorted alphabetically, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nquery_id=<query_id>\nuser=<user>'.
The full check might look like:
data_check_string = ...
-secret_key = HMAC_SHA256(;, "WebAppData")
+secret_key = HMAC_SHA256(<bot_token>, "WebAppData")
if (hex(HMAC_SHA256(data_check_string, secret_key)) == hash) {
- // data is from Telegram
+ // data is from Telegram
}
To prevent the use of outdated data, you can additionally check the auth_date field, which contains a Unix timestamp of when it was received by the Web App.
Once validated, the data may be used on your server. Complex data types are represented as JSON-serialized objects.
-Events Available for Web Apps
+Events Available for Web Apps
The Web App can receive events from the Telegram app, onto which a handler can be attached using the Telegram.WebApp.onEvent(eventType, eventHandler) method. Inside eventHandler the this object refers to Telegram.WebApp, the set of parameters sent to the handler depends on the event type. Below is a list of possible events:
@@ -668,52 +673,46 @@ if (hex(HMAC_SHA256(data_check_string, secret_key)) == hash) {
themeChangedOccurs whenever theme settings are changed in the user's Telegram app (including switching to night mode).
eventHandler receives no parameters, new theme settings and color scheme can be received via this.themeParams and this.colorScheme respectively.
+Occurs whenever theme settings are changed in the user's Telegram app (including switching to night mode).
eventHandler receives no parameters, new theme settings and color scheme can be received via this.themeParams and this.colorScheme respectively.
viewportChangedOccurs when the visible section of the Web App is changed.
eventHandler receives an object with the single field isStateStable. If isStateStable is true, the resizing of the Web App is finished. If it is false, the resizing is ongoing (the user is expanding or collapsing the Web App or an animated object is playing). The current value of the visible section’s height is available in this.viewportHeight.
+Occurs when the visible section of the Web App is changed.
eventHandler receives an object with the single field isStateStable. If isStateStable is true, the resizing of the Web App is finished. If it is false, the resizing is ongoing (the user is expanding or collapsing the Web App or an animated object is playing). The current value of the visible section’s height is available in this.viewportHeight.
mainButtonClickedOccurs when the main button is pressed.
eventHandler receives no parameters.
+Occurs when the main button is pressed.
eventHandler receives no parameters.
-backButtonClicked ^==NEW==^==Bot API 6.1+== Occurrs when the back button is pressed.
eventHandler receives no parameters.
+backButtonClicked NEWBot API 6.1+ Occurrs when the back button is pressed.
eventHandler receives no parameters.
-settingsButtonClicked ^==NEW==^==Bot API 6.1+== Occurrs when the Settings item in context menu is pressed.
eventHandler receives no parameters.
+settingsButtonClicked NEWBot API 6.1+ Occurrs when the Settings item in context menu is pressed.
eventHandler receives no parameters.
-invoiceClosed ^==NEW==^==Bot API 6.1+== Occurrs when the opened invoice is closed.
eventHandler receives an object with the two fields: url – invoice link provided and status – one of the invoice statuses:
- paid – invoice was paid successfully,
- cancelled – user closed this invoice without paying,
- failed – user tried to pay, but the payment was failed,
- pending – the payment is still processing. The bot will receive a service message about a successful payment when the payment is successfully paid.
+invoiceClosed NEWBot API 6.1+ Occurrs when the opened invoice is closed.
eventHandler receives an object with the two fields: url – invoice link provided and status – one of the invoice statuses:
- paid – invoice was paid successfully,
- cancelled – user closed this invoice without paying,
- failed – user tried to pay, but the payment was failed,
- pending – the payment is still processing. The bot will receive a service message about a successful payment when the payment is successfully paid.
-Adding Bots to the Attachment Menu
-Attachment menu integration is currently only available for major advertisers on the Telegram Ad Platform. However, all bots can use it in the test server environment. Talk to Botfather on the test server to set up the integration.
+Adding Bots to the Attachment Menu
+Attachment menu integration is currently only available for major advertisers on the Telegram Ad Platform. However, all bots can use it in the test server environment. Talk to Botfather on the test server to set up the integration.
A special link is used to add bots to the attachment menu:
-https://t.me/botusername?startattach
-or
-https://t.me/botusername?startattach=command
+https://t.me/botusername?startattach
or
https://t.me/botusername?startattach=command
-For example, open this attachment menu link for @DurgerKingBot, then use the menu in any private chat.
+For example, open this attachment menu link for @DurgerKingBot, then use the menu in any private chat.
Opening the link prompts the user to add the bot to their attachment menu. If the bot has already been added, the attachment menu will open in the current chat and redirect to the bot there (if the link is opened from a 1-on-1 chat). If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
The following link formats are also supported:
-https://t.me/username?attach=botusername
-https://t.me/username?attach=botusername&startattach=command
-https://t.me/+1234567890?attach=botusername
-https://t.me/+1234567890?attach=botusername&startattach=command
-These links open the Web App in the attachment menu in the chat with a specific user. If the bot wasn't already added to the attachment menu, the user will be prompted to do so. If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
-==Bot API 6.1+== supports a new link format:
-https://t.me/botusername?startattach&choose=users+bots
-https://t.me/botusername?startattach=command&choose=groups+channels
-Opening such a link prompts the user to choose a specific chat and opens the attachment menu in that chat. If the bot wasn't already added to the attachment menu, the user will be prompted to do so. You can specify which types of chats the user will be able to choose from. It can be one or more of the following types: users, bots, groups, channels separated by a + sign. If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
-Testing Web Apps
-Using bots in the test environment
+https://t.me/username?attach=botusername
https://t.me/username?attach=botusername&startattach=command
https://t.me/+1234567890?attach=botusername
https://t.me/+1234567890?attach=botusername&startattach=command
+These links open the Web App in the attachment menu in the chat with a specific user. If the bot wasn't already added to the attachment menu, the user will be prompted to do so. If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
+Bot API 6.1+ supports a new link format:
+https://t.me/botusername?startattach&choose=users+bots
https://t.me/botusername?startattach=command&choose=groups+channels
+Opening such a link prompts the user to choose a specific chat and opens the attachment menu in that chat. If the bot wasn't already added to the attachment menu, the user will be prompted to do so. You can specify which types of chats the user will be able to choose from. It can be one or more of the following types: users, bots, groups, channels separated by a + sign. If a non-empty startattach parameter was included in the link, it will be passed to the Web App in the start_param field and in the GET parameter tgWebAppStartParam.
+Testing Web Apps
+Using bots in the test environment
To log in to the test environment, use either of the following:
- iOS: tap 10 times on the Settings icon > Accounts > Login to another account > Test.
@@ -726,7 +725,7 @@ or
Note: When working with the test environment, you may use HTTP links without TLS to test your Web App.
-Debug Mode for Web Apps
+Debug Mode for Web Apps
Use these tools to find app-specific issues in your Web App:
Android
@@ -744,9 +743,10 @@ or
Telegram macOS
- Download and launch the Beta Version of Telegram macOS.
-- Quickly click 5 times on the Settings icon to open the debug menu and enable "Debug Web Apps".
+- Quickly click 5 times on the Settings icon to open the debug menu and enable “Debug Web Apps”.
- Right click in the web app and choose Inspect Element.
-
+
+