My ideas: Core API

I'd like an endpoint to fetch a conversation via API using the Ticket ID. Use case is that we want to give information about a ticket to our customers and the people who help our customers in Discord. They know their inquiry by the Ticket ID. Thus...

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.

Please introduce API support for Linked Conversations ( https://help.front.com/en/articles/478144 )

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.

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/...

Ability to pull AI Summaries of a conversation via the API. Useful to leverage AI summarize feature

As a developer, sometimes it's hard to determine why my API requests are failing, and I need to reach out to the support team for assistance with my API usage. It would be super helpful to see logs of all API requests issued via my account in a da...