Button to request a user to authorize via URL using Seamless Telegram Login.
Use this constructor to send a keyboardButtonUrlAuth button in an inline keyboard.
inputKeyboardButtonUrlAuth#68013e72 flags:# request_write_access:flags.0?true style:flags.10?KeyboardButtonStyle text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| request_write_access | flags.0?true | Set this flag to request the permission for your bot to send messages to the user. |
| style | flags.10?KeyboardButtonStyle | Button style, see here » for more info on button styles. |
| text | string | Button text |
| fwd_text | flags.1?string | New text of the button in forwarded messages. |
| url | string | An HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data. NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization. |
| bot | InputUser | Username of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details. |
Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.
Use this to accept a Seamless Telegram Login authorization request, for more info click here »
Button to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.
Available only in inline keyboards.
This page describes individual bot elements in greater detail. For a general overview of bots, read the introduction to bots first.