Developer Q&A

I’m attempting to get conversations for the last day and see that the “List Conversations” returns conversations sorted by most recent first. But there’s no great way of validating recency. I’ve resorted to pulling all messages for each conversation and checking to see that at least 1 message was created within the last day.Seeing as the List Conversations endpoint is doing some sort of server-side sorting with an updated_at property, is it possible to expose that so I can key off of it at as well? This would also be helpful when searching conversations too.Or if there’s some other way of getting this information please let me know. Thanks in advance!

Hello; In an effort to not miss clients contacting salespeople who have departed our company, I am modifying my offboarding script to add the user’s email to an ‘inactive’ inbox that only managers have access to.  I can successfully convert the Google user into a group and add it to the inbox, but if the user had their email set up in Front I get a “duplicate channel” error and have to go into the UI to manually delete the user and their private inbox.  Is there a way to manage this offboarding flow outside of the the UI? 

Is there a way to fetch/list only intercom conversations using the conversation api ?

Hello,I would like to know if when refreshing an access token (point 4. here : https://dev.frontapp.com/docs/oauth), the previous token is disabled even if his 1 hour lifetime is still ongoing, so there is only one token that is being replaced each time we do a refresh call to your API?Or the previous token is still valid till the end of his 1 hour lifetime ?Thank you in advance for your answer.

We would like to start measuring our shared inbox usage compliance, and we want to get insights from an analytics standpoint (volume for instance). We want to look into the ratio of messages one sends (either through Shared Inboxes or Individual Inboxes).

I am working on using the Front API to get some data we need into our BI Tool to analyze it, but I have a few questions. Basically, I need to get from the API the same data I get if I go to Analytics and get a Message Export. I wasn’t quite able to exactly that in the API so I just need a little direction on where to find it.We will also need the export to contain messages from personal inboxes. 

We are currently in the process of building an integration with Front. For our use case, we found the `List Events` API here, to be suitable. We want to only list archive events in a certain time window, and for that, we have tried using the `q` parameter, as mentioned in the document, but it doesn't seem to work, the response always contains all the events, irrespective of the query we use. Attaching a few curls we have tried curl --request GET      --url 'https://api2.frontapp.com/events?q=types%3Aarchive'      --header 'Accept: application/json'      --header 'Authorization: Bearer TOKEN'curl --request GET      --url 'https://api2.frontapp.com/events?q=after%3A1651470943.000'      --header 'Accept: application/json'      --header 'Authorization: Bearer TOKEN' Combining the before and after parameters would also be helpful.Looking forward to your help on this.

We utilize our own plugin integration to pull customer data on each inbound data for our sales reps to see.We capture the customer's email address using "emailaddress = context.conversation.recipient.handle;"This is working fine except for our contact forms on our sites. These all send and are properly signed from noreply@domain.com. So we are unable to lookup the customer email in our system... The customer email is set in the reply-to field of the email. Our plugin works as expected as soon as the sales rep hits reply - the front conversation recipient changes at that point to the 'reply-to' address.How can we pull the reply-to address in our plugin from the initial load before hitting the reply button??

We could not find raw data about the CSAT but only percentages. We need to recover the data of our customers in a raw format… We are used to working in that way with other CRM solutions.We need the same with front. Do you have some guideline or examples as how to recover CSAT raw data?

Hi, I am trying to use Front's api to send a reply to a conversation, but am receiving the error "body did not satisfy requirements" I am using webhooks via Zapier to POST to the API. I've included the text below of the inputs- I tried to match everything as closely as possible to Front's documentation. Could you provide any advice into troubleshooting this error? URLhttps://api2.frontapp.com/conversations/cnv_12345/messagesPayload TypejsonDatato"person@example.com"options{"archive": true}signature_id"sig_12345"sender_name"Dale"channel_id"cha_12345"body"test"subject"test message"Wrap Request In ArrayfalseFileUnflattentrueBasic AuthHeadersAcceptapplication/jsonAuthorizationBearer xxxxxxxxxContent-Typeapplication/json 

We've been running into an issue implementing the event sync from Front. While the webhook is working correctly, the alternative sync we wrote using the Events API seems not to respect the after filter in queries. When we make a request to e.g. https://companyDomain.api.frontapp.com/events?q=after:1652647350.45151, rather than getting only very recent events (that was basically the current UTC timestamp when I made the request) we get a paginated response with hundreds of thousands of results. Is this a bug on the Front end, or is there a different syntax we should use to query events after a certain time?

We’re hoping to send calendar invites through Front messages. Historically we’ve included the calendar invite as inline to the message using the multipart/alternative property where the invite renders as part of the message, but not sure this is available through the Front API.

Currently we have a rule for our team that when triggered sends an auto reply to the sender. We have changed something about our setup where this rule is no longer working properly.  I am hoping to get some assistanceHere is the specific use case: "A client requests a quote, the php backend sends an email to one of our addresses with the requested quote details. A front rule is triggered to send an auto-reply to the reply to address." Up until now the server for our website has been using phpmailer to send to one our emails, and it sets the replyTo email to the email we want to respond to.  The rule is triggered, the auto reply is sent, and it includes the body of the original message in the auto reply. I am told this all works fine.  But we are currently making a change to our system and may have to move away from using phpmailer. I have been testing using the front API to send the initial message. My problem is that I can't seem to get a combination of API endpoints and rule configur

Hey there!Im working on a system in which I want to be able to reply to a conversation in Front, and immediately after, have it archive.Looking at the docs at https://dev.frontapp.com/reference/post_conversations-conversation-id-messages, I should be able to get that functionality by passing "options": { "archive": true }, however it doesn't seem to be working that way.Is there anything I'm doing wrong? Or is there a bug here?Im hitting the endpoint athttps://myDomain.api.frontapp.com/conversations/cnv_12345/messagesWith a json body of { "sender_name": "System - +123456789", "body": "Uhhh Syncing the message??", "options": { "archive": true }}Does this look right?Thanks!

Attachments don't seem to be coming through. Any advice on what might be happening? What datatypes are typically accepted? Right now I'm using data:application/octet-stream

What format are you expecting to receive the created_at datetime? I've tried everything I can think of and I keep ending up with very weird dates on the messages. If I'm converting Date Time objects are you looking for seconds? Are you looking for a date and time without any symbols?

It appears that messages with different subjects are being "threaded" or "grouped" together. Why is this happening?

We are importing messages via the API from our TMS. Then from inside our TMS, users can "Send Messages" which is equivalent to sending an email. When this process is completed in the TMS, we are expecting this message to be sent to the "to" (recipient) and to show up in Front as a sent message. What appears to be happening is that the message shows up in the Front Inbox but it's not actually being sent to the recipient. Is this because we're using a demo account or is importing a message into Front not the same as sending a new message from Front? What process should we be following to ensure that any email sent from our TMS is sent via Front?

I’m having messages imported via the API. Are the following things I should be fetched from somewhere or are they typically given to us by the user who has authenticated with the integration?Inbox Id Author Id   Thanks

I can't seem to find the information I need to start testing out a use-case for the API. I'd like to create logic to review each message that arrives at an inbox or folder, and then based on some condition, move a message (email) from the inbox to a specific folder along with adding a tag—I think you might call this automated message triaging; sort of like creating a rule with custom logic that can be integrated with my internal systems. Can you point me in the right direction?

We are thinking of building a product and we'd love to know to which extent we could communicate our app with the Front API. Basically, we would need access to emails in real time and being able to send replies, that's it. What would be the best starting points to look at from your API endpoints?

Do you have a PHP OAuth 2.0 client example for Front?

Am I able to add additional metadata in anyway to conversations? For example to say that it is related to order ID 123, so that it could be referenced by subsequent API calls. I am considering tags, however this would be a new tag per new message, so we could end up with 100s of these over time.

We are attempting to use the Front API Messages -> Import Message. All of the documentation is shown with using JSON encoding with a note that requests using attachments must use form-data encoding. We have the following request that is working when using JSON encoding.curl --location --request POST 'https://api2.frontapp.com/inboxes/inb_INBOX/imported_messages' \--header 'Accept: application/json' \--header 'Authorization: Bearer TOKEN' \--header 'Content-Type: text/plain' \--data-raw '{    "sender": {        "name": "Tester",        "handle": tester@example.com    },    "to": [],    "body": "Test Message From Agent",    "external_id": "12345",    "created_at": 1654708989,    "type": "sms",    "metadata": {        "thread_ref": "777",        "is_inbound": false,        "should_skip_rules": true    },    "attachments": []}' When executed, we get a 200 – OK message. However, to get attachments to work, I have to adjust the call to use the form-data encoding. The documentation has a s

Is there any API, RSS feed, download (JSON/YAML,….) to get all Front related IP ranges for webhooks? Need to set up a white-list on my end. Best