OpenSource/telegram-crawler
OpenSource/telegram-crawler
1
0
Fork 0
mirror of https://github.com/MarshalX/telegram-crawler.git synced 2024-11-28 19:23:11 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update content of files

Browse source
This commit is contained in:
GitHub Action 2022-02-23 20:21:59 +00:00
parent be9e876fe8
commit 5fbb2b3da5
26 changed files with 106 additions and 88 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

45
data/corefork.telegram.org/api/errors.html
View file

@ -45,6 +45,51 @@
<p>Numerical value similar to HTTP status. Contains information on the type of error that occurred: for example, a data input error, privacy error, or server error. This is a required parameter.</p>
<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/464001165/11680/luDh6JDlj7I.76063.json/32eb0548a1749ae301">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>
<li>Values: All error messages for each method (object)<ul>
<li>Keys: Error messages (string)</li>
<li>Values: An array of methods which may emit this error (array of strings)</li>
</ul>
</li>
</ul>
</li>
<li><code>descriptions</code> - Descriptions for every error mentioned in <code>errors</code> (and a few other errors not related to a specific method)<ul>
<li>Keys: Error messages</li>
<li>Values: Error descriptions</li>
</ul>
</li>
<li><code>user_only</code> - A list of methods that can only be used by users, <strong>not</strong> bots.</li>
</ul>
<p>Error messages and error descriptions may contain <code>printf</code> placeholders in key positions, for now only <code>%d</code> is used to map durations contained in error messages to error descriptions.</p>
<p>Example:</p>
<pre><code class="language-json">{
"errors": {
"420": {
"2FA_CONFIRM_WAIT_%d": [
"account.deleteAccount"
],
"SLOWMODE_WAIT_%d": [
"messages.forwardMessages",
"messages.sendInlineBotResult",
"messages.sendMedia",
"messages.sendMessage",
"messages.sendMultiMedia"
]
}
},
"descriptions": {
"2FA_CONFIRM_WAIT_%d": "Since this account is active and protected by a 2FA password, we will delete it in 1 week for security purposes. You can cancel this process at any time, you'll be able to reset your account in %d seconds.",
"SLOWMODE_WAIT_%d": "Slowmode is enabled in this chat: wait %d seconds before sending another message to this chat.",
"FLOOD_WAIT_%d": "Please wait %d seconds before repeating the action."
},
"user_only": {
"account.deleteAccount"
}
}</code></pre>
<hr>
<h4><a class="anchor" href="#error-constructors" id="error-constructors" name="error-constructors"><i class="anchor-icon"></i></a>Error Constructors</h4>
<p>There should be a way to handle errors that are returned in <a href="/mtproto/service_messages#rpc-error">rpc_error</a> constructors.</p>

2
data/corefork.telegram.org/method/account.updatePasswordSettings
View file

@ -93,7 +93,7 @@
<tr>
<td>400</td>
<td>EMAIL_UNCONFIRMED_%d</td>
<td>The provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use <a href="https://core.telegram.org/method/account.verifyEmail">account.verifyEmail</a> to enter the received verification code and enable the recovery email.</td>
<td>The provided email isn't confirmed, %d is the length of the verification code that was just sent to the email: use <a href="https://core.telegram.org/method/account.verifyEmail">account.verifyEmail</a> to enter the received verification code and enable the recovery email.</td>
</tr>
<tr>
<td>400</td>

5
data/corefork.telegram.org/method/account.updateUsername
View file

@ -86,11 +86,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>USERNAME_INVALID</td>
<td>The provided username is not valid.</td>

6
data/corefork.telegram.org/method/auth.sendCode
View file

@ -110,9 +110,9 @@
<td>This API id was published somewhere, you can't use it now.</td>
</tr>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
<td>500</td>
<td>AUTH_RESTART</td>
<td>Restart the authorization process.</td>
</tr>
<tr>
<td>400</td>

5
data/corefork.telegram.org/method/auth.signIn
View file

@ -120,6 +120,11 @@
<td>PHONE_NUMBER_UNOCCUPIED</td>
<td>The phone number is not yet being used.</td>
</tr>
<tr>
<td>500</td>
<td>SIGN_IN_FAILED</td>
<td>Failure while signing in.</td>
</tr>
</tbody>
</table>
<h3><a class="anchor" href="#query-example" id="query-example" name="query-example"><i class="anchor-icon"></i></a>Query example</h3>

5
data/corefork.telegram.org/method/channels.editBanned
View file

@ -102,11 +102,6 @@
<tbody>
<tr>
<td>400</td>
<td>CHANNEL_ADD_INVALID</td>
<td>Internal error.</td>
</tr>
<tr>
<td>400</td>
<td>CHANNEL_INVALID</td>
<td>The provided channel is invalid.</td>
</tr>

