Developers

I’m currently trying to understand whether there’s a way to determine which user granted the OAuth token I’m using in the request?I’ve found the `API Token Details`, but that appears to only expose company-level information.Could I achieve this by introspecting the JWT claims? (e.g. `sub`?) 

Dear community,I need your help and would greatly appreciate any support.My task:Fetch exactly the same conversations shown to my users and team inboxes in the “Open” and “Later”/“Snoozed” views. I have not been able to accomplish this.Could someone provide a sample code or give instructions how to exactly filter conversations to achieve the goal? (I am Admin).Thank you,Best regards,Denis

I’m currently having trouble where I’m not able to trigger a sidebar opening when clicking “Call with” from a contact preview. It works without issue from the Contact Sidebar, but not the preview card. I’ve recorded this demo walking through what I’m experiencing.    

Hello,  We are looking for a developer who could connect Front to our property management software with API and Webhooks. We could also use some additional settings in Front, if you are interested send us a message or an e-mail on info@rent4me.hr I hope this is in line with the community guidelines. Kind regards,

I am using the POST `/conversations/cnv_123/messages` endpoint to add a reply message to a conversation that already exists. When I fetch the messages, I see that they contain a `metadata` field that is just {}.  Is there a way to set custom metadata fields for later use in the endpoint? When I try just adding a `metadata` field to my payload, the operation passes but the metadata does not persist when re-fetched.

Hello - at the moment when attempting to use an inbuilt copy paste button in my sidebar plugin i get the following error.Unhandled Runtime ErrorNotAllowedError: Failed to execute 'writeText' on 'Clipboard': The Clipboard API has been blocked because of a permissions policy applied to the current document. See https://goo.gl/EuHzyv for more details.After investigating the front sidebar plugin iFrame it looks as if clipboard-write is not allowed. Are there either, plans to change this or a suggested workaround? If no plans to change at the moment i can submit as a suggestion. Thank you for your help. 

We're excited to announce that the Front UI Kit is now fully compatible with React 19! This update ensures that our components and Storybook are aligned with the latest major React revision, allowing you to take advantage of React 19's new features and improvements. To update run npm install @frontapp/ui-kit@latest or yarn add @frontapp/ui-kit@latestMake sure you are using React 19 before upgrading the Front UI Kit React 19 introduces several enhancements that improve app performance, developer experience, and component flexibility. Our team has diligently tested and updated our UI Kit to ensure smooth integration and optimal functionality with this major React release. For those who aren’t familiar, the Front UI Kit is a set of React components that help you build plugins. The Front UI Kit includes buttons, menus, date pickers, and many other useful and common plugin components. Using the Front UI Kit should help you save on development time and provide your plugin users a set of well

