Skip to main content

Developers

Community topics about Front APIs and SDKs

440 Topics
wenyi_he
wenyi_heFronteer
published in API news & updates
Send attachments in ConnectorsCONNECTORS

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

200
wenyi_he
Mark Mishyn
Mark MishynConversationalist
asked in Developer Q&A
A bug with Front Context

Hello! I encountered a problem where https://dev.frontapp.com/reference/plugin-sdk-context doesn’t work as expected. Here I depicted a plugin usage scenario that went wrong.After page reloading the plugin is opened by default, and we see only 1 email attached to the user. At this moment, the issue is not visible. Next, we’re navigating to the Contact Details tab to check how many emails the user has in real. And we’re confusing that the user has 2 emails, not 1 as plugin Context said.  However, upon returning to the plugin, it correctly displays the information with 2 emails.To read this information I use  context.conversation.recipient.contact.handles Please take a look this bug, it causes problems in building the plugin.1st  - A plugin is open 2nd - Contact Details is open 3nd - A plugin is open AGAIN               

1021
justin
jonny
jonnyConversationalist
asked in Developer Q&A
HELP: Creating a historical monthly Conversation ID / Tag report (by inbox)

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

1422
jonny
Javier - Developer Relations
Javier - Developer RelationsCommunity Manager
published in API news & updates
Community contribution spotlights: A working MCP server and moreNEW SAMPLE CODE

We are thrilled to feature recent community contributions to our sample code! Read on to learn what sample apps and code your peers have recently shared with the community. MCP serverMany thanks to ​@zqush for going above and beyond to provide an example of a Model Context Protocol (MCP) server for Front! An MCP server is a standardized way to connect AI models to external data sources and tools, enabling them to access real-time information and perform tasks securely.  PHP code snippetsThank you ​@jross for contributing PHP versions of common Front code snippets!PagerDuty Connectors exampleThank you ​@jason for providing an example of how to combine Front Connectors and PagerDuty to send critical SLA alerts!Connectors and AI Assist for IT SupportThank you ​@gregkn for demonstrating how Connectors and AI Assist are used to power Front’s own internal IT Support service! Contributions like these are invaluable for making every customer’s use of Front more powerful. We deeply appreciate t

681
helena
jross
jrossRookie
posted in Developer discussion
PHP Send API Request via Curl

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

191
Javier - Developer Relations
jross
jrossRookie
posted in Developer discussion
PHP Verify Front Webhook Signature

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

190
jross
ruturaj
ruturajFronteer
published in API news & updates
The Front Chat iOS SDK is now available!FRONT CHAT

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...

290
ruturaj
kjanzen
kjanzenRookie
asked in Developer Q&A
System Variables in Connectors

Hello.  I am looking for any suggestions on how to use system variables in Connectors.  I have a moderate amount of comfort working with APIs.  I have a Connector set up and working - POST requests are working and creating records in our third party app without issue.I cannot seem to be able to figure out how to pass system variables through our POST request.  I can create dynamic variables in the Connectors, but these do not seem able to access basic system data.  I have tried every variation I can think of - {{user.name}}, user.name, etc. but all this does is pass {{user.name}}, user.name, etc.to the created record.  I’m hopeful system variables can be passed through the Connectors and I am just missing something very obvious.  Any input is welcomed and appreciated.  Thank you!

962
Javier - Developer Relations
jason
jasonFronteer
published in API news & updates
Vite-React-Auth0 sidebar plugin templateNEW SAMPLE CODE

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.

250
jason
smerel
smerelConversationalist
asked in Developer Q&A
content security policy with strict-dynamic

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?

1867
E
lucasalamos
lucasalamosFronteer
published in API news & updates
Expanded OAuth scopes are finally here!CORE API UPDATE

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. 

390
lucasalamos
naveen
naveenConversationalist
asked in Developer Q&A
exchange message-id with front message-id

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

341
R
NPdevs
NPdevsHelper
asked in Developer Q&A
Plugin SDK: context.conversation getting updated_at

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

873
jason
sudhanshu
sudhanshuConversationalist
asked in Developer Q&A
How to remove links from contacts via the Front API?

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?

1813
clemente_ortuzar
L
lifanConversationalist
asked in Developer Q&A
Question about OAuth

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

281
jason
NPdevs
NPdevsHelper
asked in Developer Q&A
Plugin: get ticket id from context

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

624
Javier - Developer Relations
Javier - Developer Relations
Javier - Developer RelationsCommunity Manager
published in API news & updates
Contact list endpoints replacing contact groupsIMPORTANT

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

1210
Javier - Developer Relations
kevin_pulido
kevin_pulidoConversationalist
asked in Developer Q&A
Reporting

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

303
cat_apac
edison.pizarro
edison.pizarroFronteer
published in API news & updates
Manage ticket statuses through the Core APICORE API UPDATE

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.

