Commit 7bb13e4b authored by Eugen Rochko's avatar Eugen Rochko

Add API permissions page

parent 17c9765f
Pipeline #255 passed with stages
in 16 seconds
......@@ -3,5 +3,5 @@ title: Entities
parent: api
weight: 2
weight: 3
title: Permissions
parent: api
weight: 2
The API is divided up into access scopes:
|Scope|Parent(s)|Added in|
|`write:blocks`|`write`, `follow`|2.4.3|
|`write:follows`|`write`, `follow`|2.4.3|
|`write:mutes`|`write`, `follow`|2.4.3|
|`read:blocks`|`read`, `follow`|2.4.3|
|`read:follows`|`read`, `follow`|2.4.3|
|`read:mutes`|`read`, `follow`|2.4.3|
The scopes are hierarchical, i.e. if you have access to `read`, you automatically have access to `read:accounts`. **It is recommended that you request as little as possible for your application.**
Multiple scopes can be requested at the same time: During app creation with the `scopes` param, and during the authorization phase with the `scope` query param (space-separate the scopes).
> **Note:** Mind the `scope` vs `scopes` difference. This is because `scope` is a standard OAuth parameter name, so it is used in the OAuth methods. Mastodon's own REST API uses the more appropriate `scopes`.
If you do not specify a `scope` in your authorization request, or a `scopes` in your app creation request, the resulting access token / app will default to `read` access.
The set of scopes saved during app creation must include all the scopes that you will request in the authorization request, otherwise authorization will fail.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment