1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
// This file is auto generated by `cg` <https://github.com/teloxide/cg> (24572cd + local changes). // **DO NOT EDIT THIS FILE**, // edit `cg` instead. use serde::Serialize; use crate::types::{ChatId, Message, ReplyMarkup}; impl_payload! { /// Use this method to send phone contacts. On success, the sent [`Message`] is returned. /// /// [`Message`]: crate::types::Message #[derive(Debug, PartialEq, Eq, Hash, Clone, Serialize)] pub SendContact (SendContactSetters) => Message { required { /// Unique identifier for the target chat or username of the target channel (in the format `@channelusername`) pub chat_id: ChatId [into], /// Contact's phone number pub phone_number: String [into], /// Contact's first name pub first_name: String [into], } optional { /// Contact's last name pub last_name: String [into], /// Additional data about the contact in the form of a [vCard], 0-2048 bytes /// /// [vCard]: https://en.wikipedia.org/wiki/VCard pub vcard: String [into], /// Sends the message [silently]. Users will receive a notification with no sound. /// /// [silently]: https://telegram.org/blog/channels-2-0#silent-messages pub disable_notification: bool, /// If the message is a reply, ID of the original message pub reply_to_message_id: i32, /// Pass _True_, if the message should be sent even if the specified replied-to message is not found pub allow_sending_without_reply: bool, /// Additional interface options. A JSON-serialized object for an [inline keyboard], [custom reply keyboard], instructions to remove reply keyboard or to force a reply from the user. /// /// [inline keyboard]: https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating /// [custom reply keyboard]: https://core.telegram.org/bots#keyboards pub reply_markup: ReplyMarkup [into], } } }