logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: 1e2bb450dbff1b8c0eee5d131992ec0a9e57c743
parent: af5fef1f228a1781d7d9cad490d3b3a783389f5e
Author: rinpatch <rinpatch@sdf.org>
Date:   Mon,  9 Dec 2019 10:16:26 +0000

Merge branch 'move-api-docs' into 'develop'

Document `with_move` parameter of the notification API

See merge request pleroma/pleroma!2047

Diffstat:

Mdocs/API/differences_in_mastoapi_responses.md1+
1 file changed, 1 insertion(+), 0 deletions(-)

diff --git a/docs/API/differences_in_mastoapi_responses.md b/docs/API/differences_in_mastoapi_responses.md @@ -103,6 +103,7 @@ The `type` value is `move`. Has an additional field: Accepts additional parameters: - `exclude_visibilities`: will exclude the notifications for activities with the given visibilities. The parameter accepts an array of visibility types (`public`, `unlisted`, `private`, `direct`). Usage example: `GET /api/v1/notifications?exclude_visibilities[]=direct&exclude_visibilities[]=private`. +- `with_move`: boolean, when set to `true` will include Move notifications. `false` by default. ## POST `/api/v1/statuses`