logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: 6c0e07b8bdc85f757e2d1e6993e64f2e1540deb6
parent: 5300cd56e55829e5f6ce471e4684a484baa1eb87
Author: rinpatch <rinpatch@sdf.org>
Date:   Sun, 21 Apr 2019 19:57:52 +0000

Merge branch 'docs/posting_formatted' into 'develop'

differences_in_mastoapi_responses.md: `content_type` parameter of post submission

See merge request pleroma/pleroma!1081

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 @@ -58,3 +58,4 @@ Has these additional fields under the `pleroma` object: Additional parameters can be added to the JSON body/Form data: - `preview`: boolean, if set to `true` the post won't be actually posted, but the status entitiy would still be rendered back. This could be useful for previewing rich text/custom emoji, for example. +- `content_type`: string, contain the MIME type of the status, it is transformed into HTML by the backend. You can get the list of the supported MIME types with the nodeinfo endpoint.