Hello,
We have an active integration for pushing messages into Front and we are trying to wrap up a webhook to receive incoming messages from Front. We have a few questions.
1. The Authorization.Id that is coming through in the request doesn't mean anything to us at the moment. It’s not clear how this is created or where it comes from. We did see; however, that the Payload.Conversation.Assignee.Id is the same value we are already storing on our side when setting up the Integration to send messages. This looks like an easy way for us to identify who the message is for. Will this value always be populated when we're getting messages in the webhook or is it possible to get a message without an Assignee?
2. The attachment object in the payload does not contain any byte or steam data but it does have a URL. When we go to this URL we get an unauthorized response. Is there another API endpoint we should be using to access Front Attachments we receive in the Incoming Message payload?
3. Part of our normal email process when reading from other mailboxes is that the user can apply a post processing action. This would typically be marking the message as read/seen, archiving it, or deleting it. Can you point us to the endpoints that would allow us to perform these actions against the message in Front? We are assuming we would use the Payload.Id or the Payload.Target.Data.Id for this?
Best answer by jason
View original