ronami_core/payloads/
send_video_note.rs

1//! Generated by `codegen_payloads`, do not edit by hand.
2
3use serde::Serialize;
4
5use crate::types::BusinessConnectionId;
6use crate::types::EffectId;
7use crate::types::EphemeralMessageParameters;
8use crate::types::InputFile;
9use crate::types::Message;
10use crate::types::Recipient;
11use crate::types::ReplyMarkup;
12use crate::types::ReplyParameters;
13use crate::types::SuggestedPostParameters;
14use crate::types::ThreadId;
15use crate::types::TopicId;
16
17impl_payload! {
18    @[multipart = video_note, thumbnail]
19    /// As of [v.4.0], Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent [`Message`] is returned.
20    ///
21    /// [v.4.0]: https://core.telegram.org/bots/api#document
22    /// [`Message`]: crate::types::Message
23    #[derive(Debug, Clone, Serialize)]
24    pub SendVideoNote (SendVideoNoteSetters) => Message {
25        required {
26            /// Unique identifier for the target chat or username of the target channel (in the format `@channelusername`)
27            pub chat_id: Recipient [into],
28            /// Video note to send. Pass a file_id as FileId to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. [More info on Sending Files »]. Sending video notes by a URL is currently unsupported
29            ///
30            /// [More info on Sending Files »]: crate::types::InputFile
31            pub video_note: InputFile,
32        }
33        optional {
34            /// Unique identifier of the business connection on behalf of which the message will be sent
35            pub business_connection_id: BusinessConnectionId,
36            /// Unique identifier for the target message thread (topic) of the forum; for forum supergroups only
37            pub message_thread_id: ThreadId,
38            /// Identifier of the direct messages topic to which the message will be sent; required if the message is sent to a direct messages chat
39            pub direct_messages_topic_id: TopicId,
40            /// Duration of the video in seconds
41            pub duration: u32,
42            /// Video width and height, i.e. diameter of the video message
43            pub length: u32,
44            /// Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. [More info on Sending Files »]
45            ///
46            /// [More info on Sending Files »]: crate::types::InputFile
47            pub thumbnail: InputFile,
48            /// Sends the message [silently]. Users will receive a notification with no sound.
49            ///
50            /// [silently]: https://telegram.org/blog/channels-2-0#silent-messages
51            pub disable_notification: bool,
52            /// Protects the contents of sent messages from forwarding and saving
53            pub protect_content: bool,
54            /// 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
55            pub allow_paid_broadcast: bool,
56            /// Unique identifier of the message effect to be added to the message; for private chats only
57            pub message_effect_id: EffectId,
58            /// 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.
59            pub suggested_post_parameters: SuggestedPostParameters,
60            /// A JSON-serialized object containing the parameters of the ephemeral message to send
61            pub ephemeral_message_parameters: EphemeralMessageParameters,
62            /// Description of the message to reply to
63            pub reply_parameters: ReplyParameters,
64            /// 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.
65            ///
66            /// [inline keyboard]: https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating
67            /// [custom reply keyboard]: https://core.telegram.org/bots#keyboards
68            pub reply_markup: ReplyMarkup [into],
69        }
70    }
71}
ronami_core/payloads/send_video_note.rs

ronami_core/payloads/
send_video_note.rs
