Service prefix: internal/services/messages/v1/

There is two collections in the new message implementation:

• Message thread feed collection
• User bookmarks collection

Threads and messages

Create a thread

• POST /companies/{company_id}/threads Create a new thread (pass a message to create the thread and add message as child to its own thread)
• POST /companies/{company_id}/threads/{thread_id} Edit thread participant

Messages collection (in thread only)

• POST /companies/{company_id}/threads/{thread_id}/messages Create a new message in a thread

• POST /companies/{company_id}/threads/{thread_id}/messages/{message_id} Edit a message in a thread

• GET /companies/{company_id}/threads/{thread_id}/messages/{message_id} Get a single message

• GET /companies/{company_id}/threads/{thread_id}/messages Get list of messages in a thread

• POST /companies/{company_id}/threads/{thread_id}/messages/{message_id}/reaction React to a message

• POST /companies/{company_id}/threads/{thread_id}/messages/{message_id}/bookmark Bookmark a message

• POST /companies/{company_id}/threads/{thread_id}/messages/{message_id}/pin Pin a message

• POST /companies/{company_id}/threads/{thread_id}/messages/{message_id}/delete Delete a message

Get list of messages from multiple views

Messages can be retrieved from thread but also for a lot of places in Twake. Every endpoint follows a common main schema to paginate and limit requests, response is also formatted and the same for all routes.