pub struct CallbackQuery {
pub id: String,
pub from: User,
pub message: Option<Message>,
pub inline_message_id: Option<String>,
pub chat_instance: String,
pub data: Option<String>,
pub game_short_name: Option<String>,
}Expand description
This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.
NOTE: After the user presses a callback button, Telegram clients will display a progress bar until you call answerCallbackQuery. It is, therefore, necessary to react by calling answerCallbackQuery even if no notification to the user is needed (e.g., without specifying any of the optional parameters).
Fields§
§id: StringUnique identifier for this query
from: UserSender
message: Option<Message>Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
inline_message_id: Option<String>Identifier of the message sent via the bot in inline mode, that originated the query.
chat_instance: StringGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
data: Option<String>Data associated with the callback button. Be aware that the message originated the query can contain no callback buttons with this data.
game_short_name: Option<String>Short name of a Game to be returned, serves as the unique identifier for the game