diff options
| author | rinpatch <rinpatch@sdf.org> | 2020-03-13 18:58:22 +0000 |
|---|---|---|
| committer | rinpatch <rinpatch@sdf.org> | 2020-03-13 18:58:22 +0000 |
| commit | 4db88242e52b00dc350b9a2ecaaea5b7ea7b21c6 (patch) | |
| tree | 6c7e6dee6abd7909dad06e5b97f7babcce12fd58 /docs/API/pleroma_api.md | |
| parent | 994ac4357cb6c3f64a8889d3a98f9a3adbd37010 (diff) | |
| parent | deb5f5c40e638472ca5a01370ad127fc4c437150 (diff) | |
| download | pleroma-4db88242e52b00dc350b9a2ecaaea5b7ea7b21c6.tar.gz | |
Merge branch 'docs/direct_conversation_id' into 'develop'
pleroma_api.md: direct_conversation_id vs. conversation_id
See merge request pleroma/pleroma!2263
Diffstat (limited to 'docs/API/pleroma_api.md')
| -rw-r--r-- | docs/API/pleroma_api.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/API/pleroma_api.md b/docs/API/pleroma_api.md index 761d5c69c..12e63ef9f 100644 --- a/docs/API/pleroma_api.md +++ b/docs/API/pleroma_api.md @@ -288,10 +288,11 @@ Pleroma Conversations have the same general structure that Mastodon Conversation 2. Pleroma Conversations statuses can be requested by Conversation id. 3. Pleroma Conversations can be replied to. -Conversations have the additional field "recipients" under the "pleroma" key. This holds a list of all the accounts that will receive a message in this conversation. +Conversations have the additional field `recipients` under the `pleroma` key. This holds a list of all the accounts that will receive a message in this conversation. The status posting endpoint takes an additional parameter, `in_reply_to_conversation_id`, which, when set, will set the visiblity to direct and address only the people who are the recipients of that Conversation. +⚠ Conversation IDs can be found in direct messages with the `pleroma.direct_conversation_id` key, do not confuse it with `pleroma.conversation_id`. ## `GET /api/v1/pleroma/conversations/:id/statuses` ### Timeline for a given conversation |