InlineQueryResultCachedSticker#

class aiogram.types.inline_query_result_cached_sticker.InlineQueryResultCachedSticker(*, type: ~typing.Literal[<InlineQueryResultType.STICKER: 'sticker'>] = InlineQueryResultType.STICKER, id: str, sticker_file_id: str, reply_markup: ~aiogram.types.inline_keyboard_markup.InlineKeyboardMarkup | None = None, input_message_content: ~aiogram.types.input_text_message_content.InputTextMessageContent | ~aiogram.types.input_location_message_content.InputLocationMessageContent | ~aiogram.types.input_venue_message_content.InputVenueMessageContent | ~aiogram.types.input_contact_message_content.InputContactMessageContent | ~aiogram.types.input_invoice_message_content.InputInvoiceMessageContent | None = None, **extra_data: ~typing.Any)[source]#

Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker. Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.

Source: https://core.telegram.org/bots/api#inlinequeryresultcachedsticker

type: Literal[InlineQueryResultType.STICKER]#

Type of the result, must be sticker

id: str#

Unique identifier for this result, 1-64 bytes

sticker_file_id: str#

A valid file identifier of the sticker

reply_markup: InlineKeyboardMarkup | None#

Optional. Inline keyboard attached to the message

input_message_content: InputTextMessageContent | InputLocationMessageContent | InputVenueMessageContent | InputContactMessageContent | InputInvoiceMessageContent | None#

Optional. Content of the message to be sent instead of the sticker