Core API

I'm building an integration with an external SMS provider, which supports group conversations. Right now, Front's Receive custom messages and Sync inbound message API endpoints do not allow me to receive a message from a sender which was addressed...

Customer requesting the ability to send an existing draft via API. They are requesting the ability to provide a message ID of the draft in a response that will initiate the sending of the message.

add a parameter in the contact list request to search with the emails

Rule data sets are currently manually maintained or limited to 500 rows for a CSV import. API access to manage this would give an avenue to maintain this in a non manual way and reduces chances of errors occurring

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.

the green, orange and red dot should be accessible via the api on the teammate object

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?