5
data/corefork.telegram.org/method/channels.viewSponsoredMessage
View file

@ -95,11 +95,6 @@
<td>CHANNEL_INVALID</td>
<td>The provided channel is invalid.</td>
</tr>
<tr>
<td>400</td>
<td>UNKNOWN_ERROR</td>
<td>Internal error.</td>
</tr>
</tbody>
</table>
<h3><a class="anchor" href="#errors" id="errors" name="errors"><i class="anchor-icon"></i></a>Errors</h3>

5
data/corefork.telegram.org/method/contacts.resolveUsername
View file

@ -85,11 +85,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>CONNECTION_LAYER_INVALID</td>
<td>Layer invalid.</td>

17
data/corefork.telegram.org/method/help.getCdnConfig
View file

@ -59,23 +59,6 @@
<p>This constructor does not require any parameters.</p>
<h3><a class="anchor" href="#result" id="result" name="result"><i class="anchor-icon"></i></a>Result</h3>
<p><a href="/type/CdnConfig">CdnConfig</a></p>
<h3><a class="anchor" href="#possible-errors" id="possible-errors" name="possible-errors"><i class="anchor-icon"></i></a>Possible errors</h3>
<table class="table">
<thead>
<tr>
<th>Code</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</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>
<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="#encrypted-cdns-for-speed-and-security" id="encrypted-cdns-for-speed-and-security" name="encrypted-cdns-for-speed-and-security"><i class="anchor-icon"></i></a><a href="/cdn">Encrypted CDNs for Speed and Security</a></h4></div>

5
data/corefork.telegram.org/method/help.getConfig
View file

@ -91,11 +91,6 @@
</tr>
<tr>
<td>400</td>
<td>INPUT_LAYER_INVALID</td>
<td>The provided layer is invalid.</td>
</tr>
<tr>
<td>400</td>
<td>MSG_ID_INVALID</td>
<td>Invalid message ID provided.</td>
</tr>

5
data/corefork.telegram.org/method/invokeWithLayer.html
View file

@ -110,11 +110,6 @@
</tr>
<tr>
<td>400</td>
<td>INPUT_LAYER_INVALID</td>
<td>The provided layer is invalid.</td>
</tr>
<tr>
<td>400</td>
<td>INVITE_HASH_EXPIRED</td>
<td>The invite link has expired.</td>
</tr>

5
data/corefork.telegram.org/method/messages.createChat
View file

@ -96,6 +96,11 @@
</thead>
<tbody>
<tr>
<td>500</td>
<td>CHAT_ID_GENERATE_FAILED</td>
<td>Failure while generating the chat ID.</td>
</tr>
<tr>
<td>400</td>
<td>CHAT_INVALID</td>
<td>Invalid chat.</td>

5
data/corefork.telegram.org/method/messages.forwardMessages
View file

@ -256,6 +256,11 @@
<td> </td>
</tr>
<tr>
<td>500</td>
<td>RANDOM_ID_DUPLICATE</td>
<td>You provided a random ID that was already used.</td>
</tr>
<tr>
<td>400</td>
<td>RANDOM_ID_INVALID</td>
<td>A provided random ID is invalid.</td>

5
data/corefork.telegram.org/method/messages.getHistory
View file

@ -123,11 +123,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>CHANNEL_INVALID</td>
<td>The provided channel is invalid.</td>

5
data/corefork.telegram.org/method/messages.sendInlineBotResult
View file

@ -226,6 +226,11 @@
<td>The query ID is empty.</td>
</tr>
<tr>
<td>500</td>
<td>RANDOM_ID_DUPLICATE</td>
<td>You provided a random ID that was already used.</td>
</tr>
<tr>
<td>400</td>
<td>RESULT_ID_EMPTY</td>
<td>Result ID empty.</td>

7
data/corefork.telegram.org/method/messages.sendMedia
View file

@ -268,7 +268,7 @@
<tr>
<td>400</td>
<td>FILE_REFERENCE_EXPIRED</td>
<td>File reference expired, it must be refetched as described in <a href="https://core.telegram.org/api/file_reference">https://core.telegram.org/api/file_reference</a>.</td>
<td>File reference expired, it must be refetched as described in <a href="https://core.telegram.org/api/file_reference">the documentation</a>.</td>
</tr>
<tr>
<td>400</td>
@ -381,6 +381,11 @@
<td>Quizes can't have the multiple_choice flag set!</td>
</tr>
<tr>
<td>500</td>
<td>RANDOM_ID_DUPLICATE</td>
<td>You provided a random ID that was already used.</td>
</tr>
<tr>
<td>400</td>
<td>REPLY_MARKUP_BUY_EMPTY</td>
<td>Reply markup for buy button empty.</td>

10
data/corefork.telegram.org/method/messages.sendMessage
View file

