mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-12-28 23:38:26 +01:00
Update content of files
This commit is contained in:
GitHub Action
parent
7de5e1649c
commit
ff08f561f3
2 changed files with 52 additions and 52 deletions
|
|
@ -140,7 +140,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>
|
||||
|
|
@ -156,7 +156,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>update_id</td>
|
||||
<td>Integer</td>
|
||||
<td>The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using <a href="#setwebhook">Webhooks</a>, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.</td>
|
||||
<td>The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using <a href="#setwebhook">webhooks</a>, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>message</td>
|
||||
|
|
@ -272,8 +272,8 @@ To learn how to create…">
|
|||
<p><strong>Notes</strong><br><strong>1.</strong> This method will not work if an outgoing webhook is set up.<br><strong>2.</strong> In order to avoid getting duplicate updates, recalculate <em>offset</em> after each server response.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="setwebhook" href="#setwebhook"><i class="anchor-icon"></i></a>setWebhook</h4>
|
||||
<p>Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized <a href="#update">Update</a>. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns <em>True</em> on success.</p>
|
||||
<p>If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. <code>https://www.example.com/<token></code>. Since nobody else knows your bot's token, you can be pretty sure it's us.</p>
|
||||
<p>Use this method to specify a URL and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified URL, containing a JSON-serialized <a href="#update">Update</a>. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns <em>True</em> on success.</p>
|
||||
<p>If you'd like to make sure that the webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. <code>https://www.example.com/<token></code>. Since nobody else knows your bot's token, you can be pretty sure it's us.</p>
|
||||
<table class="table">
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -288,7 +288,7 @@ To learn how to create…">
|
|||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td>Yes</td>
|
||||
<td>HTTPS url to send updates to. Use an empty string to remove webhook integration</td>
|
||||
<td>HTTPS URL to send updates to. Use an empty string to remove webhook integration</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>certificate</td>
|
||||
|
|
@ -323,8 +323,8 @@ To learn how to create…">
|
|||
</tbody>
|
||||
</table>
|
||||
<blockquote>
|
||||
<p><strong>Notes</strong><br><strong>1.</strong> You will not be able to receive updates using <a href="#getupdates">getUpdates</a> for as long as an outgoing webhook is set up.<br><strong>2.</strong> To use a self-signed certificate, you need to upload your <a href="/bots/self-signed">public key certificate</a> using <em>certificate</em> parameter. Please upload as InputFile, sending a String will not work.<br><strong>3.</strong> Ports currently supported <em>for Webhooks</em>: <strong>443, 80, 88, 8443</strong>.</p>
|
||||
<p><strong>NEW!</strong> If you're having any trouble setting up webhooks, please check out this <a href="/bots/webhooks">amazing guide to Webhooks</a>.</p>
|
||||
<p><strong>Notes</strong><br><strong>1.</strong> You will not be able to receive updates using <a href="#getupdates">getUpdates</a> for as long as an outgoing webhook is set up.<br><strong>2.</strong> To use a self-signed certificate, you need to upload your <a href="/bots/self-signed">public key certificate</a> using <em>certificate</em> parameter. Please upload as InputFile, sending a String will not work.<br><strong>3.</strong> Ports currently supported <em>for webhooks</em>: <strong>443, 80, 88, 8443</strong>.</p>
|
||||
<p><strong>NEW!</strong> If you're having any trouble setting up webhooks, please check out this <a href="/bots/webhooks">amazing guide to webhooks</a>.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="deletewebhook" href="#deletewebhook"><i class="anchor-icon"></i></a>deleteWebhook</h4>
|
||||
<p>Use this method to remove webhook integration if you decide to switch back to <a href="#getupdates">getUpdates</a>. Returns <em>True</em> on success.</p>
|
||||
|
|
@ -938,7 +938,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. For “text_link” only, url that will be opened after user taps on the text</td>
|
||||
<td><em>Optional</em>. For “text_link” only, URL that will be opened after user taps on the text</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>user</td>
|
||||
|
|
@ -1198,7 +1198,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>mime_type</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. Mime type of a file as defined by sender</td>
|
||||
<td><em>Optional</em>. Mime type of the file as defined by sender</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>file_size</td>
|
||||
|
|
@ -1927,7 +1927,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. HTTP or tg:// url to be opened when the button is pressed. Links <code>tg://user?id=<user_id></code> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.</td>
|
||||
<td><em>Optional</em>. HTTP or tg:// URL to be opened when the button is pressed. Links <code>tg://user?id=<user_id></code> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>callback_data</td>
|
||||
|
|
@ -2046,7 +2046,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>data</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. Data associated with the callback button. Be aware that the message, which originated the query, can contain no callback buttons with this data.</td>
|
||||
<td><em>Optional</em>. Data associated with the callback button. Be aware that the message, from which originated the query, can contain no callback buttons with this data.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>game_short_name</td>
|
||||
|
|
@ -5699,7 +5699,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<h4><a class="anchor" name="answercallbackquery" href="#answercallbackquery"><i class="anchor-icon"></i></a>answerCallbackQuery</h4>
|
||||
<p>Use this method to send answers to callback queries sent from <a href="/bots#inline-keyboards-and-on-the-fly-updating">inline keyboards</a>. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, <em>True</em> is returned.</p>
|
||||
<blockquote>
|
||||
<p>Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via <a href="https://t.me/botfather">@Botfather</a> and accept the terms. Otherwise, you may use links like <code>t.me/your_bot?start=XXXX</code> that open your bot with a parameter.</p>
|
||||
<p>Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via <a href="https://t.me/botfather">@BotFather</a> and accept the terms. Otherwise, you may use links like <code>t.me/your_bot?start=XXXX</code> that open your bot with a parameter.</p>
|
||||
</blockquote>
|
||||
<table class="table">
|
||||
<thead>
|
||||
|
|
@ -5733,7 +5733,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>
|
||||
|
|
@ -7108,7 +7108,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>mime_type</td>
|
||||
<td>String</td>
|
||||
<td>Mime type of the content of video url, “text/html” or “video/mp4”</td>
|
||||
<td>Mime type of the content of the video URL, “text/html” or “video/mp4”</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb_url</td>
|
||||
|
|
@ -8318,7 +8318,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>provider_token</td>
|
||||
<td>String</td>
|
||||
<td>Payment provider token, obtained via <a href="https://t.me/botfather">Botfather</a></td>
|
||||
<td>Payment provider token, obtained via <a href="https://t.me/botfather">@BotFather</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>currency</td>
|
||||
|
|
@ -8348,12 +8348,12 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>photo_url</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.</td>
|
||||
<td><em>Optional</em>. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_size</td>
|
||||
<td>Integer</td>
|
||||
<td><em>Optional</em>. Photo size</td>
|
||||
<td><em>Optional</em>. Photo size in bytes</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_width</td>
|
||||
|
|
@ -8388,12 +8388,12 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>send_phone_number_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if user's phone number should be sent to provider</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if the user's phone number should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>send_email_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if user's email address should be sent to provider</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if the user's email address should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>is_flexible</td>
|
||||
|
|
@ -8440,7 +8440,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p><strong>Note:</strong> It is necessary to enable <a href="/bots/inline#collecting-feedback">inline feedback</a> via <a href="https://t.me/botfather">@Botfather</a> in order to receive these objects in updates.</p>
|
||||
<p><strong>Note:</strong> It is necessary to enable <a href="/bots/inline#collecting-feedback">inline feedback</a> via <a href="https://t.me/botfather">@BotFather</a> in order to receive these objects in updates.</p>
|
||||
<h4><a class="anchor" name="answerwebappquery" href="#answerwebappquery"><i class="anchor-icon"></i></a>answerWebAppQuery</h4>
|
||||
<p>Use this method to set the result of an interaction with a <a href="/bots/webapps">Web App</a> and send a corresponding message on behalf of the user to the chat from which the query originated. On success, a <a href="#sentwebappmessage">SentWebAppMessage</a> object is returned.</p>
|
||||
<table class="table">
|
||||
|
|
@ -8527,7 +8527,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>provider_token</td>
|
||||
<td>String</td>
|
||||
<td>Yes</td>
|
||||
<td>Payments provider token, obtained via <a href="https://t.me/botfather">Botfather</a></td>
|
||||
<td>Payment provider token, obtained via <a href="https://t.me/botfather">@BotFather</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>currency</td>
|
||||
|
|
@ -8563,7 +8563,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>provider_data</td>
|
||||
<td>String</td>
|
||||
<td>Optional</td>
|
||||
<td>A JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.</td>
|
||||
<td>JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_url</td>
|
||||
|
|
@ -8575,7 +8575,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>photo_size</td>
|
||||
<td>Integer</td>
|
||||
<td>Optional</td>
|
||||
<td>Photo size</td>
|
||||
<td>Photo size in bytes</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_width</td>
|
||||
|
|
@ -8617,13 +8617,13 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>send_phone_number_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td>Optional</td>
|
||||
<td>Pass <em>True</em>, if user's phone number should be sent to provider</td>
|
||||
<td>Pass <em>True</em>, if the user's phone number should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>send_email_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td>Optional</td>
|
||||
<td>Pass <em>True</em>, if user's email address should be sent to provider</td>
|
||||
<td>Pass <em>True</em>, if the user's email address should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>is_flexible</td>
|
||||
|
|
@ -9553,7 +9553,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>game_short_name</td>
|
||||
<td>String</td>
|
||||
<td>Yes</td>
|
||||
<td>Short name of the game, serves as the unique identifier for the game. Set up your games via <a href="https://t.me/botfather">Botfather</a>.</td>
|
||||
<td>Short name of the game, serves as the unique identifier for the game. Set up your games via <a href="https://t.me/botfather">@BotFather</a>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
|
|||
|
|
@ -140,7 +140,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>
|
||||
|
|
@ -156,7 +156,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>update_id</td>
|
||||
<td>Integer</td>
|
||||
<td>The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using <a href="#setwebhook">Webhooks</a>, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.</td>
|
||||
<td>The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using <a href="#setwebhook">webhooks</a>, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>message</td>
|
||||
|
|
@ -272,8 +272,8 @@ To learn how to create…">
|
|||
<p><strong>Notes</strong><br><strong>1.</strong> This method will not work if an outgoing webhook is set up.<br><strong>2.</strong> In order to avoid getting duplicate updates, recalculate <em>offset</em> after each server response.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="setwebhook" href="#setwebhook"><i class="anchor-icon"></i></a>setWebhook</h4>
|
||||
<p>Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized <a href="#update">Update</a>. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns <em>True</em> on success.</p>
|
||||
<p>If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. <code>https://www.example.com/<token></code>. Since nobody else knows your bot's token, you can be pretty sure it's us.</p>
|
||||
<p>Use this method to specify a URL and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified URL, containing a JSON-serialized <a href="#update">Update</a>. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns <em>True</em> on success.</p>
|
||||
<p>If you'd like to make sure that the webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. <code>https://www.example.com/<token></code>. Since nobody else knows your bot's token, you can be pretty sure it's us.</p>
|
||||
<table class="table">
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -288,7 +288,7 @@ To learn how to create…">
|
|||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td>Yes</td>
|
||||
<td>HTTPS url to send updates to. Use an empty string to remove webhook integration</td>
|
||||
<td>HTTPS URL to send updates to. Use an empty string to remove webhook integration</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>certificate</td>
|
||||
|
|
@ -323,8 +323,8 @@ To learn how to create…">
|
|||
</tbody>
|
||||
</table>
|
||||
<blockquote>
|
||||
<p><strong>Notes</strong><br><strong>1.</strong> You will not be able to receive updates using <a href="#getupdates">getUpdates</a> for as long as an outgoing webhook is set up.<br><strong>2.</strong> To use a self-signed certificate, you need to upload your <a href="/bots/self-signed">public key certificate</a> using <em>certificate</em> parameter. Please upload as InputFile, sending a String will not work.<br><strong>3.</strong> Ports currently supported <em>for Webhooks</em>: <strong>443, 80, 88, 8443</strong>.</p>
|
||||
<p><strong>NEW!</strong> If you're having any trouble setting up webhooks, please check out this <a href="/bots/webhooks">amazing guide to Webhooks</a>.</p>
|
||||
<p><strong>Notes</strong><br><strong>1.</strong> You will not be able to receive updates using <a href="#getupdates">getUpdates</a> for as long as an outgoing webhook is set up.<br><strong>2.</strong> To use a self-signed certificate, you need to upload your <a href="/bots/self-signed">public key certificate</a> using <em>certificate</em> parameter. Please upload as InputFile, sending a String will not work.<br><strong>3.</strong> Ports currently supported <em>for webhooks</em>: <strong>443, 80, 88, 8443</strong>.</p>
|
||||
<p><strong>NEW!</strong> If you're having any trouble setting up webhooks, please check out this <a href="/bots/webhooks">amazing guide to webhooks</a>.</p>
|
||||
</blockquote>
|
||||
<h4><a class="anchor" name="deletewebhook" href="#deletewebhook"><i class="anchor-icon"></i></a>deleteWebhook</h4>
|
||||
<p>Use this method to remove webhook integration if you decide to switch back to <a href="#getupdates">getUpdates</a>. Returns <em>True</em> on success.</p>
|
||||
|
|
@ -938,7 +938,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. For “text_link” only, url that will be opened after user taps on the text</td>
|
||||
<td><em>Optional</em>. For “text_link” only, URL that will be opened after user taps on the text</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>user</td>
|
||||
|
|
@ -1198,7 +1198,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>mime_type</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. Mime type of a file as defined by sender</td>
|
||||
<td><em>Optional</em>. Mime type of the file as defined by sender</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>file_size</td>
|
||||
|
|
@ -1927,7 +1927,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>url</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. HTTP or tg:// url to be opened when the button is pressed. Links <code>tg://user?id=<user_id></code> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.</td>
|
||||
<td><em>Optional</em>. HTTP or tg:// URL to be opened when the button is pressed. Links <code>tg://user?id=<user_id></code> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>callback_data</td>
|
||||
|
|
@ -2046,7 +2046,7 @@ To learn how to create…">
|
|||
<tr>
|
||||
<td>data</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. Data associated with the callback button. Be aware that the message, which originated the query, can contain no callback buttons with this data.</td>
|
||||
<td><em>Optional</em>. Data associated with the callback button. Be aware that the message, from which originated the query, can contain no callback buttons with this data.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>game_short_name</td>
|
||||
|
|
@ -5699,7 +5699,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<h4><a class="anchor" name="answercallbackquery" href="#answercallbackquery"><i class="anchor-icon"></i></a>answerCallbackQuery</h4>
|
||||
<p>Use this method to send answers to callback queries sent from <a href="/bots#inline-keyboards-and-on-the-fly-updating">inline keyboards</a>. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, <em>True</em> is returned.</p>
|
||||
<blockquote>
|
||||
<p>Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via <a href="https://t.me/botfather">@Botfather</a> and accept the terms. Otherwise, you may use links like <code>t.me/your_bot?start=XXXX</code> that open your bot with a parameter.</p>
|
||||
<p>Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via <a href="https://t.me/botfather">@BotFather</a> and accept the terms. Otherwise, you may use links like <code>t.me/your_bot?start=XXXX</code> that open your bot with a parameter.</p>
|
||||
</blockquote>
|
||||
<table class="table">
|
||||
<thead>
|
||||
|
|
@ -5733,7 +5733,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>
|
||||
|
|
@ -7108,7 +7108,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>mime_type</td>
|
||||
<td>String</td>
|
||||
<td>Mime type of the content of video url, “text/html” or “video/mp4”</td>
|
||||
<td>Mime type of the content of the video URL, “text/html” or “video/mp4”</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>thumb_url</td>
|
||||
|
|
@ -8318,7 +8318,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>provider_token</td>
|
||||
<td>String</td>
|
||||
<td>Payment provider token, obtained via <a href="https://t.me/botfather">Botfather</a></td>
|
||||
<td>Payment provider token, obtained via <a href="https://t.me/botfather">@BotFather</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>currency</td>
|
||||
|
|
@ -8348,12 +8348,12 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>photo_url</td>
|
||||
<td>String</td>
|
||||
<td><em>Optional</em>. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.</td>
|
||||
<td><em>Optional</em>. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_size</td>
|
||||
<td>Integer</td>
|
||||
<td><em>Optional</em>. Photo size</td>
|
||||
<td><em>Optional</em>. Photo size in bytes</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_width</td>
|
||||
|
|
@ -8388,12 +8388,12 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<tr>
|
||||
<td>send_phone_number_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if user's phone number should be sent to provider</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if the user's phone number should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>send_email_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if user's email address should be sent to provider</td>
|
||||
<td><em>Optional</em>. Pass <em>True</em>, if the user's email address should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>is_flexible</td>
|
||||
|
|
@ -8440,7 +8440,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p><strong>Note:</strong> It is necessary to enable <a href="/bots/inline#collecting-feedback">inline feedback</a> via <a href="https://t.me/botfather">@Botfather</a> in order to receive these objects in updates.</p>
|
||||
<p><strong>Note:</strong> It is necessary to enable <a href="/bots/inline#collecting-feedback">inline feedback</a> via <a href="https://t.me/botfather">@BotFather</a> in order to receive these objects in updates.</p>
|
||||
<h4><a class="anchor" name="answerwebappquery" href="#answerwebappquery"><i class="anchor-icon"></i></a>answerWebAppQuery</h4>
|
||||
<p>Use this method to set the result of an interaction with a <a href="/bots/webapps">Web App</a> and send a corresponding message on behalf of the user to the chat from which the query originated. On success, a <a href="#sentwebappmessage">SentWebAppMessage</a> object is returned.</p>
|
||||
<table class="table">
|
||||
|
|
@ -8527,7 +8527,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>provider_token</td>
|
||||
<td>String</td>
|
||||
<td>Yes</td>
|
||||
<td>Payments provider token, obtained via <a href="https://t.me/botfather">Botfather</a></td>
|
||||
<td>Payment provider token, obtained via <a href="https://t.me/botfather">@BotFather</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>currency</td>
|
||||
|
|
@ -8563,7 +8563,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>provider_data</td>
|
||||
<td>String</td>
|
||||
<td>Optional</td>
|
||||
<td>A JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.</td>
|
||||
<td>JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_url</td>
|
||||
|
|
@ -8575,7 +8575,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>photo_size</td>
|
||||
<td>Integer</td>
|
||||
<td>Optional</td>
|
||||
<td>Photo size</td>
|
||||
<td>Photo size in bytes</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>photo_width</td>
|
||||
|
|
@ -8617,13 +8617,13 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>send_phone_number_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td>Optional</td>
|
||||
<td>Pass <em>True</em>, if user's phone number should be sent to provider</td>
|
||||
<td>Pass <em>True</em>, if the user's phone number should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>send_email_to_provider</td>
|
||||
<td>Boolean</td>
|
||||
<td>Optional</td>
|
||||
<td>Pass <em>True</em>, if user's email address should be sent to provider</td>
|
||||
<td>Pass <em>True</em>, if the user's email address should be sent to provider</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>is_flexible</td>
|
||||
|
|
@ -9553,7 +9553,7 @@ pre-formatted fixed-width code block written in the Python programming language
|
|||
<td>game_short_name</td>
|
||||
<td>String</td>
|
||||
<td>Yes</td>
|
||||
<td>Short name of the game, serves as the unique identifier for the game. Set up your games via <a href="https://t.me/botfather">Botfather</a>.</td>
|
||||
<td>Short name of the game, serves as the unique identifier for the game. Set up your games via <a href="https://t.me/botfather">@BotFather</a>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>disable_notification</td>
|
||||
|
|
|
|||
Loading…
Reference in a new issue