From d07f6856fecde7d0e397d8dc614c697d24dd2d40 Mon Sep 17 00:00:00 2001
From: reivilibre account_validity
) in Synapse's configuration.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
This API extends the validity of an account by as much time as configured in the
period
parameter from the account_validity
configuration.
This API returns information about reported events.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
The api is:
GET /_synapse/admin/v1/event_reports?from=0&limit=10
diff --git a/develop/admin_api/media_admin_api.html b/develop/admin_api/media_admin_api.html
index d1005372de..8c8aa1830d 100644
--- a/develop/admin_api/media_admin_api.html
+++ b/develop/admin_api/media_admin_api.html
@@ -151,7 +151,7 @@
Details about the format of the media_id
and storage of the media in the file system
are documented under media repository.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
This API gets a list of known media in a room. However, it only shows media from unencrypted events or rooms.
diff --git a/develop/admin_api/purge_history_api.html b/develop/admin_api/purge_history_api.html index bec236320b..9a61ccad38 100644 --- a/develop/admin_api/purge_history_api.html +++ b/develop/admin_api/purge_history_api.html @@ -155,7 +155,7 @@ paginate further back in the room from the point being purged from.Note that Synapse requires at least one message in each room, so it will never delete the last message in a room.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
The API is:
POST /_synapse/admin/v1/purge_history/<room_id>[/<event_id>]
diff --git a/develop/admin_api/room_membership.html b/develop/admin_api/room_membership.html
index ac593aca69..718d2ce478 100644
--- a/develop/admin_api/room_membership.html
+++ b/develop/admin_api/room_membership.html
@@ -152,7 +152,7 @@ to a room with a given room_id_or_alias
. You can only modify the me
local users. The server administrator must be in the room and have permission to
invite users.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
The following parameters are available:
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
Parameters
The following query parameters are available:
null
.
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.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
This endpoint mirrors the Matrix Spec defined Messages API.
The API is:
GET /_synapse/admin/v1/rooms/<room_id>/messages
diff --git a/develop/admin_api/statistics.html b/develop/admin_api/statistics.html
index 68dc66f51e..52b69dfa25 100644
--- a/develop/admin_api/statistics.html
+++ b/develop/admin_api/statistics.html
@@ -150,7 +150,7 @@
Returns information about all local media usage of users. Gives the
possibility to filter them by time and user.
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
+for a server admin: see Admin API.
The API is:
GET /_synapse/admin/v1/statistics/users/media
diff --git a/develop/admin_api/user_admin_api.html b/develop/admin_api/user_admin_api.html
index 5f4cc6c351..8fc74d7844 100644
--- a/develop/admin_api/user_admin_api.html
+++ b/develop/admin_api/user_admin_api.html
@@ -148,7 +148,7 @@
User Admin API
To use it, you will need to authenticate by providing an access_token
-for a server admin: see Admin API.
+for a server admin: see Admin API.
Query User Account
This API returns information about a specific user account.
The api is:
--
cgit 1.5.1