Skip to main content

Ideas
Product updates
Events
Groups
Partners
Academy

Home
Discussions
Developers
API news & updates

API news & updates

Learn about the latest updates to the Front Platform

39 Topics
15 Replies

When you subscribe we will email you when there is a new topic in this category

39 Topics

Recently active

Most replies Most views Newest first

Javier - Developer RelationsCommunity Manager

published in API news & updates

Knowledge base API is now live!CORE API UPDATE

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.

xdmnlFronteer

published in API news & updates

Bug fix: Updating conversation status via the APICORE API

The Update conversation endpoint now correctly updates conversation statuses in personal inboxes. Before the update, the status update would only be applied at the team-level. The status update did not affect private conversations or propagate to the conversation assignee.From now on, the conversation status update will follow the behavior of our rule engine: the status update will be applied to the conversation assignee and owners for private conversations in addition to the shared inbox at the workspace level. This update will gradually be released to all customers over the next week. Please comment below if you want to access it immediately. PS: The update only impacts the conversation status for assignee and private conversation owners. It does not impact the status of the conversation for its followers (participants who are not the assignee or owner of the private conversation).

Javier - Developer RelationsCommunity Manager

published in API news & updates

Front will begin disabling application webhooks that do not respond successfullyIMPORTANT

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.

Richard Developer PlatformFronteer

published in API news & updates

You can now manage teammate groups via the APICORE API UPDATE

We are excited to announce that you can now manage teammate groups via the Core API! Teammate groups allow you to create centralized lists of users that make it easier to manage shared inbox and contact access. We’ve added 14 endpoints to help you fetch, create, update, and delete teammate groups or related access like inboxes or teammates within the group. Some example endpoints include:List teammate groups Create teammate group Add teammate group team inboxes Add teammate group teammates Add teammate group teams Check out our Developer Portal for the full list of endpoints. Happy coding!

kapFronteer

published in API news & updates

You can now update and pin comments via the APICORE API UPDATE

We are pleased to announce that the Core API now supports:Updating comments via the API—Using the comment ID, you can update the body or the pinned status of the comment. Controlling whether a comment is pinned in the conversation—A pinned comment is displayed in the pinned comments link within the conversation UI. You can mark a comment as pinned via the API using the new is_pinned field, which is available when adding or updating a comment and in all comment responses. Let us know if you have any feedback in the comments below, no pun intended.

Javier - Developer RelationsCommunity Manager

published in API news & updates

Another update on Chrome's third-party cookie deprecation affecting Front pluginsIMPORTANT

On July 22, 2024, Google released a blog post indicating that regulators may allow the continued use of third-party cookies if users opt into them. If this turns out to be the case, it will still be important to provide alternatives to third-party cookies for those users who do not consent to the use of third-party cookies, as noted in our original post. However, Google continuing to support third-party cookies would allow you to keep using these cookies in Front plugins if you have control over the browser decisions of your users (if all your plugin users belong to your company, for example).

Javier - Developer RelationsCommunity Manager

published in API news & updates

Introducing connectors, the evolution of dynamic objectsCONNECTORS

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

Javier - Developer RelationsCommunity Manager

published in API news & updates

Please update your Highway dynamic object configurationDynamic Objects

Highway Integration Enhancements: New "spoof warning" workflow and cleaner dynamic object variables If you had configured the Highway dynamic object configuration per our tutorial prior to May 31st, 2024, then the configuration contained errors that could lead to false positives for the fraud use case described in the tutorial. It also did not include the spoof warning property from the Highway API. Our tutorial now reflects the correct setup, and we’ve created a migration guide to make it easier to know exactly what changes to make (limited only to the fraud use case). When you complete the changes, your dynamic objects will look like: Let us know if there are any questions!

Javier - Developer RelationsCommunity Manager

published in API news & updates

How to prepare for phone number normalization in the Front APIIMPORTANT

