send_document¶
-
template<class Agent>
api_result<message_t, Agent&&> send_document(Agent &&agent, send_document_args_t args)¶
-
template<class Agent, class F>
void send_document(Agent &&agent, send_document_args_t args, F &&callback)¶ agent
is any object satisfying agent concept.callback
is any callable object acceptingexpected<message_t>
.Use this method to send general files. On success, the sent Message is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.
-
struct send_document_args_t¶
Arguments that should be passed to
send_document()
.Unique identifier for the target chat or username of the target channel (in the format @channelusername)
-
optional_t<integer_t> message_thread_id¶
Unique identifier for the target message thread (topic) of the forum; for forum supergroups only
-
variant_t<input_file_t, string_t> document¶
File to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More information on Sending Files »
-
optional_t<variant_t<input_file_t, string_t>> thumbnail¶
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 information on Sending Files »
Document caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
-
optional_t<string_t> parse_mode¶
Mode for parsing entities in the document caption. See formatting options for more details.
A JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
-
optional_t<boolean_t> disable_content_type_detection¶
Disables automatic server-side content type detection for files uploaded using multipart/form-data
-
optional_t<boolean_t> disable_notification¶
Sends the message silently. Users will receive a notification with no sound.
-
optional_t<boolean_t> protect_content¶
Protects the contents of the sent message from forwarding and saving
-
optional_t<reply_parameters_t> reply_parameters¶
Description of the message to reply to
-
optional_t<variant_t<inline_keyboard_markup_t, reply_keyboard_markup_t, reply_keyboard_remove_t, force_reply_t>> reply_markup¶
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.
-
optional_t<integer_t> message_thread_id¶