Struct teloxide_core::payloads::SendVideo
source · pub struct SendVideo {Show 17 fields
pub chat_id: Recipient,
pub video: InputFile,
pub message_thread_id: Option<i32>,
pub duration: Option<u32>,
pub width: Option<u32>,
pub height: Option<u32>,
pub thumb: Option<InputFile>,
pub caption: Option<String>,
pub parse_mode: Option<ParseMode>,
pub caption_entities: Option<Vec<MessageEntity>>,
pub has_spoiler: Option<bool>,
pub supports_streaming: Option<bool>,
pub disable_notification: Option<bool>,
pub protect_content: Option<bool>,
pub reply_to_message_id: Option<MessageId>,
pub allow_sending_without_reply: Option<bool>,
pub reply_markup: Option<ReplyMarkup>,
}
Expand description
Fields§
§chat_id: Recipient
Unique identifier for the target chat or username of the target channel (in the format @channelusername
)
video: InputFile
Video to send. Pass a file_id as String to send a video that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »
message_thread_id: Option<i32>
Unique identifier for the target message thread (topic) of the forum; for forum supergroups only
duration: Option<u32>
Duration of the video in seconds
width: Option<u32>
Video width
height: Option<u32>
Video height
thumb: Option<InputFile>
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 »
Video caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing
parse_mode: Option<ParseMode>
Mode for parsing entities in the video caption. See formatting options for more details.
List of special entities that appear in the caption, which can be specified instead of parse_mode
has_spoiler: Option<bool>
Pass True if the video needs to be covered with a spoiler animation
supports_streaming: Option<bool>
Pass True, if the uploaded video is suitable for streaming
disable_notification: Option<bool>
Sends the message silently. Users will receive a notification with no sound.
protect_content: Option<bool>
Protects the contents of sent messages from forwarding and saving
reply_to_message_id: Option<MessageId>
If the message is a reply, ID of the original message
allow_sending_without_reply: Option<bool>
Pass True, if the message should be sent even if the specified replied-to message is not found
reply_markup: Option<ReplyMarkup>
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.
Implementations§
Trait Implementations§
source§impl MultipartPayload for SendVideo
impl MultipartPayload for SendVideo
fn copy_files(&self, into: &mut dyn FnMut(InputFile))
fn move_files(&mut self, into: &mut dyn FnMut(InputFile))
source§impl Payload for SendVideo
impl Payload for SendVideo
source§fn timeout_hint(&self) -> Option<Duration>
fn timeout_hint(&self) -> Option<Duration>
GetUpdates
with
big timeout
), the minimum timeout that should be used.