synapse

History

Quentin Gliech 41b9def9f2 Add a new admin API to create a new device for a user. (#15611 ) This allows an external service (e.g. the matrix-authentication-service) to create devices for users.		2023-05-17 14:39:06 +00:00
..
account_validity.md	Fix broken links in the Synapse documentation. (#14744 )	2023-01-05 18:18:00 +00:00
event_reports.md	Admin API endpoint to delete a reported event (#15116 )	2023-02-28 12:09:10 +00:00
experimental_features.md	Remove references to supporting per-user flag for msc2654 (#15522 )	2023-05-02 14:21:36 -07:00
media_admin_api.md	Respond correctly to unknown methods on known endpoints (#14605 )	2023-02-09 13:04:24 -05:00
purge_history_api.md	Fix broken links in the Synapse documentation. (#14744 )	2023-01-05 18:18:00 +00:00
README.rst	Fix broken links in documentation (#10180 )	2021-06-16 13:15:52 +01:00
register_api.md	Fix the cross-link from register admin API to config docs. (#13870 )	2022-09-22 09:11:50 -04:00
room_membership.md	Fix broken links in the Synapse documentation. (#14744 )	2023-01-05 18:18:00 +00:00
rooms.md	Fix broken links in the Synapse documentation. (#14744 )	2023-01-05 18:18:00 +00:00
server_notices.md	Docs: Use something other than the document name to describe a page (#10399 )	2021-07-15 12:47:55 +01:00
statistics.md	Fix documented path to largest rooms statistics endpoint. (#15560 )	2023-05-10 13:00:27 +00:00
user_admin_api.md	Add a new admin API to create a new device for a user. (#15611 )	2023-05-17 14:39:06 +00:00
version_api.md	Drop support for and remove references to EOL Python 3.6 (#11683 )	2022-01-21 14:23:26 -08:00

README.rst

Admin APIs
==========

**Note**: The latest documentation can be viewed `here <https://matrix-org.github.io/synapse>`_.
See `docs/README.md <../README.md>`_ for more information.

**Please update links to point to the website instead.** Existing files in this directory
are preserved to maintain historical links, but may be moved in the future.

This directory includes documentation for the various synapse specific admin
APIs available. Updates to the existing Admin API documentation should still
be made to these files, but any new documentation files should instead be placed under
`docs/usage/administration/admin_api <../usage/administration/admin_api>`_.