On September 1st 2024, we will be introducing E.164 phone number normalization to the Front API to address issues caused by inconsistent phone number handles attached to contacts. Phone number handles for contacts in Front can be created via the API, the Front contacts manager, incoming messages in channels, CRM contact syncs, and CSV import of contacts. With so many different ways of creating contacts and storing phone numbers for those contacts, it’s important to normalize the data because the different input formats can lead to duplicate contacts and related search issues. To prepare for this change, make sure your API requests (including those made through the Zapier integration) are sending valid phone numbers with the country code included. Country codes must be preceded by a plus (+) sign. Read the “Potential impacts” section below for details.If you experience any issues with phone number normalization, reach out to us and we can roll the feature back for your company instance

Javier - Developer RelationsCommunity Manager

published in API news & updates

An update on Chrome's third-party cookie deprecation affecting Front pluginsIMPORTANT

Based on recent developments, we’ve updated our original post on handling Chrome’s third-party cookie deprecation to note the following:Google has postponed the deprecation to Q1 2025 (originally Q3 2024) We now also recommend the Storage Access API as a viable solution to handling the deprecation, in addition to CHIPS. More details in the original post. We’ve linked to an example of handling partitioned cookies in Next.js for a Google Sign In authentication flow.

Javier - Developer RelationsCommunity Manager

published in API news & updates

Update your Postman collection linksIMPORTANT

Due to breaking changes in Postman, the Postman collections previously supplied in our Developer Portal can no longer push changes to forks. To obtain the latest Postman collections of our Core API and Channel API, create new forks from the following links:Core API collection Channel API collection These forks should be able to pull changes as expected whenever we update the source collection. Thanks for being part of our Front developer community!

Javier - Developer RelationsCommunity Manager

published in API news & updates

Dynamic objects now leverage the rule systemPLATFORM UPDATE

Dynamic objects are now integrated with rules. This means that you can use Front’s powerful rule system to customize when and how dynamic objects apply to your workflows. IMPORTANTRules have been auto-generated for all existing dynamic object configurations. These auto-generated rules have been named Create dynamic objects. While you are welcome to edit these rules, please note that disabling or deleting these rules will stop the associated dynamic objects from working. Where to manage dynamic object rulesYou can manage existing dynamic object rules from Settings > Company name / Workspace name > Rules. As noted in the above callout, dynamic objects that you created prior to March 12th, 2024 will have auto-generated rules named Create dynamic objects associated with them, but the rules you create from this point forth will be named whatever you choose to name them. If you create a dynamic object for the first time and no rule has been created before, the “Dynamic object config

kapFronteer

published in API news & updates

Sort conversation messages by created dateCORE API UPDATE

You can now sort messages returned by the List conversation messages endpoint by their creation date.The endpoint now includes the query parameters sort_by and sort_order. Set sort_by to created_at, and then specify whether you want the sort_order to return messages as asc (oldest first) or desc (newest first) results.

Javier - Developer RelationsCommunity Manager

published in API news & updates

Replacing third-party cookies in Front pluginsIMPORTANT

In a significant move towards enhancing user privacy, major web browsers are on a trajectory to deprecate support for third-party cookies to limit cross-site tracking. This shift has notable implications for developers of Front custom plugins or third-party integrations that rely on third-party cookies for authentication and other functionalities. Understanding this transition is crucial to ensure the continued seamless operation of your plugins once third-party cookies are fully deprecated. Note: On July 22, 2024, Google released a blog post indicating that regulators may allow the continued use of third-party cookies if users opt into them. If this turns out to be the case, it will still be important to provide alternatives to third-party cookies for those users who do not consent to the use of third-party cookies, as noted in the rest of this article. However, Google continuing to support third-party cookies would allow you to continue using these cookies in Front plugins if you hav

Javier - Developer RelationsCommunity Manager

published in API news & updates

Breaking changes to the Analytics endpointIMPORTANT

We are making a breaking change to the Create a new analytics export endpoint offered by our Core API. The endpoint will now require you to specify the columns that will be present in the export. Previously, the endpoint generated an export that included all available columns. In addition, three columns will be deprecated from the export: Resolution time, Replies to resolve, and Final resolution. You should use Total reply time, Replies to resolution, and Stage resolution time instead. Why are we making these changes?We are making these changes for the following reasons:By explicitly specifying the columns you need in the export, future additions to the available columns will not affect your export. This ensures backwards compatibility as we continue to enrich the Analytics data. Customers who need a subset of columns in their exports can benefit from faster exports and smaller response sizes. The Resolution time, Replies to resolve, and Final resolution columns are being deprecated b