This change contains a deprecation of the external_conversation_id property in the metadata object.You can now reply to specific messages through application channels.{ "type": "message", "payload": { [MESSAGE BODY] }, "metadata": { "external_conversation_ids": string[], // External identifier of the conversations related to this message. "referenced_message_external_id": string // (Optional) ID of the message being referenced as a direct reply }}As part of this change, we are introducing two new properties in the metadata object used when creating or replying to messages in a channel:external_conversation_ids—a string array containing the external conversation identifiers, which you use when creating or receiving messages. This property replaces external_conversation_id, which is now deprecated in the metadata object. This change allows you to send multiple external conversation IDs instead of just one. reference_message_external_id—the external identifier of the mes

I ran into internal error 500 when trying to use attachments. Even If I don’t use attachments and just Content-type multipart/form-data it returns error anyway.postmanpostmanwith code (wordpress)[headers] => WpOrg\Requests\Utility\CaseInsensitiveDictionary Object        (            [data:protected] => Array                (                    [date] => Sun, 03 Aug 2025 06:23:15 GMT                    [content-type] => application/json; charset=utf-8                    [content-length] => 52                    [x-ratelimit-limit] => 100                    [x-ratelimit-remaining] => 98                    [x-ratelimit-reset] => 1754202213.637                    [vary] => Accept                    [etag] => W/"34-zWc8gW+EWeg2mrqPaNjNywdzhTk"                    [x-front-time] => 33                )        )    [body] => {"_error":{"message":"An internal error occurred."}}

Hi everyone, Has anyone here built a custom integration between Front and a cloud contact center solution?We’re looking to:Display incoming voice call context in Front Sync call metadata (duration, caller ID, agent notes)

Hi everyoneWe’re exploring ways to integrate our cloud contact center solution with Front and wanted to see what others here have done. Specifically, we're hoping to streamline agent workflows by syncing conversations, contact data, and possibly call recordings into Front.Has anyone here integrated Front with platforms like:Genesys Cloud WebEx Contact Center Talkdesk Five9

 I have an image in signature. When sending from admin image is shown correctly and has attribute data-image-whitelisted. But when using API it is brokenfrom API$url = 'https://api2.frontapp.com/channels/' . $channel_id . '/messages'; $body = array( 'to' => array( $to ), 'subject' => $subject, 'body' => $content, 'text' => wp_strip_all_tags( $content ), 'options' => array( 'archive' => false, ), 'author_id' => 'tea_j7twg', 'signature_id' => $signature_id, ); $args = array( 'method' => 'POST', 'headers' => array( 'Authorization' => 'Bearer ' . $api_token, 'Content-Type' => 'application/json', // 'Content-type' => 'multipart/form-data', ), 'body' => wp_json_encode( $body ), 'timeout' => 30, ); from adminI know also that if omit author_id, email always in spam.

You can now configure servers with variable subdomains. This enables your apps to connect to APIs with customer-specific endpoints (e.g. Salesforce, Shopify, Netsuite) or support different regions or production environments. During setup, the developer specifies what part of the origin is a variable, and then during installation of your app, Front admins supply the specific subdomain value. Happy coding!

I want to access the data used to calculate handle time for my team which to my understanding isn’t included in the fivetran schema that I’m currently using to connect to the database. Which API end point do I need to interact with to get this? I understand the logic used to calculated handle time but what are the fields (i.e. date, interval) used called and how can I find them? 

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               

We’ve added ticketing concepts to the Plugin SDK so you can easily view and manage conversations for companies that have this feature enabled. The new method and data model updates should help navigate Front ticketing within your plugins without having to call the Core API. To grab the latest version, run npm install @frontapp/plugin-sdk@^1.9.0 --save or bump your package version manually. If using Yarn, run yarn upgrade @frontapp/plugin-sdk@^1.9.0. The Plugin SDK now offers the following additions:A new listTicketStatuses method that returns the ticket statuses available for the company. The Conversation model in the Plugin SDK Context has been updated to include the following fields. statusId String The ID of the ticket status that applies to the conversation. Only present if ticketing is enabled for the company. statusCategory String The category of the ticket status: open, waiting, or resolved. Only present if ticketing is e

Build more flexible Connectors by adding multiple requests to your configuration—all within a more intuitive visual interface.  We’ve redesigned how you build Connectors in Front, moving from a rigid step-by-step setup to a flexible flow builder. This new visual interface gives you greater control when connecting Front to external APIs and systems using application requests and application objects.With the new visual flow builder, you can now add multiple requests within a single Connector configuration. Whether you're retrieving data from different endpoints or chaining actions across systems, you can place each request exactly where it makes sense in your workflow. The flow-based layout makes it easier to see how everything fits together—and much simpler to make updates down the line.Your existing Connectors will be automatically migrated to the new flow builder within the coming days.Start building smarter, more powerful Connectors—no code required. P.S. We also introduced the abili

Hello,We are looking for a developer to help us migrate 6000 email conversation as well as 10 inboxes (and some tags and contacts) over to a different Front account. We have been using Front for a year through a third-party company that we pay to perform customer service duties, but we now want to do this in-house and are looking to open our own account.

Hello, I would like to ask if it is possible to display the typing indicator while waiting for a response from the API, and secondly, how can I authorize the client logging in to the chatbot via SMS?

The first two steps in the documentation to make an app are to go to settings, click on company, and then click developers. However, I can’t see developer as an option and nothing appears on the search bar either when I search for developer. I have been granted admin permission from the company (received it a few hours ago). Sorry if this is a really silly question to ask just no idea how to continue from here. 

Are you planning to add support for Expo for React Native in the future?Our team uses Expo to build and ship our mobile app, and we’ve historically used Intercom (which already has an Expo plugin). We’re considering switching to Front but the lack of Expo support makes the potential switch a big headache.

initially I thought adding the inbox access to the newly created teammate group would work but I get an error that Team access is required to link to team inboxes. I find it odd that I can create a teammate group via the API but cant actually add inbox permissions without a manual step in between? Any insight would be appreciated, just want to make sure I am not missing something.  Thank you! 

We have a Front integration that involves fetching conversations within a timeframe from selected inboxes, at the moment we paginate through the conversation search endpoint for each inbox ID. However, to ensure that we fetch all the conversations in that timeframe it would be much easier for us if the inbox filter was treated as one of the `OR` filters (from, to, cc, bcc) so that we could filter `inbox:A inbox:B after:<date> before:<date>`

I’m looking for a way to include a link that users can click on to compose a new Twilio SMS in Front. Ideally it would work similar to clicking the phone number on a contact record (where it opens a compose window with the To: field already pointing to the phone number.  Is this possible today? It would be great if it was possible to just have a link like app.front.com/compose?type=sms&to=1234567891 but I’m also open to using the core API to create a new conversation and then link to that conversation.  

You should now see a fresh look and feel to the UI when you navigate to Settings > Developers. These changes were made to help you manage features on your developer apps more quickly. The Apps list now displays the features associated with each of your apps:When you click into an app, you will see that the Features tab now lists all the app’s features so you can easily manage them without having to click into each feature card like you did in the old experience.The OAuth tab has been moved into the Features list. It was previously a top-level tab. When you click Add feature, you will be presented with a new categorization for quick selection of the feature you want:Final note: The Basic information tab was renamed to Settings, but is otherwise the same.Let us know if you have any feedback about the new experience. Hopefully it will save you time when managing your app’s features!