+23
-5
@@ -9,9 +9,21 @@ type InlineQueryResult map[string]any
|
||||
// Since: Bot API 6.3
|
||||
// See https://core.telegram.org/bots/api#inlinequeryresultsbutton
|
||||
type InlineQueryResultsButton struct {
|
||||
Text string `json:"text"`
|
||||
WebApp *WebAppInfo `json:"web_app,omitempty"`
|
||||
StartParameter string `json:"start_parameter,omitempty"`
|
||||
// Text Label text on the button
|
||||
Text string `json:"text"`
|
||||
// WebApp Optional. Description of the Web App that will be launched when the user presses the button. The
|
||||
// Web App will be able to switch back to the inline mode using the method switchInlineQuery inside the Web
|
||||
// App.
|
||||
WebApp *WebAppInfo `json:"web_app,omitempty"`
|
||||
// StartParameter Optional. Deep-linking parameter for the /start message sent to the bot when a user
|
||||
// presses the button. 1-64 characters, only A-Z, a-z, 0-9, _ and - are allowed. Example: An inline bot that
|
||||
// sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results
|
||||
// accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even
|
||||
// before showing any. The user presses the button, switches to a private chat with the bot and, in doing
|
||||
// so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer
|
||||
// a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's
|
||||
// inline capabilities.
|
||||
StartParameter string `json:"start_parameter,omitempty"`
|
||||
}
|
||||
|
||||
// InputRichMessageContent represents the content of a rich message to be
|
||||
@@ -28,6 +40,8 @@ type InputRichMessageContent struct {
|
||||
// Since: Bot API 8.0
|
||||
// See https://core.telegram.org/bots/api#sentwebappmessage
|
||||
type SentWebAppMessage struct {
|
||||
// InlineMessageID Optional. Identifier of the sent inline message. Available only if there is an inline
|
||||
// keyboard attached to the message.
|
||||
InlineMessageID string `json:"inline_message_id,omitempty"`
|
||||
}
|
||||
|
||||
@@ -35,13 +49,17 @@ type SentWebAppMessage struct {
|
||||
// Since: Bot API 8.0
|
||||
// See https://core.telegram.org/bots/api#preparedinlinemessage
|
||||
type PreparedInlineMessage struct {
|
||||
ID string `json:"id"`
|
||||
ExpirationDate int `json:"expiration_date"`
|
||||
// ID Unique identifier of the prepared message
|
||||
ID string `json:"id"`
|
||||
// ExpirationDate Expiration date of the prepared message, in Unix time. Expired prepared messages can no
|
||||
// longer be used.
|
||||
ExpirationDate int `json:"expiration_date"`
|
||||
}
|
||||
|
||||
// PreparedKeyboardButton describes a prepared keyboard button.
|
||||
// Since: Bot API 8.0
|
||||
// See https://core.telegram.org/bots/api#preparedkeyboardbutton
|
||||
type PreparedKeyboardButton struct {
|
||||
// ID Unique identifier of the keyboard button
|
||||
ID string `json:"id"`
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user