Javier - Developer RelationsCommunity Manager

published in API news & updates

[us-west-1] Scheduled database maintenance on Jan. 7thIMPORTANT

Between Sunday 2023-01-07 0800 UTC and Sunday 2023-01-07 0900 UTC, customers in our us-west-1 data center region may experience a disruption to the following features:* Full text search* Contacts manager* Autosuggest in the composer including: recipients, tags, inboxes, and teammates* Certain parts of the settings UI including: search, teammates, inboxes, channels, rules, views, tags, time off and shifts* Conversation audit trailThis is due to planned maintenance work required on a core database service.What is the impact?During the window, parts of the app experience will be degraded or unavailable. The display of new messages in search, events in search, and autosuggest resources in search will be delayed.Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disruption to customers.What will the exact experience be for our c

Javier - Developer RelationsCommunity Manager

published in API news & updates

[eu-west-1] Scheduled database maintenance on Dec. 31stIMPORTANT

Between Sunday 2023-12-31 0200 UTC and Sunday 2023-12-31 0300 UTC, customers in our eu-west-1 data center region may experience a disruption to the following features:* Full text search* Contacts manager* Autosuggest in the composer including: recipients, tags, inboxes, and teammates* Certain parts of the settings UI including: search, teammates, inboxes, channels, rules, views, tags, time off and shifts* Conversation audit trailThis is due to planned maintenance work required on a core database service.What is the impact?During the window, parts of the app experience will be degraded or unavailable. The display of new messages in search, events in search, and autosuggest resources in search will be delayed.Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disruption to customers.What will the exact experience be for our c

Javier - Developer RelationsCommunity Manager

published in API news & updates

[us-west-2] Scheduled database maintenance on Dec. 31stIMPORTANT

Between Sunday 2023-12-31 0800 UTC and Sunday 2023-12-31 0900 UTC, customers in our us-west-2 data center region may experience a disruption to the following features:* Full text search* Contacts manager* Autosuggest in the composer including: recipients, tags, inboxes, and teammates* Certain parts of the settings UI including: search, teammates, inboxes, channels, rules, views, tags, time off and shifts* Conversation audit trailThis is due to planned maintenance work required on a core database service.What is the impact?During the window, parts of the app experience will be degraded or unavailable. The display of new messages in search, events in search, and autosuggest resources in search will be delayed.Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disruption to customers.What will the exact experience be for devel

Javier - Developer RelationsCommunity Manager

published in API news & updates

Dynamic objects sample code availableNEW SAMPLE CODE

We are excited to announce the release of sample code that demonstrates how to augment dynamic objects with information fetched from a server or API. The code also demonstrates how to verify that requests to the server are coming from Front. We hope this code is useful and results in more powerful dynamic object use cases for customers!

Javier - Developer RelationsCommunity Manager

published in API news & updates

Event limit added to analytics exportsCore API Update

The Fetch an analytics export endpoint now enforces a maximum of 5,120,000 events or messages within a single export. If your export exceeds this number, the API will return a response with the status parameter set to too_big. To address this scenario, reduce the time period of the export and fetch it again.

Javier - Developer RelationsCommunity Manager

published in API news & updates

[us-west-1] Downtime / maintenance affecting conversations API endpointsIMPORTANT

Between Sunday 2023-11-19 0800 UTC and Sunday 2023-11-19 0900 UTC, customers in our us-west-1 data center region may experience an interruption to loading conversations, loading conversation lists, and reopening conversations from an integration. This is due to planned maintenance work required on a core database service. What is the impact?During the window, the conversations viewing experience will be degraded or unavailable. The display of new messages, counter updates of all workspaces, and some asynchronous conversation mass-actions will be delayed. Developers trying to use the API via integrations may receive a 503 "service unavailable" error in their list conversations responses during the interruption. This should be resolved once the maintenance is complete. Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disrup

