aboutsummaryrefslogtreecommitdiff
path: root/docs/API
diff options
context:
space:
mode:
authorEgor Kislitsyn <egor@kislitsyn.com>2020-05-19 21:52:26 +0400
committerEgor Kislitsyn <egor@kislitsyn.com>2020-05-20 15:15:13 +0400
commit490a3a34b63fa10e9151e9a385920c10615a1a3c (patch)
tree6bd84e38cbab0437db167b4284bcbc270beb1cd0 /docs/API
parent94ba5a780212920a1d4b303c3523f66ca0147a67 (diff)
downloadpleroma-490a3a34b63fa10e9151e9a385920c10615a1a3c.tar.gz
Add OpenAPI spec for PleromaAPI.PleromaAPIController
Diffstat (limited to 'docs/API')
-rw-r--r--docs/API/pleroma_api.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/API/pleroma_api.md b/docs/API/pleroma_api.md
index 867f59919..d6dbafc06 100644
--- a/docs/API/pleroma_api.md
+++ b/docs/API/pleroma_api.md
@@ -358,7 +358,7 @@ The status posting endpoint takes an additional parameter, `in_reply_to_conversa
* `recipients`: A list of ids of users that should receive posts to this conversation. This will replace the current list of recipients, so submit the full list. The owner of owner of the conversation will always be part of the set of recipients, though.
* Response: JSON, statuses (200 - healthy, 503 unhealthy)
-## `GET /api/v1/pleroma/conversations/read`
+## `POST /api/v1/pleroma/conversations/read`
### Marks all user's conversations as read.
* Method `POST`
* Authentication: required
@@ -536,7 +536,7 @@ Emoji reactions work a lot like favourites do. They make it possible to react to
```
## `GET /api/v1/pleroma/statuses/:id/reactions/:emoji`
-### Get an object of emoji to account mappings with accounts that reacted to the post for a specific emoji`
+### Get an object of emoji to account mappings with accounts that reacted to the post for a specific emoji
* Method: `GET`
* Authentication: optional
* Params: None