ronami_core/payloads/send_photo.rs
1//! Generated by `codegen_payloads`, do not edit by hand.
2
3use serde::Serialize;
4
5use crate::types::{
6 BusinessConnectionId, CallbackQueryId, EffectId, InputFile, Message, MessageEntity, ParseMode,
7 Recipient, ReplyMarkup, ReplyParameters, SuggestedPostParameters, ThreadId, TopicId, UserId,
8};
9
10impl_payload! {
11 @[multipart = photo]
12 /// Use this method to send photos. On success, the sent [`Message`] is returned.
13 ///
14 /// [`Message`]: crate::types::Message
15 #[derive(Debug, Clone, Serialize)]
16 pub SendPhoto (SendPhotoSetters) => Message {
17 required {
18 /// Unique identifier for the target chat or username of the target channel (in the format `@channelusername`)
19 pub chat_id: Recipient [into],
20 /// Photo to send. Pass a file_id as FileId to send a photo that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a photo from the Internet, or upload a new photo using multipart/form-data. [More info on Sending Files »]
21 ///
22 /// [More info on Sending Files »]: crate::types::InputFile
23 pub photo: InputFile,
24 }
25 optional {
26 /// Unique identifier of the business connection on behalf of which the message will be sent
27 pub business_connection_id: BusinessConnectionId,
28 /// Unique identifier for the target message thread (topic) of the forum; for forum supergroups only
29 pub message_thread_id: ThreadId,
30 /// Identifier of the direct messages topic to which the message will be sent; required if the message is sent to a direct messages chat
31 pub direct_messages_topic_id: TopicId,
32 /// Photo caption (may also be used when resending photos by _file\_id_), 0-1024 characters after entities parsing
33 pub caption: String [into],
34 /// Mode for parsing entities in the photo caption. See [formatting options] for more details.
35 ///
36 /// [formatting options]: https://core.telegram.org/bots/api#formatting-options
37 pub parse_mode: ParseMode,
38 /// List of special entities that appear in the photo caption, which can be specified instead of _parse\_mode_
39 pub caption_entities: Vec<MessageEntity> [collect],
40 /// Pass True, if the caption must be shown above the message media
41 pub show_caption_above_media: bool,
42 /// Pass True if the photo needs to be covered with a spoiler animation
43 pub has_spoiler: bool,
44 /// Sends the message [silently]. Users will receive a notification with no sound.
45 ///
46 /// [silently]: https://telegram.org/blog/channels-2-0#silent-messages
47 pub disable_notification: bool,
48 /// Protects the contents of sent messages from forwarding and saving
49 pub protect_content: bool,
50 /// Pass `true` to allow up to 1000 messages per second, ignoring broadcasting limits for a fee of 0.1 Telegram Stars per message. The relevant Stars will be withdrawn from the bot's balance
51 pub allow_paid_broadcast: bool,
52 /// Unique identifier of the message effect to be added to the message; for private chats only
53 pub message_effect_id: EffectId,
54 /// An object containing the parameters of the suggested post to send; for direct messages chats only. If the message is sent as a reply to another suggested post, then that suggested post is automatically declined.
55 pub suggested_post_parameters: SuggestedPostParameters,
56 /// Identifier of the user who received the message
57 pub receiver_user_id: UserId,
58 /// Unique identifier of the query to be answered
59 pub callback_query_id: CallbackQueryId,
60 /// Description of the message to reply to
61 pub reply_parameters: ReplyParameters,
62 /// Additional interface options. A JSON-serialized object for an [inline keyboard], [custom reply keyboard], instructions to remove a reply keyboard or to force a reply from the user. Not supported for messages sent on behalf of a business account.
63 ///
64 /// [inline keyboard]: https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating
65 /// [custom reply keyboard]: https://core.telegram.org/bots#keyboards
66 pub reply_markup: ReplyMarkup [into],
67 }
68 }
69}