Javier - Developer RelationsCommunity Manager

published in API news & updates

[eu-west-1] Downtime / maintenance affecting conversations API endpointsIMPORTANT

Between Sunday 2023-11-12 0200 UTC and Sunday 2023-11-12 0300 UTC, customers in our eu-west-1 data center region may experience an interruption to loading conversations, loading conversation lists, and reopening conversations from an integration. This is due to planned maintenance work required on a core database service. What is the impact?During the window, the conversations viewing experience will be degraded or unavailable. The display of new messages, counter updates of all workspaces, and some asynchronous conversation mass-actions will be delayed. Developers trying to use the API via integrations may receive a 503 "service unavailable" error in their list conversations responses during the interruption. This should be resolved once the maintenance is complete. Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disrup

Javier - Developer RelationsCommunity Manager

published in API news & updates

New Core API export applicationNew Sample Code

We now offer a sample application that demonstrates how to export conversations and messages from Front! The application demonstrates: Listing all inboxes Searching for conversations Applying filters to the conversation search Handling pagination of results from the Core API Export all conversations with messages and attachments included Applying rate limit handlers Check out the application and GitHub source code on our Developer Portal.

xdmnlFronteer

published in API news & updates

Custom fields + .eml messages added to the APICore API Update

Custom Fields in the Core APIThe Core API now exposes endpoints to list the custom fields that can be used on different resources:Use GET /accounts/custom_fields to list the custom fields available on an Account (docs). Use GET /contacts/custom_fields to list the custom fields available on a Contact (docs).Use GET /conversations/custom_fields to list the custom fields available on a Conversation (docs). Use GET /inboxes/custom_fields to list the custom fields available on an Inbox (docs). Use GET /teammates/custom_fields to list the custom fields available on a Teammate (docs). In addition, the Custom Field data model now returns all the supported values for the Custom Field of type enum. Accessing email messages in the .eml formatThe Get message (GET /messages/:message_id) endpoint now supports customizing the response's Content Type.By default, the endpoint returns the documented JSON data. However, you can now request the response to contain the message in the .eml format by setti

Javier - Developer RelationsCommunity Manager

published in API news & updates

[us-west-2] Downtime / maintenance affecting conversations API endpointsIMPORTANT

Between Sunday 2023-10-22 0700 UTC and Sunday 2023-10-22 0800 UTC, customers in our us-west-2 data center region may experience an interruption to loading conversations, loading conversation lists, and reopening conversations from an integration. This is due to planned maintenance work required on a core database service. What is the impact?During the window, the conversations viewing experience will be degraded or unavailable. The display of new messages, counter updates of all workspaces, and some asynchronous conversation mass-actions will be delayed. Developers trying to use the API via integrations may receive a 503 "service unavailable" error in their list conversations responses during the interruption. This should be resolved once the maintenance is complete. Why are we doing this?One of our core database clusters needs to be restarted during the maintenance window while we perform an important security upgrade. We are doing this type of work during off-hours to minimize disrup

1
2

Page 1 / 2

Badge winners

mhumphreyshas earned the badge Innovator
mhumphreyshas earned the badge Brainy
marlita_privettehas earned the badge Innovator
isaiah_lhas earned the badge Innovator
april.lackpourhas earned the badge Innovator

Show all badges

Powered by Gainsight

Terms & Conditions Cookie settings

Sign up

Already have an account? Login

Use your Front credentials

Log in with Front

or

Username *

E-mail address *

First Name *

Last Name

(Private)

Only you and moderators can see this information

*

Job Title *

Company *

User Type (select all that apply) *

Team

Password *

I certify that I am not a bug bounty hunter, and that I have reviewed and accept the Front Community Terms and Conditions and the Front Privacy Notice.

I will not engage in any sort of penetration testing. I understand that creating a community account as a bug bounty hunter forfeits my right to receive bounties, and opens me to legal, financial, and criminal prosecution.

loginBox.register.email_repeat

Login to the community

No account yet? Create an account

Use your Front credentials

Log in with Front

or

Username or Email

Password

Remember me

Forgot password?

Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

Enter your e-mail address

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

OK

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

OK