mirror of https://github.com/watcha-fr/synapse
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ThibF
0085dc5abc
|
4 years ago | |
---|---|---|
.. | ||
README.rst | 5 years ago | |
account_validity.rst | 6 years ago | |
delete_group.md | 5 years ago | |
event_reports.md | 4 years ago | |
media_admin_api.md | 4 years ago | |
purge_history_api.rst | 5 years ago | |
purge_room.md | 4 years ago | |
register_api.rst | 4 years ago | |
room_membership.md | 5 years ago | |
rooms.md | 4 years ago | |
server_notices.md | 6 years ago | |
shutdown_room.md | 4 years ago | |
statistics.md | 4 years ago | |
user_admin_api.rst | 4 years ago | |
version_api.rst | 6 years ago |
README.rst
Admin APIs
==========
This directory includes documentation for the various synapse specific admin
APIs available.
Authenticating as a server admin
--------------------------------
Many of the API calls in the admin api will require an `access_token` for a
server admin. (Note that a server admin is distinct from a room admin.)
A user can be marked as a server admin by updating the database directly, e.g.:
.. code-block:: sql
UPDATE users SET admin = 1 WHERE name = '@foo:bar.com';
A new server admin user can also be created using the
``register_new_matrix_user`` script.
Finding your user's `access_token` is client-dependent, but will usually be shown in the client's settings.
Once you have your `access_token`, to include it in a request, the best option is to add the token to a request header:
``curl --header "Authorization: Bearer <access_token>" <the_rest_of_your_API_request>``
Fore more details, please refer to the complete `matrix spec documentation <https://matrix.org/docs/spec/client_server/r0.5.0#using-access-tokens>`_.