Data that was contained in the callback button, if any
Note that this field is defined by the client, and a bad client can send arbitrary data in this field.
Data that was contained in the callback button, if any, parsed as a UTF8 string
Note that this field is defined by the client, and a bad client can send arbitrary data in this field.
In case this message was from InputInlineResultGame, or the button was BotKeyboard.game, short name of the game that should be returned.
ID of this callback query
Identifier of the previously sent inline message,
that contained the button which was clicked.
This ID can be used in TelegramClient.editInlineMessage
Identifier of the previously sent inline message, that contained the button which was clicked, as a TDLib and Bot API compatible string. Can be used instead of inlineMessageId in case you want to store it in some storage.
Unique ID, that represents the chat to which the inline message was sent. Does not contain actual chat ID.
User who has pressed the button
Answer to this callback query
Optionalalert?: booleanWhether to show an alert in the middle of the screen instead of a notification at the top of the screen.
OptionalcacheTime?: numberMaximum amount of time in seconds for which this result can be cached by the client (not server!).
Optionaltext?: stringText of the notification (0-200 chars).
If not set, nothing will be displayed
Optionalurl?: stringURL that the client should open.
If this was a button containing a game,
you can provide arbitrary link to your game.
Otherwise, you can only use links in the format
t.me/your_bot?start=... that open your bot
with a deep-link parameter.
Edit the message that contained the callback button that was clicked.
Context of an inline-originated callback query update.
This is a subclass of InlineCallbackQuery, so all its fields are also available.