deploy: 4eb2f4e02b

develop/admin_api/account_validity.html

@@ -151,7 +151,7 @@
 use it, you must enable the account validity feature (under
 <code>account_validity</code>) in Synapse's configuration.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <h2 id="renew-account"><a class="header" href="#renew-account">Renew account</a></h2>
 <p>This API extends the validity of an account by as much time as configured in the
 <code>period</code> parameter from the <code>account_validity</code> configuration.</p>

develop/admin_api/event_reports.html

@@ -149,7 +149,7 @@
                         <h1 id="show-reported-events"><a class="header" href="#show-reported-events">Show reported events</a></h1>
 <p>This API returns information about reported events.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <p>The api is:</p>
 <pre><code>GET /_synapse/admin/v1/event_reports?from=0&amp;limit=10
 </code></pre>

develop/admin_api/media_admin_api.html

@@ -151,7 +151,7 @@
 <p>Details about the format of the <code>media_id</code> and storage of the media in the file system
 are documented under <a href="../media_repository.html">media repository</a>.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <h2 id="list-all-media-in-a-room"><a class="header" href="#list-all-media-in-a-room">List all media in a room</a></h2>
 <p>This API gets a list of known media in a room.
 However, it only shows media from unencrypted events or rooms.</p>

develop/admin_api/purge_history_api.html

@@ -155,7 +155,7 @@ paginate further back in the room from the point being purged from.</p>
 <p>Note that Synapse requires at least one message in each room, so it will never
 delete the last message in a room.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <p>The API is:</p>
 <pre><code>POST /_synapse/admin/v1/purge_history/&lt;room_id&gt;[/&lt;event_id&gt;]
 </code></pre>

develop/admin_api/room_membership.html

@@ -152,7 +152,7 @@ to a room with a given <code>room_id_or_alias</code>. You can only modify the me
 local users. The server administrator must be in the room and have permission to
 invite users.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <h2 id="parameters"><a class="header" href="#parameters">Parameters</a></h2>
 <p>The following parameters are available:</p>
 <ul>

develop/admin_api/rooms.html

@@ -151,7 +151,7 @@
 server. There are various parameters available that allow for filtering and
 sorting the returned list. This API supports pagination.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <p><strong>Parameters</strong></p>
 <p>The following query parameters are available:</p>
 <ul>
@@ -509,7 +509,7 @@ If the room does not define a type, the value will be <code>null</code>.</li>
 sent to a room in a given timeframe. There are various parameters available
 that allow for filtering and ordering the returned list. This API supports pagination.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <p>This endpoint mirrors the <a href="https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3roomsroomidmessages">Matrix Spec defined Messages API</a>.</p>
 <p>The API is:</p>
 <pre><code>GET /_synapse/admin/v1/rooms/&lt;room_id&gt;/messages

develop/admin_api/statistics.html

@@ -150,7 +150,7 @@
 <p>Returns information about all local media usage of users. Gives the
 possibility to filter them by time and user.</p>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <p>The API is:</p>
 <pre><code>GET /_synapse/admin/v1/statistics/users/media
 </code></pre>

develop/admin_api/user_admin_api.html

@@ -148,7 +148,7 @@
 
                         <h1 id="user-admin-api"><a class="header" href="#user-admin-api">User Admin API</a></h1>
 <p>To use it, you will need to authenticate by providing an <code>access_token</code>
-for a server admin: see <a href="../usage/administration/admin_api">Admin API</a>.</p>
+for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
 <h2 id="query-user-account"><a class="header" href="#query-user-account">Query User Account</a></h2>
 <p>This API returns information about a specific user account.</p>
 <p>The api is:</p>