Core API

To monitor the "seen" status of messages, api clients currently need to implement a polling strategy. Adding a seen event to enable web-hook integration, will limit api usage and improve state change detection.

As a developer I sometimes need to see the source inbox of a move (i.e. see which inbox a conversation was moved from in addition to the inbox it was moved to.

Hi, We are implementing a requirement to correlate Outlook emails to Front messages. There is one common ID in the source message (internetMessageId in Outlook and message-id in Front). We need to have the ability to fetch a message using the Fron...

Per this answer the only way to retrieve all of the recipients of a conversation is to iterate through all messages in the conversation and manually pull out - and de-duplicate - the recipients from each message. This is both unnecessarily complic...

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.