What's new?

This section,

• Is a one-stop destination for us to communicate all the feature changes, upgrades, bug-fixes, and new app-building capabilities that we extend to our developers.
• Contains the changelogs of the current month. For older changelogs, see Dev Platform - changelog reference.

All release announcements in this section are tagged with one or more labels. The labels help understand the impact of the changes.

OAuth authorization and authentication for Freshworks APIs New feature

With this feature release, Freshworks APIs are accessible through the OAuth framework. Freshworks offers a mechanism to generate the OAuth credentials for your app. The app can use the credentials to request an authorization code, use the authorization code to request an access token, and use the access token to access the REST APIs.

Freshworks and Custom apps built using the FDK (v9.1.0 or above), as well as External apps built using third-party provisions can access the Freshworks APIs through OAuth.

Important:Currently, OAuth authorization and authentication is available only for Freshservice APIs.

We provide the following resources in this document to help you implement an OAuth flow in your app:

• How to implement the OAuth flow in a Freshworks app that intends to access Freshworks resources?
• How to implement the OAuth flow in an External app that intends to access Freshworks resources?
• How to implement the OAuth flow in a Freshworks app that intends to access third-party resources?

Also, we support multi-OAuth configurations using which you can implement the OAuth flow in an app that intends to access,

• Multiple third-party OAuth-secured resources, or
• Third-party OAuth secured resources and Freshworks resources.

New product event: The list of product events to which an app can subscribe and react has been enhanced. The onAgentCustomStatusUpdate is a new product event to which the apps can subscribe.

Platform version 3.0 and FDK 9.1.0 Platform version upgrade

What is new? Well, everything!

With this beta release, we present a new way of building apps. You have an app use case. You have zeroed in on the Freshworks product that can benefit from the use case. Imagine building one app such that it works not just for one of Freshworks products but for all products that have the feature related to the use case. Let us call this app a global app.

How have we facilitated building a global app? We have broken down all Freshworks products into functional units called modules. Through the new platform version, we have provided the capabilities to build an app that extends a module's functionality or extends multiple modules' functionalities.

To meet the evolving customer requirements, Freshworks offers business SKUs. A SKU is a bundling of compatible products. A global app that you build is available across SKUs. After we review and publish your app to our Marketplace, the app can be installed and used with any SKU that has the module(s) that your app works with. The only condition is, as part of the SKU subscription, the app user must have subscribed to a plan that has the product (module) compatible with your app.

We understand that as developers moving from a product landscape to a functional-module landscape you might face difficulties. We aim to make the transition easy through an intuitive FDK experience and comprehensive documentation. Global app concepts might be a good starting point.

This is a beta-release document. In the coming days, we are going to keep our eyes and ears open to get feedback from our beta app developers and update content accordingly. In your journey of building a global app, we hope to bring to you the best developer experience.