Core API

Paginate GET /channels results, and enable filtering by type

Right now Front requires a channel_id to be supplied on calls to Create Draft endpoints - this is not required on send reply endpoints. Could we have the API select a default channel when the channel_id param is not supplied?

Hi, Using the API to create a new inbox/team inbox. It would be so helpful to enable the ability to change the color in the settings of the item. Similar to what is already enabled when creating a tag, using the highlight attribute.

Ability to split a conversation into multiple converastions via API.

The search conversation endpoint has limited date-searching parameters. 'Before' and 'After' are only able to filter by a conversation's first message. There is a need to search for Conversations by the most recent message timestamp.

Support the ability to move a Message or Messages to a new conversation via the API. Suggested implementation to could be: // This example moves messages msg_10 and msg_11 out of conversation cnv_3 to their own new conversation. PATCH /conversatio...

Ability to send notifications to a user even when the plugin is not currently open.

you should put the conversation id in the response of the create draft endpoint (and other endpoint like create message) directly. I had to extract it out of the url `_links.related.conversation`. It would have been better to extract it out of the...

Instead of requiring that a user hash be computed based on HMAC-SHA256, expose some API devs can call to automatically generate this based when the verifications ecret is passed in.