diff options
| author | Haelwenn (lanodan) Monnier <contact@hacktivis.me> | 2020-03-02 04:01:37 +0100 |
|---|---|---|
| committer | rinpatch <rinpatch@sdf.org> | 2020-03-15 17:00:30 +0300 |
| commit | f9c43a4d9d407ed0e48bd7bbc843c57ab2dbddeb (patch) | |
| tree | b18dc10315692f125c18d32fb2a3fe64147beff6 | |
| parent | ffd636f109d437ff49f38d5fabeb1109566f117b (diff) | |
| download | pleroma-f9c43a4d9d407ed0e48bd7bbc843c57ab2dbddeb.tar.gz | |
pleroma_api.md: direct_conversation_id vs. conversation_id
Related: https://git.pleroma.social/pleroma/pleroma/issues/1594
| -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 |