Developers

I’m in the process of building an integration for our application. We’re not Front customers, but our customers are Front customers.I setup a trial account, but I’m running into issues with many development workflows - key integration features are gated behind paywalls. I’ve built a bunch of integrations lately. It’s not uncommon to have premium features gated, but this is the first time I’ve run into basic integration functionality being gated for developers. Generally, companies are limiting abuse by keeping developer accounts to, say, 3 or less users. but generally allow most of the features to be available.Further, I don’t have a simple way to simply sign up for a paid account. Once the credit card comes out, the vendor review process comes out. I’d really like to avoid that.Here’s my use case:We have an AI tool that we integrate into our customer’s ticketing environments. We need inbound webhooks when tickets are created or comments are added to tickets _on specific inboxes_ While

We're in the process of building out a Front integration and trying to set expectations with customers of when it will be ready. Specifically, we want to get this in the hands of customers quickly. We’re trying to decide if we should have them setup “internal” OAuth clients while we wait for the partner review process to finish.I’m curious if you could provide a ballpark estimate of how long it will take to review and approve an app once I submit it for review?  Days, weeks, months? 

We have a saved Message Template for logins to our system that we send out frequently, we have noticed that when we paste in the username to the template within the body of the email it is changing the link behind it to an old customers email address. Any ideas why this might be happening or how we can stop it..  We paste in the new customer email address on the line Your Username is .. (eg email@email.co.uk) it shows the correct email address but on sending, it is changing the mailto link behind it to another email address beginning with info@. So when the end user then copies the email their side if tells them the credentials are wrong because it copies the info@ email address.Any suggestions gratefully received. 

Hi TeamWe are integrating front chat to our website. So for its good but we are facing 2 problems that we are trying to fix.First one is related to showing the previous chats we have built flows and for some flows we have been seeing escaped html spans in the chat history. Please see the screenshot attached. From what I understand this happens when we usually follow multi choice question with a message and it shows span in the conversation historySecond issue we are facing is that sometimes when we look at the conversations page. It doesn’t show the last message in the conversation instead it shows first message or second last in the conversation which might confuse the users.Looking forward to hear from you,Thanks and RegardsGlen 

Hi, I wasn’t able to add this as idea, so asking here. If you are planning to add article import to knowledge base from docosaurus? Maybe there is some API that we can use to add articles from docosaurus? Thanks 

I’m trying to add application objects to my published application. I need users from other companies who install my application to be able to set it up with as little configuration steps as possible.  I was trying to follow the Logistics TMS Guide, and I was able to set up Application Objects, but I found that I had to create a rule to trigger the App Object whenever a new message came in.  Does that mean that my users would have to manually create the rule for the Application Object to be added to incoming messages? Is there any way to build this logic into my published application so it automatically gets set up when the app is installed? 

Connectors provide a no-code means of making API calls to external systems and can also transform URLs or strings found in comments or messages into structured objects that are easy to access from a conversation in Front. Connectors come in two flavors:Application objects (previously known as “dynamic objects”)—these connectors identify matching patterns (such as order IDs) in Front conversations or comments and automatically attach a structured object to the conversation that contains information about and a link to the external resource. Application requests—these connectors make API calls to external systems to provide a no-code method for building integrations. These requests can also be leveraged in rules and macros. Currently, only GET requests are supported, but additional methods will be available soon to allow you to push data to external systems.  If you are currently using dynamic objects, they will be migrated to application objects in the coming days without any impact or

I have a problem using the fron-chat-sdk

Front has just released an official Front Chat Android SDK that makes it easier than ever to install Front Chat in your native Android apps. Visit our Developer Portal to learn how to install and use the SDK. The setup guide includes a link to the SDK’s GitHub repo.

You can now send attachments in Connectors! To do so, set the Content Type to multipart/form-data when building the request and include the attachment data in the body.Sending attachments through Connectors enables use cases for when you want to send files to external services. For example, a Front teammate using the JIRA Connector could run a macro to upload an image to a JIRA task describing an issue they are dealing with. Watch a video of the example use casePasscode: Pi%gEU9L

Hi all — I’m not a developer, I’m a sales guy (apologies) - so that should be the problem right there.  Anyway, I can’t loop in our dev team due to strategic constraints, and I’m trying to build a simple reporting workflow using the Front API.Goal:Generate a report that lists: Conversation ID Shared inbox name(s) Tags Grouped by Month and Year, based on when the conversation first arrived (i.e. was created). I'd like to use this for historical reporting — so I need to pull conversations created in previous months, like March 2025, February 2025, etc.From what I understand, this means: Using the /conversations endpoint Possibly filtering or grouping by created_at But I’m running into issues — even when I try filtering with something like created:[YYYY-MM-DD TO YYYY-MM-DD] (or manually filtering the created_at values after retrieval), I only return conversations with today’s date, nothing from prior days or weeks.Key question:👉 What’s the best way to reliably retrieve conversation

