mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-12-01 12:42:07 +01:00
Update content of files
This commit is contained in:
parent
8d5b831545
commit
a16d5d56c8
3 changed files with 8 additions and 5 deletions
|
@ -49,7 +49,7 @@
|
|||
<h4><a class="anchor" href="#error-type" id="error-type" name="error-type"><i class="anchor-icon"></i></a>Error Type</h4>
|
||||
<p>A string literal in the form of <code>/[A-Z_0-9]+/</code>, which summarizes the problem. For example, <code>AUTH_KEY_UNREGISTERED</code>. This is an optional parameter.</p>
|
||||
<h4><a class="anchor" href="#error-database" id="error-database" name="error-database"><i class="anchor-icon"></i></a>Error Database</h4>
|
||||
<p>A full machine-readable JSON list of RPC errors that can be returned by all methods in the API can be found <a href="/file/464001230/1129a/YMkJ7A1KB-g.85383.json/f3dde939df04dfdf86">here »</a>, what follows is a description of its fields: </p>
|
||||
<p>A full machine-readable JSON list of RPC errors that can be returned by all methods in the API can be found <a href="/file/464001413/fd7b/hMQMyQzkbzQ.85929.json/b3dbd40b4ae42ebfc5">here »</a>, what follows is a description of its fields: </p>
|
||||
<ul>
|
||||
<li><code>errors</code> - All error messages and codes for each method (object).<ul>
|
||||
<li>Keys: Error codes as strings (numeric strings)</li>
|
||||
|
|
|
@ -126,7 +126,7 @@
|
|||
<tr>
|
||||
<td>400</td>
|
||||
<td>HIDE_REQUESTER_MISSING</td>
|
||||
<td> </td>
|
||||
<td>The join request was missing or was already handled.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>400</td>
|
||||
|
|
|
@ -191,7 +191,7 @@
|
|||
<tr>
|
||||
<td>400</td>
|
||||
<td>STICKER_TGS_NODOC</td>
|
||||
<td>Incorrect document type for sticker.</td>
|
||||
<td>You must send the animated sticker as a document.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>400</td>
|
||||
|
@ -216,7 +216,7 @@
|
|||
<tr>
|
||||
<td>400</td>
|
||||
<td>STICKER_VIDEO_NODOC</td>
|
||||
<td> </td>
|
||||
<td>You must send the video sticker as a document.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>400</td>
|
||||
|
@ -230,7 +230,10 @@
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3></div>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3>
|
||||
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
|
||||
<h4><a class="anchor" href="#deep-links" id="deep-links" name="deep-links"><i class="anchor-icon"></i></a><a href="/api/links">Deep links</a></h4>
|
||||
<p>Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
Loading…
Reference in a new issue