Current Use Case:

There is always a need for the client to synchronize messages from time to time via calling the API; however, the current process requires sequential API calls to retrieve information:

Get Conversations

Get messages in conversation

Get contact

If the /api/conversation/message/search endpoint could support parameters for 'message start time' and 'message end time', and return conversation, message, and contact information in a single response, it would streamline the process of retrieving conversation messages via the API.