aboutsummaryrefslogtreecommitdiff
path: root/docs/api
diff options
context:
space:
mode:
authorrinpatch <rinpatch@sdf.org>2019-04-21 19:57:52 +0000
committerrinpatch <rinpatch@sdf.org>2019-04-21 19:57:52 +0000
commit6c0e07b8bdc85f757e2d1e6993e64f2e1540deb6 (patch)
tree905db7086b2caa86d5850ae786d3cfcdb6561269 /docs/api
parent5300cd56e55829e5f6ce471e4684a484baa1eb87 (diff)
parentd0863197330d3d0ed12c884b651599e60da5467d (diff)
downloadpleroma-6c0e07b8bdc85f757e2d1e6993e64f2e1540deb6.tar.gz
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 (limited to 'docs/api')
-rw-r--r--docs/api/differences_in_mastoapi_responses.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/api/differences_in_mastoapi_responses.md b/docs/api/differences_in_mastoapi_responses.md
index ed3fd9b67..63644fc56 100644
--- 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.