InlineQueryResultContact#
- class aiogram.types.inline_query_result_contact.InlineQueryResultContact(*, type: Literal[InlineQueryResultType.CONTACT] = InlineQueryResultType.CONTACT, id: str, phone_number: str, first_name: str, last_name: str | None = None, vcard: str | None = None, reply_markup: InlineKeyboardMarkup | None = None, input_message_content: InputTextMessageContent | InputLocationMessageContent | InputVenueMessageContent | InputContactMessageContent | InputInvoiceMessageContent | None = None, thumbnail_url: str | None = None, thumbnail_width: int | None = None, thumbnail_height: int | None = None, **extra_data: Any)[source]#
Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.
Source: https://core.telegram.org/bots/api#inlinequeryresultcontact
- type: Literal[InlineQueryResultType.CONTACT]#
Type of the result, must be contact
- id: str#
Unique identifier for this result, 1-64 Bytes
- phone_number: str#
Contact’s phone number
- first_name: str#
Contact’s first name
- last_name: str | None#
Optional. Contact’s last name
- model_computed_fields: ClassVar[dict[str, ComputedFieldInfo]] = {}#
A dictionary of computed field names and their corresponding ComputedFieldInfo objects.
- model_post_init(_ModelMetaclass__context: Any) None #
We need to both initialize private attributes and call the user-defined model_post_init method.
- 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 contact
- thumbnail_url: str | None#
Optional. Url of the thumbnail for the result
- thumbnail_width: int | None#
Optional. Thumbnail width
- thumbnail_height: int | None#
Optional. Thumbnail height