Update content of files

data/web/corefork.telegram.org/api/errors.html

@@ -49,7 +49,7 @@ An error is characterized by several parameters:</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/464001274/fb29/W9EMV_oFbts.96573.json/0e00d744fe39e5a4f2">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/464001898/f343/2jELphxDfcg.96919.json/329f1cb1d50599e5ed">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>

data/web/corefork.telegram.org/api/layers.html

@@ -46,12 +46,15 @@
 
 <p>Below you will find information on schema changes. For more details on the use of layers, see <a href="/api/invoking#layers">Invoking API methods</a>.</p>
 <h3><a class="anchor" href="#layer-158" id="layer-158" name="layer-158"><i class="anchor-icon"></i></a><a href="/schema?layer=158">Layer 158</a></h3>
-<p>To view all the changes since the last update, start reading the changelog @ <a href="/api/layers#layer-146">Layer 146</a>.  </p>
+<p>To view all the changes since the last update, start reading the changelog @ <a href="#layer-146">Layer 146</a>.</p>
+<p>Most importantly, <a href="#layer-152">layer 152</a> added support for Firebase SMS authentication, which in some conditions may be required by the server in order to send SMS codes.<br>
+Currently, only official apps can make use of Firebase SMS authentication: this means that in some conditions, only the official applications can receive a login/signup code via SMS/call.<br>
+Third-party apps may log in using any of the other code delivery methods (Telegram codes, Fragment codes, email codes, <a href="/api/auth#future-auth-tokens">future auth tokens</a>, <a href="/api/qr-login">QR codes</a>).</p>
 <p>You can now <a href="/api/folders#shared-folders">share folders »</a>, <a href="/api/fragment">use collectible usernames for bots »</a>, <a href="/method/messages.setChatWallPaper">set custom per-chat wallpapers »</a> and <a href="/method/auth.resetLoginEmail">reset the login email »</a>.<br>
 Users may now edit the <a href="/api/bots/info">usernames, name, about text, description and profile picture</a> of bots they own using the API.<br>
 Bots can now directly invoke <a href="/method/photos.updateProfilePhoto">photos.updateProfilePhoto</a> and <a href="/method/photos.uploadProfilePhoto">photos.uploadProfilePhoto</a> to edit their own profile picture.<br>
 Bots may also now specify a custom peer filter when using <a href="/constructor/keyboardButtonSwitchInline">keyboardButtonSwitchInline</a> buttons.</p>
-<p>Added the <a href="/api/config#small-queue-max-active-operations-count"><code>small_queue_max_active_operations_count</code> »</a> and <a href="/api/config#large-queue-max-active-operations-count"><code>large_queue_max_active_operations_count</code> »</a> client configuration parameters, used to limit parallelism when downloading multiple files in parallel as described in the <a href="/api/files#downloading-files">docs »</a>.  </p>
+<p>Added the <a href="/api/config#small-queue-max-active-operations-count"><code>small_queue_max_active_operations_count</code> »</a> and <a href="/api/config#large-queue-max-active-operations-count"><code>large_queue_max_active_operations_count</code> »</a> client configuration parameters, used to limit parallelism when downloading multiple files in parallel as described in the <a href="/api/files#downloading-files">docs »</a>.</p>
 <p>The <a href="/api/errors#error-database">RPC error database »</a> was also updated, and a small clarification for open-source push notification standards like UnifiedPush was added to the <a href="/api/push-updates">push notifications documentation »</a>.</p>
 <h4><a class="anchor" href="#schema-changes" id="schema-changes" name="schema-changes"><i class="anchor-icon"></i></a>Schema changes</h4>
 <h5><a class="anchor" href="#new-methods" id="new-methods" name="new-methods"><i class="anchor-icon"></i></a>New Methods</h5>

data/web/corefork.telegram.org/method/auth.resendCode

@@ -95,6 +95,11 @@
 <tbody>
 <tr>
 <td>400</td>
+<td>PHONE_CODE_EMPTY</td>
+<td>phone_code is missing.</td>
+</tr>
+<tr>
+<td>400</td>
 <td>PHONE_CODE_EXPIRED</td>
 <td>The phone code you provided has expired.</td>
 </tr>

data/web/corefork.telegram.org/method/chatlists.exportChatlistInvite

@@ -109,6 +109,11 @@
 </tr>
 <tr>
 <td>400</td>
+<td>INVITES_TOO_MUCH</td>
+<td>The maximum number of per-folder invites specified by the <code>chatlist_invites_limit_default</code>/<code>chatlist_invites_limit_premium</code> <a href="/api/config#chatlist-invites-limit-default">client configuration parameters »</a> was reached.</td>
+</tr>
+<tr>
+<td>400</td>
 <td>PEERS_LIST_EMPTY</td>
 <td>The specified list of peers is empty.</td>
 </tr>
@@ -120,7 +125,9 @@
 <h4><a class="anchor" href="#folders" id="folders" name="folders"><i class="anchor-icon"></i></a><a href="/api/folders">Folders</a></h4>
 <p>Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.</p>
 <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>
+<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>
+<h4><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a><a href="/api/config">Client configuration</a></h4>
+<p>The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.</p></div>
   
 </div>
           

data/web/corefork.telegram.org/method/messages.forwardMessages

@@ -240,6 +240,11 @@
 </tr>
 <tr>
 <td>403</td>
+<td>CHAT_SEND_VOICES_FORBIDDEN</td>
+<td>You can't send voice recordings in this chat.</td>
+</tr>
+<tr>
+<td>403</td>
 <td>CHAT_WRITE_FORBIDDEN</td>
 <td>You can't write in this chat.</td>
 </tr>