diff --git a/data/web/corefork.telegram.org/api/links.html b/data/web/corefork.telegram.org/api/links.html
index 8bfe76989b..30db31d77b 100644
--- a/data/web/corefork.telegram.org/api/links.html
+++ b/data/web/corefork.telegram.org/api/links.html
@@ -107,6 +107,28 @@
 </tbody>
 </table>
 <p>Note that <a href="#message-links">chat invite links</a> have the same syntax, but <code>&lt;phone_number&gt;</code> is not a valid phone number.  </p>
+<h3><a class="anchor" href="#user-id-links" id="user-id-links" name="user-id-links"><i class="anchor-icon"></i></a>User ID links</h3>
+<p>Used to link to users by their user ID: such links should only be parsed when encountered in inline or reply keyboard buttons.<br>
+They are useful when linking to users without a username, but of course they will work only if the client has the user's access hash already stored in its database.  </p>
+<p><code>tg:</code> syntax:</p>
+<pre><code>tg://user?id=&lt;user_id&gt;</code></pre>
+<p>Parameters:</p>
+<table class="table">
+<thead>
+<tr>
+<th>Name</th>
+<th style="text-align: center;">Optional</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>user_id</code></td>
+<td style="text-align: center;">Required</td>
+<td>User ID</td>
+</tr>
+</tbody>
+</table>
 <h3><a class="anchor" href="#chat-invite-links" id="chat-invite-links" name="chat-invite-links"><i class="anchor-icon"></i></a>Chat invite links</h3>
 <p>Used to invite users to private groups and channels, see <a href="/api/invites#invite-links">here for more info on how to generate such links »</a>.  </p>
 <p><code>t.me</code> syntax:</p>