David Robertson f3f0ab10fe Move scripts directory inside synapse, exposing as setuptools entry_points (#12118) | há 2 anos atrás | |
---|---|---|
.. | ||
README.md | f3f0ab10fe Move scripts directory inside synapse, exposing as setuptools entry_points (#12118) | há 2 anos atrás |
background_updates.md | ea20937084 Add an admin API to run background jobs. (#11352) | há 3 anos atrás |
federation.md | 6a72c910f1 Add admin API to get a list of federated rooms (#11658) | há 2 anos atrás |
registration_tokens.md | 013e0f9cae Update doc of the allowed characters for registration tokens (#11093) | há 3 anos atrás |
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.:
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
command. This is a script that is distributed as part of synapse. It is possibly
already on your $PATH
depending on how Synapse was installed.
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
, you will need to authenticate each request to an Admin API endpoint by
providing the token as either a query parameter or a request header. To add it as a request header in cURL:
curl --header "Authorization: Bearer <access_token>" <the_rest_of_your_API_request>
For more details on access tokens in Matrix, please refer to the complete matrix spec documentation.