Merge branch 'fix/docs-markdown' into 'develop'
Fix formatting in documentation See merge request pleroma/pleroma!2348
This commit is contained in:
commit
8444e7ee96
|
@ -164,6 +164,7 @@ Additional parameters can be added to the JSON body/Form data:
|
||||||
- `actor_type` - the type of this account.
|
- `actor_type` - the type of this account.
|
||||||
|
|
||||||
### Pleroma Settings Store
|
### Pleroma Settings Store
|
||||||
|
|
||||||
Pleroma has mechanism that allows frontends to save blobs of json for each user on the backend. This can be used to save frontend-specific settings for a user that the backend does not need to know about.
|
Pleroma has mechanism that allows frontends to save blobs of json for each user on the backend. This can be used to save frontend-specific settings for a user that the backend does not need to know about.
|
||||||
|
|
||||||
The parameter should have a form of `{frontend_name: {...}}`, with `frontend_name` identifying your type of client, e.g. `pleroma_fe`. It will overwrite everything under this property, but will not overwrite other frontend's settings.
|
The parameter should have a form of `{frontend_name: {...}}`, with `frontend_name` identifying your type of client, e.g. `pleroma_fe`. It will overwrite everything under this property, but will not overwrite other frontend's settings.
|
||||||
|
@ -172,17 +173,20 @@ This information is returned in the `verify_credentials` endpoint.
|
||||||
|
|
||||||
## Authentication
|
## Authentication
|
||||||
|
|
||||||
*Pleroma supports refreshing tokens.
|
*Pleroma supports refreshing tokens.*
|
||||||
|
|
||||||
`POST /oauth/token`
|
`POST /oauth/token`
|
||||||
Post here request with grant_type=refresh_token to obtain new access token. Returns an access token.
|
|
||||||
|
Post here request with `grant_type=refresh_token` to obtain new access token. Returns an access token.
|
||||||
|
|
||||||
## Account Registration
|
## Account Registration
|
||||||
|
|
||||||
`POST /api/v1/accounts`
|
`POST /api/v1/accounts`
|
||||||
|
|
||||||
Has theses additional parameters (which are the same as in Pleroma-API):
|
Has theses additional parameters (which are the same as in Pleroma-API):
|
||||||
* `fullname`: optional
|
|
||||||
* `bio`: optional
|
- `fullname`: optional
|
||||||
* `captcha_solution`: optional, contains provider-specific captcha solution,
|
- `bio`: optional
|
||||||
* `captcha_token`: optional, contains provider-specific captcha token
|
- `captcha_solution`: optional, contains provider-specific captcha solution,
|
||||||
* `token`: invite token required when the registerations aren't public.
|
- `captcha_token`: optional, contains provider-specific captcha token
|
||||||
|
- `token`: invite token required when the registrations aren't public.
|
||||||
|
|
Loading…
Reference in New Issue