Core API

We’d like the ability to programmatically close conversations using the Front API. Right now, the API allows updating a conversation’s status to archived, but there’s no way to mark it as closed. This creates a challenge for teams like ours who re...

As the title suggests, getting this information is helpful to display it in external systems, feed it into LLMs for account insights, and more.

The new tasking system is not easy to use - it takes multiple clicks to make a task. Allow auto creation via API or Front rules

Currently the Get Message endpoint for Front's Core API does not allow lookup on the external ID field. It would be nice if we allowed lookup on the external_id as a resource alias much like the GET Account endpoint.

Today we need to get for each conversation what is the status and if status is resolve when it was resolved. Unfortunately we cannot retrieve this information using the end-point GET List Tagged Conversations or any other end-point. In addition we...

I regularly need to fetch Teammate Activity Export data - it would be useful to enable access via the API

Internal comments can be added, but currently cannot be deleted via the Core API.

At present, Front API/OAuth tokens have very wide permissions, such as the "Shared Resources" token scope allowing read+write access to all shared resources. To help improve security, it would be great to support more granular scopes such as read/...

Allow to set a value to the reply-to email header when creating a new email - at least when we create that email through api : https://www.getresponse.com/help/reply-to-field.html