530
edison.pizarro
NPdevs
NPdevsHelper
asked in Developer Q&A
Plugin: spawn attachment preview

Is there a way to preview a message attachment from the Sidebar plugin, for example using the plugin SDK downloadAttachment()?I am currently only getting a File object returned from Front.downloadAttachment('msg_xxx', 'fil_xxx') with the following properties:lastModified:  1740416909060lastModifiedDate:  Mon Feb 24 2025 18:08:29 GMT+0100 (Central European Standard Time) {}name: "fd880b5930634b94bfa961a2b3815db2.jpg"size:  293622type:  "image/jpeg"webkitRelativePath: ""

212
NPdevs
NPdevs
NPdevsHelper
asked in Developer Q&A
Plugin: listTeammates()

A few questions regarding teammates:What would be a scenario where multiple teammates are returned by listTeammates()? Is the current front user always the first user in the array? Is there a better way of identifying the current front user from the plugin, ie. where only the current user is returned?

522
jason
Mark Mishyn
Mark MishynConversationalist
asked in Developer Q&A
Get a "seen" status of inbound message

Hello!I wonder why “Get message seen status” https://dev.frontapp.com/reference/get-message-seen-status API works only for outbound messages? Wasn't the initial idea to have a info WHEN a teammate has seen INBOUND message?{    "status": 400,    "title": "Bad request",    "message": "You cannot see seen status for an inbound message."}Why am I asking this? We’re implementing the Frontapp plugin which gonna track the time when a teammate seen a inbound message from a customer (to measure activity of diff(seen,archived)). There’re not those fields in the webhook triggers, so we can’t receive the time of “seen” activities. The plugin context API doesn’t have this data too.Also I see the internal CONVERSATION by ID request that returns the “seen” data for it. I think it can be useful for our task, but this data is not in the conversation PUBLIC API. Could you cover 2 questions please:1. How to get “seen” information per teammate for a MESSAGE?2. If for some reason (1) is not possible, how c

1053
E
G
GlentkConversationalist
asked in Developer Q&A
Support for persisting multiple chat on same machine with different accounts

We have been integrating Front Chat into our app, and the experience has been great so far. However, we are facing a challenge with supporting multiple logins on the same machine.Expected Behavior:• When a user logs in, they should see the continuation of their own previous chat (if available).• If a different user logs in, they should only see their own chat history (or start a new conversation if no prior chat exists).Current Issue:Right now, when a new user logs in on the same machine, they see the chat history of the first logged-in user, which we want to avoid.We attempted using the shutdown() method from the Front Chat SDK to clear the chat on logout, but this also removes the previous chat history, preventing the original user from retrieving their past conversations when they log back in.can someone help me out on this matter? 

553
cat_apac
Reinier
ReinierConversationalist
asked in Developer Q&A
Update Conversation assignee API call

Hey all,I am trying to build a connection to Front to interact with the conversations, so we can assign the assignees to the conversations through the API. Using the example of the API documentation keeps giving me errors and I can’t figure out what is going wrong. I’m using the Update conversation assignee with the NodeJS example, but I keep getting an error:{"_error":{"status":400,"title":"Bad request","message":"Body did not satisfy requirements","details":["body.assignee_id: missing"]}}I’ve tried it with JSON and FormData, but the error stays the same, my latest example code is the following const frontUpdateAssignee = async ({ conversation, assignee, token }) => {   const options = {    method: "PUT",    headers: {      accept: "multipart/form-data",      authorization: `Bearer ${token}`,    },    body: JSON.stringify({ assignee_id: "tea_hjdlj" }),  };  const updateAssignee = await fetch(    `https://api2.frontapp.com/conversations/${conversation}/assignee`,    options  )    .t

654
Reinier
jason
jasonFronteer
posted in Developer discussion
Never miss an SLA, with Front Application Requests and PagerDuty

If your team has SLA agreements you can’t afford to miss, or you already page on-call teammates for urgent issues, you might want to consider automating this using Front Rules and Application Requests.This post will guide you through how to add a Front Application Request to trigger a PagerDuty incident, and how to enable that from a Rule in Front. 1. Create a PagerDuty ServiceThe PagerDuty Service is required as the “entry point” for creating the incident. When creating the PagerDuty Service, select the Events API V2 integration;Creating a PagerDuty Service2. Create your Front Application RequestHead into Front > Settings > Developers, and create a new App. Give it a useful name like “PagerDuty”. Click into the Servers tab in your new App, and create a server. The PagerDuty events API is hosted at https://events.pagerduty.com, so we can add that as the Server Origin value. No auth is needed here - this is specified elsewhere.Click Save. 3.  Add Application RequestClick into the

220
jason

Badge winners

Show all badges
Terms & ConditionsCookie settings