News

Freshservice API v1 Deprecation Reminder

Related products: Freshservice

Hello everyone,

This is a gentle reminder about the upcoming API V1 deprecation. As mentioned in our earlier communication in November ‘22 about the migration cycle, Freshservice API v1 endpoints will be inaccessible after May 31, 2023.

IMPACTED MODULES
 

Freshservice admins are expected to verify that if API V1 end-points are used in any of the below modules,
 

  1. Workflow Automator ( Web Request nodes and “Trigger Webhook” Action nodes)

  2. Custom apps

  3. Portal Customization

  4. Any custom services or middleware developed using Freshservice APIs

 

Please update the code base from API v1 to V2 at the earliest with the help of our API V2 documentation.
 

HOW TO IDENTIFY API V1 ENDPOINTS?
 

To ensure a smooth transition, we have introduced visual cues in the user interface to update API v1 endpoints with the corresponding API v2 endpoints.Here are a few resources to help you migrate to API v2 endpoints:
 

1. Mappings from API v1 to v2
 

2. Solution article to help migrate Freshservice configurations to API v2


WHAT HAPPENS AFTER THE DEPRECATION DATE?
 

After May 31, 2023, all the workflow automators, portal customization, and custom apps using v1 endpoints will stop working, and your configurations will fail. Henceforth, all API calls must be made using the API v2 endpoints.


HAVE QUERIES?

Our teams can assist if you have questions about the migration or encounter any challenges. Please contact support@freshservice.com, and we’d be happy to assist you anytime.

Join the Community or User Group to Participate in this Discussion