Discussions may now be created with the POST /conversations endpoint.

Fixed

The create comments endpoint, POST /conversations/:conversation_id/comments, no longer requires an author_id parameter. If the author_id is omitted, the comment will be posted using a specialized bot teammate representing the entity that made the request - either an OAuth client or an API token.

Update Channel now supports updating certain channel settings for channel types other than custom:

As part of our ongoing investments in the performance and intuitiveness of Front analytics, the analytics feature was revamped earlier this year. As part of that revamp, we have deprecated the endpoints that supported the legacy analytics, in favor of new endpoints that align with the latest capabilities of the analytics feature. The deprecated routes will be removed on June 24th, 2022.

As communicated earlier in a previous changelog entry, Topics have been renamed to Links in the Front API as of October 31, 2021. We will begin a progressive rollout of the removal of the topics field from the Conversation model and the link field from the Link model on November 9, 2021.

As communicated earlier in a previous changelog entry, Topics have been renamed to Links in the Front API as of October 31, 2021. The legacy topics links have been removed from the API.

To improve the performance and reliability of the API, we will be removing the last_message field from the Conversation model on June 6th, 2022. As of today, the field is considered deprecated and replaced with the last_message key in the _links.related object.

Message templates (previously referred to as 'responses' or 'canned answers') and message template folders now expose a number of additional endpoints. These endpoints make it possible to bulk upload or sync message templates from any external service.

Comment endpoints now support attachments when creating or fetching them.