mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2025-01-16 22:53:12 +01:00
Update content of files
This commit is contained in:
GitHub Action
parent
c1f49de62f
commit
866fc25857
1 changed files with 59 additions and 59 deletions
|
|
@ -74,7 +74,7 @@ To learn how to create…">
|
|||
</ul>
|
||||
<hr>
|
||||
<blockquote>
|
||||
<p><strong><img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /> WARNING! <img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /></strong><br>After one of the upcoming Bot API updates, user identifiers will become bigger than <code>2^31 - 1</code> and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
|
||||
<p><strong>вљ пёЏ WARNING! вљ пёЏ</strong><br>After one of the upcoming Bot API updates, user identifiers will become bigger than <code>2^31 - 1</code> and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
|
||||
</blockquote>
|
||||
<hr>
|
||||
<h4><a class="anchor" name="april-26-2021" href="#april-26-2021"><i class="anchor-icon"></i></a>April 26, 2021</h4>
|
||||
|
|
@ -91,15 +91,15 @@ To learn how to create…">
|
|||
</ul>
|
||||
<hr>
|
||||
<blockquote>
|
||||
<p><strong><img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /> WARNING! <img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /></strong><br>After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field <code>file_unique_id</code> in objects of the type <a href="#photosize">PhotoSize</a> and of the fields <code>small_file_unique_id</code> and <code>big_file_unique_id</code> in objects of the type <a href="#chatphoto">ChatPhoto</a>.</p>
|
||||
<p><strong>вљ пёЏ WARNING! вљ пёЏ</strong><br>After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field <code>file_unique_id</code> in objects of the type <a href="#photosize">PhotoSize</a> and of the fields <code>small_file_unique_id</code> and <code>big_file_unique_id</code> in objects of the type <a href="#chatphoto">ChatPhoto</a>.</p>
|
||||
</blockquote>
|
||||
<hr>
|
||||
<blockquote>
|
||||
<p><strong><img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /> WARNING! <img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /></strong><br>Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.</p>
|
||||
<p><strong>вљ пёЏ WARNING! вљ пёЏ</strong><br>Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.</p>
|
||||
</blockquote>
|
||||
<hr>
|
||||
<blockquote>
|
||||
<p><strong><img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /> WARNING! <img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /></strong><br>After one of the upcoming Bot API updates, user identifiers will become bigger than <code>2^31 - 1</code> and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
|
||||
<p><strong>вљ пёЏ WARNING! вљ пёЏ</strong><br>After one of the upcoming Bot API updates, user identifiers will become bigger than <code>2^31 - 1</code> and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
|
||||
</blockquote>
|
||||
<hr>
|
||||
<h4><a class="anchor" name="march-9-2021" href="#march-9-2021"><i class="anchor-icon"></i></a>March 9, 2021</h4>
|
||||
|
|
@ -131,7 +131,7 @@ To learn how to create…">
|
|||
</ul>
|
||||
<hr>
|
||||
<blockquote>
|
||||
<p><strong><img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /> WARNING! <img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /></strong><br>After one of the upcoming Bot API updates, some user identifiers will become bigger than <code>2^31 - 1</code> and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
|
||||
<p><strong>вљ пёЏ WARNING! вљ пёЏ</strong><br>After one of the upcoming Bot API updates, some user identifiers will become bigger than <code>2^31 - 1</code> and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
|
||||
</blockquote>
|
||||
<hr>
|
||||
<h4><a class="anchor" name="november-4-2020" href="#november-4-2020"><i class="anchor-icon"></i></a>November 4, 2020</h4>
|
||||
|
|
@ -201,7 +201,7 @@ To learn how to create…">
|
|||
<ul>
|
||||
<li>Supported the new <strong>football</strong> and <strong>slot machine</strong> animations for the random <a href="#dice">dice</a>. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the <em>emoji</em> parameter in the method <a href="#senddice">sendDice</a>.</li>
|
||||
</ul>
|
||||
<p><strong><a href="/bots/api-changelog">See earlier changes »</a></strong></p>
|
||||
<p><strong><a href="/bots/api-changelog">See earlier changes В»</a></strong></p>
|
||||
<h3><a class="anchor" name="authorizing-your-bot" href="#authorizing-your-bot"><i class="anchor-icon"></i></a>Authorizing your bot</h3>
|
||||
<p>Each bot is given a unique authentication token <a href="/bots#6-botfather">when it is created</a>. The token looks something like <code>123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11</code>, but we'll use simply <strong><token></strong> in this document instead. You can learn about obtaining tokens and generating new ones in <a href="https://core.telegram.org/bots#6-botfather">this document</a>.</p>
|
||||
<h3><a class="anchor" name="making-requests" href="#making-requests"><i class="anchor-icon"></i></a>Making requests</h3>
|
||||
|
|
@ -239,7 +239,7 @@ To learn how to create…">
|
|||
<h4><a class="anchor" name="do-i-need-a-local-bot-api-server" href="#do-i-need-a-local-bot-api-server"><i class="anchor-icon"></i></a>Do I need a Local Bot API Server</h4>
|
||||
<p>The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of <a href="#using-a-local-bot-api-server">these features</a>, you're welcome to switch to your own at any time.</p>
|
||||
<h3><a class="anchor" name="getting-updates" href="#getting-updates"><i class="anchor-icon"></i></a>Getting updates</h3>
|
||||
<p>There are two mutually exclusive ways of receiving updates for your bot — the <a href="#getupdates">getUpdates</a> method on one hand and <a href="#setwebhook">Webhooks</a> on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.</p>
|
||||
<p>There are two mutually exclusive ways of receiving updates for your bot — the <a href="#getupdates">getUpdates</a> method on one hand and <a href="#setwebhook">Webhooks</a> on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.</p>
|
||||
<p>Regardless of which option you choose, you will receive JSON-serialized <a href="#update">Update</a> objects as a result.</p>
|
||||
<h4><a class="anchor" name="update" href="#update"><i class="anchor-icon"></i></a>Update</h4>
|
||||
<p>This <a href="#available-types">object</a> represents an incoming update.<br>At most <strong>one</strong> of the optional parameters can be present in any given update.</p>
|
||||
|
|
@ -260,7 +260,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>message</td>
|
||||
<td><a href="#message">Message</a></td>
|
||||
<td><em>Optional</em>. New incoming message of any kind — text, photo, sticker, etc.</td>
|
||||
<td><em>Optional</em>. New incoming message of any kind — text, photo, sticker, etc.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>edited_message</td>
|
||||
|
|
@ -270,7 +270,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>channel_post</td>
|
||||
<td><a href="#message">Message</a></td>
|
||||
<td><em>Optional</em>. New incoming channel post of any kind — text, photo, sticker, etc.</td>
|
||||
<td><em>Optional</em>. New incoming channel post of any kind — text, photo, sticker, etc.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>edited_channel_post</td>
|
||||
|
|
@ -826,7 +826,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>game</td>
|
||||
<td><a href="#game">Game</a></td>
|
||||
<td><em>Optional</em>. Message is a game, information about the game. <a href="#games">More about games »</a></td>
|
||||
<td><em>Optional</em>. Message is a game, information about the game. <a href="#games">More about games В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>poll</td>
|
||||
|
|
@ -906,17 +906,17 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>invoice</td>
|
||||
<td><a href="#invoice">Invoice</a></td>
|
||||
<td><em>Optional</em>. Message is an invoice for a <a href="#payments">payment</a>, information about the invoice. <a href="#payments">More about payments »</a></td>
|
||||
<td><em>Optional</em>. Message is an invoice for a <a href="#payments">payment</a>, information about the invoice. <a href="#payments">More about payments В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>successful_payment</td>
|
||||
<td><a href="#successfulpayment">SuccessfulPayment</a></td>
|
||||
<td><em>Optional</em>. Message is a service message about a successful payment, information about the payment. <a href="#payments">More about payments »</a></td>
|
||||
<td><em>Optional</em>. Message is a service message about a successful payment, information about the payment. <a href="#payments">More about payments В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>connected_website</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. The domain name of the website on which the user has logged in. <a href="/widgets/login">More about Telegram Login »</a></td>
|
||||
<td><em>Optional</em>. The domain name of the website on which the user has logged in. <a href="/widgets/login">More about Telegram Login В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>passport_data</td>
|
||||
|
|
@ -1409,7 +1409,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>value</td>
|
||||
<td>Integer</td>
|
||||
<td>Value of the dice, 1-6 for “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB2.png" width="20" height="20" alt="🎲" />”, “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EAF.png" width="20" height="20" alt="🎯" />” and “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB3.png" width="20" height="20" alt="🎳" />” base emoji, 1-5 for “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8F80.png" width="20" height="20" alt="🏀" />” and “<img class="emoji" src="//telegram.org/img/emoji/40/E29ABD.png" width="20" height="20" alt="⚽" />” base emoji, 1-64 for “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB0.png" width="20" height="20" alt="🎰" />” base emoji</td>
|
||||
<td>Value of the dice, 1-6 for “рџЋІ”, “рџЋЇ” and “рџЋі” base emoji, 1-5 for “рџЏЂ” and “вљЅ” base emoji, 1-64 for “рџЋ°” base emoji</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -1818,7 +1818,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>one_time_keyboard</td>
|
||||
<td>Boolean</td>
|
||||
<td><em>Optional</em>. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to <em>false</em>.</td>
|
||||
<td><em>Optional</em>. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to <em>false</em>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>input_field_placeholder</td>
|
||||
|
|
@ -1960,12 +1960,12 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>switch_inline_query</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.<br><br><strong>Note:</strong> This offers an easy way for users to start using your bot in <a href="/bots/inline">inline mode</a> when they are currently in a private chat with it. Especially useful when combined with <a href="#answerinlinequery"><em>switch_pm…</em></a> actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.</td>
|
||||
<td><em>Optional</em>. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.<br><br><strong>Note:</strong> This offers an easy way for users to start using your bot in <a href="/bots/inline">inline mode</a> when they are currently in a private chat with it. Especially useful when combined with <a href="#answerinlinequery"><em>switch_pm…</em></a> actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>switch_inline_query_current_chat</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.<br><br>This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.</td>
|
||||
<td><em>Optional</em>. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.<br><br>This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>callback_game</td>
|
||||
|
|
@ -2105,7 +2105,7 @@ To learn how to create…">
|
|||
<li>Explain the user how to send a command with parameters (e.g. /newpoll question answer1 answer2). May be appealing for hardcore users but lacks modern day polish.</li>
|
||||
<li>Guide the user through a step-by-step process. 'Please send me your question', 'Cool, now let's add the first answer option', 'Great. Keep adding answer options, then send /done when you're ready'.</li>
|
||||
</ul>
|
||||
<p>The last option is definitely more attractive. And if you use <a href="#forcereply">ForceReply</a> in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.</p>
|
||||
<p>The last option is definitely more attractive. And if you use <a href="#forcereply">ForceReply</a> in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="chatphoto" href="#chatphoto"><i class="anchor-icon"></i></a>ChatPhoto</h4>
|
||||
<p>This object represents a chat photo.</p>
|
||||
|
|
@ -2837,7 +2837,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>media</td>
|
||||
<td>String</td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -2875,12 +2875,12 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>media</td>
|
||||
<td>String</td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -2938,12 +2938,12 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>media</td>
|
||||
<td>String</td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -2996,12 +2996,12 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>media</td>
|
||||
<td>String</td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3054,12 +3054,12 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>media</td>
|
||||
<td>String</td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>File to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><em>Optional</em>. 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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3153,7 +3153,7 @@ To learn how to create…">
|
|||
<td>entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in message text, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in message text, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_web_page_preview</td>
|
||||
|
|
@ -3345,7 +3345,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the new caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the new caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -3395,7 +3395,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>photo</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>Photo to send. Pass a file_id as String 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. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>Photo to send. Pass a file_id as String 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. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3413,7 +3413,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -3464,7 +3464,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>audio</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>Audio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>Audio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3482,7 +3482,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>duration</td>
|
||||
|
|
@ -3506,7 +3506,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -3556,13 +3556,13 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>document</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>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. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3580,7 +3580,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_content_type_detection</td>
|
||||
|
|
@ -3636,7 +3636,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>video</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>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. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>duration</td>
|
||||
|
|
@ -3660,7 +3660,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3678,7 +3678,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>supports_streaming</td>
|
||||
|
|
@ -3734,7 +3734,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>animation</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>Animation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>Animation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>duration</td>
|
||||
|
|
@ -3758,7 +3758,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3776,7 +3776,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -3826,7 +3826,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>voice</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>Audio 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. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>Audio 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. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>caption</td>
|
||||
|
|
@ -3844,7 +3844,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>duration</td>
|
||||
|
|
@ -3900,7 +3900,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>video_note</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>Video note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. <a href="#sending-files">More info on Sending Files »</a>. Sending video notes by a URL is currently unsupported</td>
|
||||
<td>Video note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. <a href="#sending-files">More info on Sending Files В»</a>. Sending video notes by a URL is currently unsupported</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>duration</td>
|
||||
|
|
@ -3918,7 +3918,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>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>. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -4406,7 +4406,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>explanation_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the poll explanation, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the poll explanation, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>open_period</td>
|
||||
|
|
@ -4474,7 +4474,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>emoji</td>
|
||||
<td>String</td>
|
||||
<td>Optional</td>
|
||||
<td>Emoji on which the dice throw animation is based. Currently, must be one of “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB2.png" width="20" height="20" alt="🎲" />”, “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EAF.png" width="20" height="20" alt="🎯" />”, “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8F80.png" width="20" height="20" alt="🏀" />”, “<img class="emoji" src="//telegram.org/img/emoji/40/E29ABD.png" width="20" height="20" alt="⚽" />”, “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB3.png" width="20" height="20" alt="🎳" />”, or “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB0.png" width="20" height="20" alt="🎰" />”. Dice can have values 1-6 for “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB2.png" width="20" height="20" alt="🎲" />”, “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EAF.png" width="20" height="20" alt="🎯" />” and “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB3.png" width="20" height="20" alt="🎳" />”, values 1-5 for “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8F80.png" width="20" height="20" alt="🏀" />” and “<img class="emoji" src="//telegram.org/img/emoji/40/E29ABD.png" width="20" height="20" alt="⚽" />”, and values 1-64 for “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB0.png" width="20" height="20" alt="🎰" />”. Defaults to “<img class="emoji" src="//telegram.org/img/emoji/40/F09F8EB2.png" width="20" height="20" alt="🎲" />”</td>
|
||||
<td>Emoji on which the dice throw animation is based. Currently, must be one of “рџЋІ”, “рџЋЇ”, “рџЏЂ”, “вљЅ”, “рџЋі”, or “рџЋ°”. Dice can have values 1-6 for “рџЋІ”, “рџЋЇ” and “рџЋі”, values 1-5 for “рџЏЂ” and “вљЅ”, and values 1-64 for “рџЋ°”. Defaults to “рџЋІ”</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -4839,7 +4839,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>permissions</td>
|
||||
<td><a href="#chatpermissions">ChatPermissions</a></td>
|
||||
<td>Yes</td>
|
||||
<td>New default chat permissions</td>
|
||||
<td>A JSON-serialized object for new default chat permissions</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -5327,7 +5327,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td>Optional</td>
|
||||
<td>URL that will be opened by the user's client. If you have created a <a href="#game">Game</a> and accepted the conditions via <a href="https://t.me/botfather">@Botfather</a>, specify the URL that opens your game — note that this will only work if the query comes from a <a href="#inlinekeyboardbutton"><em>callback_game</em></a> button.<br><br>Otherwise, you may use links like <code>t.me/your_bot?start=XXXX</code> that open your bot with a parameter.</td>
|
||||
<td>URL that will be opened by the user's client. If you have created a <a href="#game">Game</a> and accepted the conditions via <a href="https://t.me/botfather">@Botfather</a>, specify the URL that opens your game — note that this will only work if the query comes from a <a href="#inlinekeyboardbutton"><em>callback_game</em></a> button.<br><br>Otherwise, you may use links like <code>t.me/your_bot?start=XXXX</code> that open your bot with a parameter.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cache_time</td>
|
||||
|
|
@ -5472,7 +5472,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in message text, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in message text, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_web_page_preview</td>
|
||||
|
|
@ -5534,7 +5534,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>caption_entities</td>
|
||||
<td>Array of <a href="#messageentity">MessageEntity</a></td>
|
||||
<td>Optional</td>
|
||||
<td>List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
<td>A JSON-serialized list of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>reply_markup</td>
|
||||
|
|
@ -5847,7 +5847,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>sticker</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Yes</td>
|
||||
<td>Sticker 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 .WEBP file from the Internet, or upload a new one using multipart/form-data. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td>Sticker 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 .WEBP file from the Internet, or upload a new one using multipart/form-data. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
@ -5917,7 +5917,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>png_sticker</td>
|
||||
<td><a href="#inputfile">InputFile</a></td>
|
||||
<td>Yes</td>
|
||||
<td><strong>PNG</strong> image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><strong>PNG</strong> image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -5955,7 +5955,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>png_sticker</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td><strong>PNG</strong> image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a <em>file_id</em> as a String to send a file that already exists on the Telegram servers, 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. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><strong>PNG</strong> image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a <em>file_id</em> as a String to send a file that already exists on the Telegram servers, 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. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tgs_sticker</td>
|
||||
|
|
@ -6011,7 +6011,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>png_sticker</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td><strong>PNG</strong> image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a <em>file_id</em> as a String to send a file that already exists on the Telegram servers, 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. <a href="#sending-files">More info on Sending Files »</a></td>
|
||||
<td><strong>PNG</strong> image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a <em>file_id</em> as a String to send a file that already exists on the Telegram servers, 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. <a href="#sending-files">More info on Sending Files В»</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tgs_sticker</td>
|
||||
|
|
@ -6107,7 +6107,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>thumb</td>
|
||||
<td><a href="#inputfile">InputFile</a> or String</td>
|
||||
<td>Optional</td>
|
||||
<td>A <strong>PNG</strong> image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a <strong>TGS</strong> animation with the thumbnail up to 32 kilobytes in size; see <a href="https://core.telegram.org/animated_stickers#technical-requirements"><a href="https://core.telegram.org/animated_stickers#technical-requirements">https://core.telegram.org/animated_stickers#technical-requirements</a></a> for animated sticker technical requirements. Pass a <em>file_id</em> as a String to send a file that already exists on the Telegram servers, 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. <a href="#sending-files">More info on Sending Files »</a>. Animated sticker set thumbnail can't be uploaded via HTTP URL.</td>
|
||||
<td>A <strong>PNG</strong> image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a <strong>TGS</strong> animation with the thumbnail up to 32 kilobytes in size; see <a href="https://core.telegram.org/animated_stickers#technical-requirements"><a href="https://core.telegram.org/animated_stickers#technical-requirements">https://core.telegram.org/animated_stickers#technical-requirements</a></a> for animated sticker technical requirements. Pass a <em>file_id</em> as a String to send a file that already exists on the Telegram servers, 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. <a href="#sending-files">More info on Sending Files В»</a>. Animated sticker set thumbnail can't be uploaded via HTTP URL.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -9176,7 +9176,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
</tbody>
|
||||
</table>
|
||||
<hr>
|
||||
<p>And that's about all we've got for now.<br>If you've got any questions, please check out our <a href="/bots/faq"><strong>Bot FAQ »</strong></a></p>
|
||||
<p>And that's about all we've got for now.<br>If you've got any questions, please check out our <a href="/bots/faq"><strong>Bot FAQ В»</strong></a></p>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in a new issue