Developer Q&A

Hi, We're using the JS Chat Widget API. I found an issue when using the `show` command. If the 'show' command is run too soon after the 'init' command, it has no effect. Delaying the 'show' command by using setTimeout seems to work around the problem. Is this a bug? There doesn't appear to be a way to tell if the chat is ready to be shown or not. Thanks for your help

Hi guys,How can I forward an email using the Front API? I don't see a method for that, although the Forward button exists in UI.Any suggestions?

Our use case is that we want to automate the process of adding a new Twilio phone number to an existing inbox. So that the agent can continue to receive sms responses from both numbers (old plus new one). Since each inbox was created manually on the Front website, we can't locate the inbox id for a specific agent.  Want to know if the Front team can support filtering on the Get channels endpoint?

We were showing front chat app icon on FE to communicate with our support team, everything was working fine from the past years, recently the icon is not showing anymore, We have initialised FCSP token and frontChat too. But we don't know how suddenly this stops working.Is there any expiry date in token?Or is there any change is script to integrate front chat?<script src="https://chat-assets.frontapp.com/v1/chat.bundle.js"></script><script> window.FCSP = 'xxx';</script> 

The way we are currently using Front is we create contacts beforehand using https://dev.frontapp.com/reference/post_contacts and then use https://dev.frontapp.com/reference/post_channels-channel-id-incoming-messages to create a conversation for them with one of our agents. This endpoint works for us because we can pass contact_id in the sender object but the problem is it does not return the conversation_id that we need for sending further messages within this conversation. Instead we are getting back the message_id only and have to query for the message entity to get the conversation_id from it. This makes our flow inefficient.  Another way to create conversation is https://dev.frontapp.com/reference/post_channels-channel-id-messages and it does return the conversation_id but it does not accept contact_id param to create conversation for existing contact. Ideally we want to be able to create conversation for existing contact_id and receive back the conversation_id in the same request.

My webhook  loading time is around 5.3 sec but it works for "inbound" message events  and you recommended loading time below 5 sec so for manual move do we have different webhook loading time and what do you recommend 

What are the differences in events payloads for “move” events between rules and manual user actions?

Can we find which inbox/mailbox/folder the user is in at any given time via the Plugin SDK?This is then used so that when the user later returns to the inbox we can return them to the last message they were on in that particular mailbox.

We are currently after a historical backload of our Front's event stream prior to 14-06-2022.I've looked at the get_events API and tried fetching events from it but:No matter how we specify the start/end timestamp parameter the API will return the event starting from the current time It only emits 15 events per fetch.Please let me know

Using the API, I would like to list all the conversations with status = "assigned" as described here:https://dev.frontapp.com/reference/list-conversations I'm not sure how the endpoint should look like. Can you please send me the endpoint with the query params? Thanks

Looking for information on OAuth. Also, does it support PKCE?

I’m looking for your rate limiting policies

We are wanting to use the API to create custom channels. The only piece we can't automate right now is creating the Channel. We have the inbox, but need a way to create the channel, and add it to the inbox so that we can get the channel ID, add our endpoint to the channel for messages, etc… Where in the API would be input endpoint for our service when messages are sent from Front?

To add a comment to a conversation, the API requires us to pass the conversation ID. But when we create the conversation using the API in the custom channel, we do not get the conversation ID in the response. The response for the above only gives us the following keys:conversation_reference message_uid statusTo pass a comment after creating the conversation, we need the conversation ID.How do we get this?Sample response data:data: {    conversation_reference: 'i:16623333570-h:62fb674ca562f438cbaeba4c06_game_62e4fc8e73e3232322668b3efbe3',    message_uid: 'fe445d0cb7b72a48460829e74fd82332fdcd',    status: 'accepted'  } 

Are these the only API end points for CSAT data? num_csat_survey_response and pct_csat_survey_satisfaction ?  What is the suggested method for customers to get all CSAT data via the API? Would it be by leveraging a full events export?  What if they also want the "raw" CSAT data? Looks like those end points will only pull total # and averages, correct?

I’d like to send more data to the custom channel endpoint, like sending more customer data, sending a tag, etc. The endpoint seems like it only receives messageshttps://dev.frontapp.com/reference/post_channels-channel-id-incoming-messages I assume I can make additional calls after the conversation exists to perform actions like adding tags, and that I can hit the Contact API endpoints to create/modify the Contact record.However, I’m hunting through the docs and I can’t find where I can get a contact_id from the message_uid that is returned when I create the message in the custom channel. I can of course create a contact before calling the custom message endpoint, but that fails if the contact exists already, which, maybe that is fine. Ideally the system can send the message, and then I can just grab the contact_id of the contact on that message, and add meta-info after the fact. I can’t even find an endpoint to grab a contact ID by handle, that’s the other strategy to avoid a 429 failu

We're working with a third party company on an integration with our data in Front, and we're hoping to get some support on pagination through the Events API.  I am trying hit the list events endpoint. I am able to make the first request successfully.In the response, I see"_pagination": { "next": "https://api.frontapp.com/events?q=after:2022-08-11T16:05:03.088883Z&page_token=XXX..." }However, when I make the request with this link, I run into the following 400 response with this message"status":400,"title":"Bad request","message":"Query parameter page_token is invalid." I was hoping you might have some insight here? 

I need a little direction with something I’m struggling with. One of my teammates previously wrote a webhook that triggered whenever an email was received. This works regardless of if the user opens the email.I’m looking for a way to limit the amount of times the function executes so instead I’m trying to build functionality that will on a button click within the plugin, select some emails starting at the newest in the current email inbox and run a function on each of them.Any chance someone can point me in the right direction?Thanks! 

Please advise where I can find the developer environment within my front connection.

Hi, We recently adopted Front for our Sales Team but the CRM we use, Copper, does not have a native integration. I was told that we could use Zapier to create connections between the two systems but unfortunately, it appears that most of the functionality exists only in shared or team inboxes.  Upon exploring further, there does seem to be an available API connection via Webhooks by Zapier. Can you help shed light on this?

Hello,What determines which conversations/messages a user can get through an API endpoint using a Front token they made?One of our clients provided us with a Front token with the scopes "Shared Resources", "Private Resources", and "Provisioning" enabled, and our plugin would use that token to make API calls on the conversations they select from their inboxes. This client also has a starter plan and works from private inboxes.Currently, this client is facing an issue where our plugin is unable to read conversations from their private inboxes, and I'm not sure what could be causing that.When I make a GET request to https://api2.frontapp.com/conversations/cnv_X, I get the follow response body:{    "_error": {        "status": 403,        "title": "Forbidden",        "message": "This agent is not allowed to read the \"conversation\" with ID: \"X\""    }}Is there anything we could do on our end to fix this issue, or is this primarily caused by our client's Front account?

How can I add a tag to a message that was created via the Receive custom messages endpoint? https://dev.frontapp.com/reference/post_channels-channel-id-incoming-messages There's documentation for how to attach a tag to a Conversation but my understanding is that these two are different primitives. See here:https://dev.frontapp.com/reference/post_conversations-conversation-id-tags

We're working with webhooks at the moment, and I'm trying to understand the data that I receive. What is the target? What is the source? What are all the values that each property can take? I'm not sure where to look for this in your documentation.

I am currently trying to use the createDraft context API using the SDK (found here: https://dev.frontapp.com/reference/createdraft) My code is below but the draft just doesn’t include the attachment. The draft is successful otherwise.const createDraft1 = await.Front.createDraft({ to: ['acme@example.com'], subject: "Your invoice for the order: ", attachments: ['./X.pdf', 'path/X.pdf'], content: { body: 'Invoice attached.', type: 'text' }}); 

Hello,We are progressing on the synchronization of the Analytics part, over the last 30 days, for accounts. For this, as seen together, we use the /reports routes in GET then PUT.We are facing several problems. The limit is not 200 calls per minute for these routes but 200 + a 1 second delay between each. We need 2 requests: GET then PUT. That is 4 seconds for 2 requests for an analysis request. First limit. Second limit, in order to collect information from the last 30 days, or even more, we need a significant delay: around 20 hours. However, it seems that our "massive" requests, by internal choice, trigger this error:Could not resolve host: api2.frontapp.com.Are we, suddenly, considered as "spammers" and therefore blocked after a number of requests? In this case how should we proceed if we want to refine our filters and "consume" requests.Thanks in advance.