@ -156,11 +156,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>BOT_DOMAIN_INVALID</td>
<td>Bot domain invalid.</td>
@ -271,6 +266,11 @@
<td>Invalid poll option provided.</td>
</tr>
<tr>
<td>500</td>
<td>RANDOM_ID_DUPLICATE</td>
<td>You provided a random ID that was already used.</td>
</tr>
<tr>
<td>400</td>
<td>REPLY_MARKUP_INVALID</td>
<td>The provided reply markup is invalid.</td>

5
data/corefork.telegram.org/method/messages.sendMultiMedia
View file

@ -176,6 +176,11 @@
<td>The provided peer id is invalid.</td>
</tr>
<tr>
<td>500</td>
<td>RANDOM_ID_DUPLICATE</td>
<td>You provided a random ID that was already used.</td>
</tr>
<tr>
<td>400</td>
<td>RANDOM_ID_EMPTY</td>
<td>Random ID empty.</td>

5
data/corefork.telegram.org/method/messages.startBot
View file

@ -131,6 +131,11 @@
<td>The provided peer id is invalid.</td>
</tr>
<tr>
<td>500</td>
<td>RANDOM_ID_DUPLICATE</td>
<td>You provided a random ID that was already used.</td>
</tr>
<tr>
<td>400</td>
<td>START_PARAM_EMPTY</td>
<td>The start parameter is empty.</td>

5
data/corefork.telegram.org/method/phone.acceptCall
View file

@ -105,6 +105,11 @@
<td>The call was already declined.</td>
</tr>
<tr>
<td>500</td>
<td>CALL_OCCUPY_FAILED</td>
<td>The call failed because the user is already making another call.</td>
</tr>
<tr>
<td>400</td>
<td>CALL_PEER_INVALID</td>
<td>The provided call peer object is invalid.</td>

5
data/corefork.telegram.org/method/phone.requestCall
View file

@ -120,6 +120,11 @@
<td>The specified user was deleted.</td>
</tr>
<tr>
<td>500</td>
<td>PARTICIPANT_CALL_FAILED</td>
<td>Failure while making call.</td>
</tr>
<tr>
<td>400</td>
<td>PARTICIPANT_VERSION_OUTDATED</td>
<td>The other participant does not use an up to date telegram client with support for calls.</td>

5
data/corefork.telegram.org/method/stickers.createStickerSet
View file

@ -157,11 +157,6 @@
</tr>
<tr>
<td>400</td>
<td>SHORTNAME_OCCUPY_FAILED</td>
<td>An internal error occurred.</td>
</tr>
<tr>
<td>400</td>
<td>STICKERS_EMPTY</td>
<td>No sticker provided.</td>
</tr>

5
data/corefork.telegram.org/method/updates.getChannelDifference
View file

@ -152,6 +152,11 @@
<td>Persistent timestamp invalid.</td>
</tr>
<tr>
<td>500</td>
<td>PERSISTENT_TIMESTAMP_OUTDATED</td>
<td>Channel internal replication issues, try again later (treat this like an RPC_CALL_FAIL).</td>
</tr>
<tr>
<td>400</td>
<td>PINNED_DIALOGS_TOO_MUCH</td>
<td>Too many pinned dialogs.</td>

5
data/corefork.telegram.org/method/updates.getDifference
View file

@ -108,11 +108,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>CDN_METHOD_INVALID</td>
<td>You can't call this method in a CDN DC.</td>

7
data/corefork.telegram.org/method/upload.getFile
View file

@ -111,11 +111,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>CHANNEL_INVALID</td>
<td>The provided channel is invalid.</td>
@ -143,7 +138,7 @@
<tr>
<td>400</td>
<td>FILE_REFERENCE_EXPIRED</td>
<td>File reference expired, it must be refetched as described in <a href="https://core.telegram.org/api/file_reference">https://core.telegram.org/api/file_reference</a>.</td>
<td>File reference expired, it must be refetched as described in <a href="https://core.telegram.org/api/file_reference">the documentation</a>.</td>
</tr>
<tr>
<td>400</td>

10
data/corefork.telegram.org/method/users.getUsers
View file

@ -84,11 +84,6 @@
</thead>
<tbody>
<tr>
<td>401</td>
<td>AUTH_KEY_PERM_EMPTY</td>
<td>The temporary auth key must be binded to the permanent auth key to use these methods.</td>
</tr>
<tr>
<td>400</td>
<td>CHANNEL_INVALID</td>
<td>The provided channel is invalid.</td>
@ -100,11 +95,6 @@
</tr>
<tr>
<td>400</td>
<td>INPUT_LAYER_INVALID</td>
<td>The provided layer is invalid.</td>
</tr>
<tr>
<td>400</td>
<td>MSG_ID_INVALID</td>
<td>Invalid message ID provided.</td>
</tr>