Hello,Sharing how to send an API request using PHP Curl and Bearer token:<?phpdefine('FRONT_API_KEY', 'xxxxxxxxxxxxxxxxxxxxxxxxxxx');/** * Performs an API call using cURL * * @since 1.0.0 * * @global string FRONT_API_KEY * * @param string $url URL. * @param string $requestType 'GET', 'PUT', 'PATCH', etc. * @param array $postFields Array of fields and values to be posted to URL * * @return array Associated array of JSON objects returned from API call. * */function api_call($url, $requestType, $postFields) { try { $ch = curl_init(); if ($ch === false) { throw new Exception("Failed to initialize"); } curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, $requestType); if (isset($postFields)) { $json = json_encode($postFields); curl_setopt($ch, CURLOPT_POSTFIELDS, $json); } curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_USERAGENT, "curl/7.7

Hello,Working on my Front Admin certification and this is my contribution to the community. I haven’t seen many PHP integrations and wanted to share how I am verifying the Front signature.<?phpdefine('FRONT_WEBHOOK_API_KEY', 'xxxxxxxxxxxxxxxxxxxxx');/** * Verify Front rule webhook request function * * Calculates the base64 encoded HMAC hash of the request body (payload) using SHA1 algorithm and the Front API key. * Compares the hash to the X-Front-Signature header to verify the request is from Front. * * @since 1.0.0 * * @param string $payload Request body. * * @return bool true if verified, otherwise false. * * @link https://dev.frontapp.com/docs/webhooks-1#configure-rule-webhooks */function is_valid_front_webhook($payload){ if (isset($_SERVER['HTTP_X_FRONT_SIGNATURE'])) { $hexHash = hash_hmac('sha1', $payload, mb_convert_encoding(FRONT_WEBHOOK_API_KEY, 'UTF-8')); $base64Hash = base64_encode(hex2bin($hexHash)); return hash_equals($_SERVER['HTTP_X_FRONT_SI

Front has just released an official Front Chat iOS SDK that makes it easier than ever to install Front Chat in your native iOS apps. Visit our Developer Portal to learn how to install and use the SDK. The setup guide includes a link to the SDK’s GitHub repo. P.S. An Android version of the SDK is coming soon...

We just released sample code that demonstrates how to create a Front sidebar plugin using Vite, React, and Auth0!  Visit our Developer Portal to learn more.

I’m trying to use ‘strict-dynamic’ for my ‘script-src’ content security policy.I have a nonce set up in my page where I include the Front chat widget script: <script nonce="random nonce here" type="text/javascript" src='https://chat-assets.frontapp.com/v1/chat.bundle.js'></script>but it appears that that chat.bundle.js script dynamically loads app.bundle.js, which leads to a CSP violation in Chrome:Refused to load the script 'https://chat-assets.frontapp.com/v1/app.bundle.js?v=840fb872' because it violates the following Content Security Policy directive: "script-src 'self' 'strict-dynamic' chat-assets.frontapp.com 'nonce-9a6157311c94f2a96914fe5ac561d6fc'". Note that 'strict-dynamic' is present, so host-based allowlisting is disabled. Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.Is there a way to use strict-dynamic with the Front chat widget?

We are thrilled to announce that partners and developers can now use OAuth to access all available Front permission scopes, such as personal resources and knowledge base data in addition to shared workspace data. This update means that integrations can use OAuth regardless of the type of data they need access to. OAuth makes it much easier for customers to install your integration by simply agreeing to the OAuth screen instead of requesting that the customer manually generate and supply your integration an API token. Previously, OAuth tokens could only access shared workspace data.  Visit our Developer Portal to view the full list of available scopes. You can manage scopes when you add OAuth credentials for your developer app. With this change, Front admins will also have access to a Tokens tab on the App Store that lists the resources your app has been granted. Learn more on our Help Center. 

How do I lookup a front email using exchange or office365 message-id?

Is it possible to get a conversation’s updated_at datetime from the Plugin SDK?

Hey, We had previously added a few links to contacts in our Front instance. However, we wish to remove them now. The API explains how that can be done with lists, but doesn’t really go into contact links. How can we achieve this?

If we setup OAuth with a agent, but later, the agent resigned and her account deactivated, will this affect the OAuth?

Is it possible to get Ticket data from the context (singleConversation) via the plugin SDK?

Our new contact list endpoints are replacing the contact group endpoints, which will be deprecated on September 1st, 2025. Please update your API calls before September 1st so that the URLs use contact_lists in the path instead of contact_groups. Note that the contact list ID remains the same as the contact group ID. The following table details how to change your endpoints:Deprecated path New path Notes https://api2.frontapp.com/contact_groups https://api2.frontapp.com/contact_lists   https://api2.frontapp.com/contact_groups/{contact_group_id} https://api2.frontapp.com/contact_lists/{contact_list_id} The contact_list_id is the same as the contact_group_id https://api2.frontapp.com/contact_groups/{contact_group_id}/contacts https://api2.frontapp.com/contact_lists/{contact_list_id}/contacts The contact_list_id is the same as the contact_group_id https://api2.frontapp.com/teammates/{teammate_id}/contact_groups https://api2.frontapp.com/teammates/{teammate_id}/contact

We are looking for a report, that will provide the below information to export so that we can merge with our inbound phone traffic. DateHourInboxDirection

You can now manage ticket statuses through the Core API. Front released ticketing a couple months ago, which you can now access via the API if your company has the ticketing feature enabled. The following is a summary of the new ticketing functionality available in the Core API:Conversation responses return status_id, status_category, and ticket_ids fields. Search for conversations in the open, waiting, or resolved ticketing statuses via the is operator. Use ticketing filters in the q query string parameter when listing conversations. Access new Statuses API routes:  List company ticket statuses Get ticket status Update the status_id of a conversation. Update conversation reminders with a waiting status_id.