`POST /api/v1/pleroma/chats/by-account-id/{account_id}`
-The account id is the normal FlakeId of the usre
-
+The account id is the normal FlakeId of the user
```
POST /api/v1/pleroma/chats/by-account-id/someflakeid
```
+If you already have the id of a chat, you can also use
+
+```
+GET /api/v1/pleroma/chats/:id
+```
+
There will only ever be ONE Chat for you and a given recipient, so this call
will return the same Chat if you already have one with that user.
},
"id" : "1",
"unread" : 2,
- "last_message" : {...} // The last message in that chat
+ "last_message" : {...}, // The last message in that chat
+ "updated_at": "2020-04-21T15:11:46.000Z"
}
```
...
},
"id" : "1",
- "unread" : 0
+ "unread" : 0,
+ "updated_at": "2020-04-21T15:11:46.000Z"
}
```
},
"id" : "1",
"unread" : 2,
- "last_message" : {...} // The last message in that chat
+ "last_message" : {...}, // The last message in that chat
+ "updated_at": "2020-04-21T15:11:46.000Z"
}
]
```
`POST /api/v1/pleroma/chats/{id}/messages`
Parameters:
-- content: The text content of the message
+- content: The text content of the message. Optional if media is attached.
- media_id: The id of an upload that will be attached to the message.
-Currently, no formatting beyond basic escaping and emoji is implemented, as well as no
-attachments. This will most probably change.
+Currently, no formatting beyond basic escaping and emoji is implemented.
Returned data:
}
```
+### Deleting a chat message
+
+Deleting a chat message for given Chat id works like this:
+
+`DELETE /api/v1/pleroma/chats/{chat_id}/messages/{message_id}`
+
+Returned data is the deleted message.
+
### Notifications
There's a new `pleroma:chat_mention` notification, which has this form: