API news & updates

We are thrilled to announce the implementation of a new rate limiting system that offers a more sophisticated and user-friendly approach to managing API requests. We will start rolling this new rate limiter out on Monday, September 22nd, with the aim of updating all companies by Friday, September 26th. Our improved rate limiter provides the following key enhancements: 1. Removing the penalty for 429 rate-limited requestsIn the past, hitting the rate limit meant that requests that returned a 429 response informing you of the breach also counted against your limit, which could result in compounding and unnecessarily long windows before your limit was reset. With the new system, 429 rate-limited requests will not count towards your rate limit, making it clearer to understand when your new rate limit window will replenish.2. Burst Limit for Occasional Traffic SpikesThe introduction of a burst limit provides

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 hel

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

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!

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

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 act

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

You can now reply to specific comments using the Core API. Comment replies visually indicate which comment is being responded to, helping users follow the conversation. This feature has been available in the Front UI for a long time, but is now available via the API. Use the Add comment reply endpoint to create a comment reply. Happy coding!

The is_spammer property is no longer part of the Contacts response. This property was deprecated a few years ago but is now fully removed from the response object. No issues are expected, but if you notice any, please leave us a comment or reach out to our Support team.

Application triggers allow you to execute workflows in Front in response to events that occur in external systems. For example, you might want to re-open conversations in Front anytime an order changes status. When the event occurs in your order management system, you send Front an event payload identifying the trigger for the change of order status. The event payload would also identify an application object, likely through the link to the order in your management system. Once the trigger is received, any conversations that have a related application object attached for the order would reopen based on a rule. Your rule could also pull additional properties from the trigger's event payload, such as the new status, and make that available through a dynamic variable. The additional data from the property could apply a comment or tag or other action in Front based on the new status. To learn how to use application triggers, refer to our Developer Portal:

You can now open a sidebar plugin from URLs found in Front messages or comments. The format for doing so is:Syntaxhttps://<Front base domain>/open-sidebar-plugin/<App UID>Examplehttps://app.frontapp.com/open-sidebar-plugin/40a4eae201a760d1 Pass custom properties to your pluginYou can pass custom properties in the URL as query string parameters, which will then become available to your plugin’s context in the EntryPoint object.https://app.frontapp.com/open-sidebar-plug

Going forward, Front will disable application webhooks that do not respond successfully. After three failed attempts, the webhook will be disabled and Front will stop sending events to your URL. We expect this change will mostly impact webhooks set up during development that are no longer used. However, if an active webhook experiences downtime and is disabled, you can go to the Webhook feature of your developer app and click Update to re-verify and re-enable it.

Hello Front developers, If you retrieve a conversation through the API, the response will now return a 301 redirect if that conversation has been merged into another one. Previously, the API returned a 404. This change makes it easier to keep track of conversations after they have been merged. The change applies to any API endpoint that interacts with a specific conversation:Get conversation Update conversation Update conversation assignee

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 objec

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

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.

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

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  

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

We are happy to announce that you can now access knowledge base API endpoints through the Core API. These endpoints allow you to read and update your internal and external Front knowledge bases. With the API, you now have the flexibility to process your knowledge base content for various purposes, including advanced display on different websites and additional means of importing content. Read the docs on our Developer Portal to start using the knowledge base API endpoints.

We are thrilled to announce a new enhancement to our Core API knowledge base resources: Endpoints now return a slug for article and category pages! The slug is a user-friendly, readable string that can be used to construct URLs to your knowledge base articles and categories. This addition makes it easier than ever to integrate and surface your knowledge base content within the search results or display components of systems external to Front's knowledge base, such as a community hub or other resource center. The following endpoints return the URL slug in their response:List articles in a knowledge base Get a knowledge base article

You can now download attachments via the following resource-specific endpoints:Download attachment for a comment Download attachment for a message template Download attachment for a messageThe ability to download message template attachments is a new benefit. The other benefit of these endpoints is that Front validates that the requester has access to the resource in question versus only validating the attachment access credentials. Fetch attachments via their download URLFront recommends you fetch attachments via their download URL (which includes resource-specific routing) versus providing only the ID

You can now access entry point data in the Plugin SDK to learn how a Front user opened your plugin. A new property called entryPoint is now available in the context object. Read the full details on our Developer Portal This property allows you to handle different scenarios depending on where the plugin was opened. The current plugin entry points are:SIDEBAR—User opened a plugin in the Front sidebar. COMPOSER_TOOLBAR—User opened a plugin in the composer toolbar while composing a message. CONTACT_HANDLE—User opened a plugin from a Front contact’s phone handle. More information on plugins that open from this entry point in order to make or handle calls will be coming soon!