API news & updates

Starting October 19, 2026, we’re rolling out a new rate limiter for the Core API, with all companies updated by October 31. Your rate limit stays the same, but we’re changing how your requests refill. What’s changingToday, your rate limit resets all at once at the end of each one-minute window, with a separate burst allowance that takes 10 minutes to replenish. The new limiter replaces both with a single allowance that refills continuously at your rate limit, so at 100 requests per minute you get back about one request every 0.6 seconds instead of all 100 at the start of the next window. This removes the cliff at the end of each window, which means an integration that spreads its requests out at its rate limit can run indefinitely without waiting for a reset, and the wait after a 429 is now usually a few seconds rather than up to a minute (429 responses still don't count against your limit). Short spikes are still absorbed: while you send fewer requests than your limit allows, unused c

Heads up for anyone who works with Front API tokens. When you create a token in Settings > Company > Developers > API tokens, the full value is now shown only once right after creation. After creation, the token can’t be revealed or copied again, and the token’s detail page only shows a masked value with the last 8 characters. Existing integrations will keep working as before, but you won’t be able to see the full API token value anymore. If you encounter any issues with this change, please let us know in the comments, and we can help you out during this transitionary period.

If you build an application channel that syncs message templates into Front, you can now remove one directly instead of waiting for a resync. DELETE /channels/{channel_id}/application_message_templates/{external_id} Previously, when a template was deleted in your external service, Front kept its copy until the next full resync, which only runs on channel creation or a manual trigger. Now you can call this the moment your deletion webhook fires and keep Front in lock step with your template catalogue. The endpoint returns 204 on success, 400 if the channel doesn't support message templates, and 404 if no template matches that external ID. View full details in the Developer Portal.

You can now subscribe to conversation lifecycle events in Autopilot Resolve, so your app can react in real time as end users move through a conversation, from starting a new one to escalating to a human teammate. Available event types:created: end user starts a new conversation viewed: end user opens or navigates to a conversation escalation_offered: Autopilot Resolve offers to hand off to a human escalated: the conversation is handed off escalation_declined: end user dismisses the offer status_changed: the conversation moves between open, in_progress, and resolvedThree ways to subscribe, depending on your setup:FrontCompanion.on(handler) for a synchronous listener that returns an unsubscribe function onConversationEvent as an option on init() to register in the same call A companion-conversation-event CustomEvent on window, which works even before the boot script has loadedCommon patterns include firing your own analytics when a conversation escalates, updating your UI when a new conv

You can now create application channels programmatically, without manual setup in the Front UI for every new channel your app needs. This unlocks fully automated provisioning flows so your integration can spin up channels as customers onboard or as new use cases emerge. POST /inboxes/:inbox_id/channels To create an application channel, send a request with:type set to custom application_uid set to the developer app that defines the channel credentials matching your application server's authentication type (API key, basic, bearer, or OAuth2 variants)For OAuth2 authorization_code flows, omit credentials and complete the OAuth flow interactively after the channel is created. Full parameter details, credential shapes, and examples are in the reference docs. Happy coding!

 We've added a new set of API endpoints and settings designed specifically for building voice call integrations in Front. If you're building a telephony integration or looking to bring voice into your Front workflows, here's what's new.New API endpointsThe Channel API now includes dedicated endpoints for voice calls:Create a call Update call status Add a call transcript Add a call summary Add a call recordingCall state managementVoice channels support a full call lifecycle — from ringing and queued to connected, hold, transferred, hangup, missed, and abandoned — with defined valid transitions between each state so your integration can handle any scenario cleanly.There are also related call events.App configurationVoice integrations are built on top of application channels, with a few voice-specific settings to configure:Use a Phone contact type when setting up your application channel feature Add a sidebar plugin feature to visualize calls and related assets — with support for incoming

With the Autopilot Resolve SDK, you can take complete control over the Autopilot Resolve widget on your websites. The widget answers customer questions using your Front knowledge sources and Playbooks, and escalates to a human agent when needed. The Autopilot Resolve SDK gives you more advanced control compared to the default JavaScript snippet. It allows you to mount the widget in a container element, pass customer context to the AI, manage visibility, and handle identity verification for logged-in users in ways that you can more deeply customize. The SDK is intended for cases where you need more control, like single-page apps, custom launcher buttons, dynamic context updates, or programmatic show/hide behavior.Get started on our Developer Portal.Happy coding!

We're building a way for external AI agents to operate as real teammates inside Front — assigned conversations, their own identity, clean handoffs to humans, and @mention support. No more webhook workarounds or human accounts standing in as proxies. If you've already built an agent or are actively working on one, we want to hear from you. We're in early development and looking to understand real use cases before we build. Interested? Join our beta group to get started.

Task conversations are now fully supported in the Core API. You can create, read, and update them just like you can other conversation types, with a dedicated description field for capturing the context of the task. To learn more about how tasks work in Front, refer to our Help Center.POST /conversationstype now accepts 'task' in addition to 'discussion' The subject field provides the title of the task comment is optional for tasks and required for discussions New optional description field, valid only when type is 'task'GET /conversations/:conversation_idResponse now includes a type field returning 'conversation', 'discussion', or 'task' Response includes a nullable description field, present only on task conversationsPATCH /conversations/:conversation_idNew description field to set or clear (null) the task descriptionGive it a spin and let us know what you build!Happy coding!

UPDATE: There’s a new version of the MCP server. Please join the following group to learn how to get started: https://community.front.com/groups/beta-mcp-server-83The data access note for the original MCP server does not apply to the new one linked above. We're excited to announce the beta release of the Front MCP server — and we'd love for you to try it.Model Context Protocol (MCP) is an open standard that lets AI applications securely connect to external data sources and tools. With the Front MCP server, AI-powered tools like Claude, Cursor, Windsurf, and others can interact directly with your Front account and API documentation using natural language — no manual API calls required.What does that look like in practice?Ask your AI assistant to pull open conversations from a specific inbox, then tag or triage them Query your Front account data in real time to inform what you're building Explore Front's API endpoints and get full details about specific ones — without digging through doc

We've added a set of Time Off API endpoints to help you build integrations that stay in sync with teammate availability in Front. What is Time Off?A time off represents a scheduled out-of-office period for a teammate in Front. While active, the teammate's status switches to Out of office and any configured auto-responder starts replying to inbound messages on their behalf. When the period ends, their status returns to Available automatically. What you can buildThe Time Off API lets you read and manage these scheduled periods programmatically. A few example use cases:Surface upcoming absences in a workforce management tool Sync time off data with your HRIS Skip unavailable teammates when routing work from an external systemEndpointsGet time off List teammate time offs List team time offs Create time off Update time off Delete time offFor full reference docs, check out our Developer Portal.For an end-user overview of how time off works in Front, see Time off in the Help Center. Happy cod

 If you've been looking to bring voice calling into Front, we just made it a lot easier to get started. We've published a voice channel template on GitHub that gives you a working foundation for building a full voice application channel integration — without starting from scratch.What the template coversAuthorizing Front users connecting to your channel via OAuth Instantiating a new channel and handling the webhook lifecycle Processing call status events (ringing, connected, hold, transferred, hangup, and more) Syncing call assets — transcripts, recordings, and summaries — back into Front conversations Displaying incoming call notifications to teammates via a sidebar plugin and managing the call lifecycle from thereThe template is built in TypeScript with Node and Express, but the architecture is straightforward enough to adapt to your language of choice.Getting startedThe repo includes a quickstart README if you want to get the code running before diving into the details, and a full t

You can now run sidebar plugins in the background by enabling the Run in background setting when you configure a plugin feature in your developer app. While this setting currently only supports voice channels through the new displayNotification and dismissNotification Plugin SDK functions, please leave us a comment about other use cases you’d like us to support so that our Product team can prioritize! Happy coding!

We've revamped the Connectors Academy course to reflect all the recent improvements to the no-code framework—and this time, you'll build something you can actually use right away.The updated course walks you through building a Connector with Asana that lets teammates create a new task in Asana directly from Front. Along the way, you'll learn how to:Chain multiple app requests together to pull in workspaces, projects, and tasks from Asana Build dynamic dropdown menus that let teammates select the right project, task, or any other context—adaptable to any use case, like selecting the correct order for a customer! Use pagination and other new Connector features recently added to the platform Arrange complex logic visually in the flow builder, including using app request nodes to perform external actions without writing that logic inside a dynamic variableHead over to the course to access the new example, or view the full learning path if you’re new to Connectors.

 If you’re a customer or partner who has been using our APIs, SDKs, Connectors, channels, or any other platform touchpoint to build integrations or improve your workflow automations, we’re looking to partner closely with you to take your existing usage to the next level. Interested? Become one of our design partners: 

You can now add query string parameters to Connectors using a handy table. While you can still type query string parameters directly into the URL, the table makes it easier to see the parameter names and values, especially when you have multiple parameters. The URL has also been split into two rows (one for the domain and one for the rest of the endpoint) so that it’s easier to manage longer paths. This update applies to both application requests and application objects. We hope you enjoy it! 

You can now configure your app webhooks to use an authenticated server instead of a plain URL. While these requests have always been signed—which lets you tell if some imposter sent the notification instead of Front—they now can be authenticated, too.When you set up application webhooks with a server, customers will supply unique credentials when installing your published app:Allowing your webhook server to identify exactly which customer each event pertains to Meeting enterprise security requirements  One thing to note: Webhooks will fail to send if customers skip the Authentication tab during install, so make sure your setup guide tells them to complete it. Check out our webhooks documentation to get started.

Learn how to add search and pagination parameters to your app requests in order to power dynamic dropdowns in macros. These dropdowns allow your teammates to search for and scroll through a relevant list of results in order to select the external record they’re interested in. The walkthrough uses searching for charges in the Stripe API as an example.View the example below:  

You can now manage views programmatically via the Core API. Views are custom work queues that filter conversations by inboxes, tags, and assignees—helping users track high-priority conversations and ensure nothing goes unanswered. What you can do:List all views accessible to your token, or filter by teammate, team, or company Get, create, update, and delete views Configure filtering criteria including inbox IDs, tag IDs, and assignee IDs Add views to specific teammates' sidebars to make them visible in their navigationCommon use cases:Provision custom views for new team members during onboarding Standardize views across teams to ensure consistent workflows Dynamically create views based on external data or business logic Pin important views to teammates' sidebars automatically Manage views at scale across your organizationCheck out the full Views API documentation to get started, or learn more about how views work in Front in our Help Center.

You can now permanently delete conversations via the Core API using the new Delete conversation endpoint. Key details:Conversations must have status trashed before they can be permanently deleted This action cannot be undone Requires the conversations:delete scope Check out the full documentation for implementation details.

We're excited to announce that the Core API now supports granular permissions for API tokens and OAuth tokens. You now have fine-grained control over what your tokens can access and modify, helping you follow the principle of least privilege and improve your integration's security.  How It WorksWhen you configure a token, you'll specify Features (what functionality the token can use), Namespaces (the scope of resources it can access), and Permissions (what actions it can perform for each resource it has access to). Granular PermissionsYou can now granularly control access for each resource type:Read – Retrieve resource information Write – Create and update resources Delete – Remove resources Send – Create and send messages that start new conversations or reply to active ones (note: importing historical messages only requires Write permission) Best Practices✅ Limit permissions to only what your integration needs to prevent misuse or security issues✅ Check the Core API reference document

Join Front’s community team for three hands-on Connectors workshops in January! Follow along as we automate workflows between Front and your 3rd-party tools. January 15: Salesforce <> Front workflows: Use Connectors to update Salesforce objects directly from your inbox. January 22: HubSpot <> Front workflows: Use Connectors to easily manage customer data in HubSpot. January 29: Jira <> Front workflows: Use Connectors to create Jira tickets from Front with just a few clicks. Register nowCan’t make it? No problem! Join the community group to access self-paced examples and view the workshop videos later. Note: To access Front pre-built Connectors, you must be on the Professional plan or above.

We're excited to announce the launch of our new API analytics dashboard! You can now get a visual overview of your Core API request patterns and rate limiting directly in Front. This dashboard makes it easy to monitor your Core API consumption over time, quickly identify which endpoints are generating the most traffic, and spot where you might be hitting rate limits—all without having to piece together information from logs or error messages.  The dashboard features interactive time-series charts showing your total Core API calls (with rate-limited requests clearly highlighted) and an endpoint breakdown table that shows usage by path, including call counts and rate limit hits. You can view data for the last 30 days and drill down into specific time periods. Company admins can access it by navigating to Settings > Developers > API analytics. We hope this gives you better visibility into your integration's performance and helps you optimize your API usage!

We're thrilled to announce a major improvement to how you build macros with Connectors: app request nodes are now available in your flow builder. No more hunting through dynamic variable menus or trying to figure out where to nest your app requests inside action nodes. You can now drop an app request directly into your macro flow by clicking the plus (+) sign and selecting "Send app request"—just like any other node. This makes building Connector-powered workflows far more visual and intuitive.View the docs for step-by-step instructions!  Each app request node comes with built-in success and failure paths, so you can immediately see how your workflow branches based on the request outcome. Want to chain multiple requests together? Send a success message to your teammates? Branch based on output values? You can now build these flows exactly how you envision them, with complete flexibility. Plus, your app request outputs automatically become dynamic variables that you can use anywhere dow