What is happening?
Clio’s API allows our customers and third-party developers to create custom applications and integrations that extend Clio’s core functionality.
Clio makes regular updates to our API. This includes releasing new versions of the API, and dropping support for older versions. In October 2017, version 2 (v2) of Clio’s API received a major upgrade. We are now requiring all of our customers, developers, and partners to use the upgraded version (v4).
Some of the improvements made to Clio’s API v4 include:
Clio’s API v4 has been built to meet modern security standards. Clio’s API v2 can be considered less secure than Clio’s API v4, especially if customers and developers have not been diligent in their use of API v2.
Clio’s API v4 includes several key performance and reliability improvements. Clio’s API v2 had the potential to reduce Clio’s stability and increase load times as Clio’s user base continues to grow larger.
Since the introduction of Clio’s API v4, Clio’s API v2 has continued to require testing, support, and consideration from our development team. We hope that dropping support for API v2 will allow us to increase the frequency and quality of the new features and bug fixes that we add to Clio.
When is the API v2 deprecation happening?
October 10, 2017: Clio announced the availability of API v4, and the impending deprecation of API v2.
October 2017 - October 2018: Clio has sent several pieces of communication to our registered application developers; reminding them of this change and providing them with advice for migrating their applications.
October 15, 2018: Clio prevented new applications from being created that use API v2.
November 21, 2018: Clio prevented existing API v2 apps from adding new users or accounts.
January 1, 2019: Clio’s API v2 will stop working for all third-party applications.
How do I prevent the API v2 deprecation from affecting my Clio account?
1. Check if your account has been impacted.
- On October 24th, 25th, and 26th, 2018, we sent an email to all of the Clio customers that were still using a custom-built application connected to Clio via API v2.
- Reference the list of integrations below to see if you are using an integration that has an API v4 version of your application ready for you to use.
If you are unsure whether or not your account will be impacted and you would like to check on the status of your account, please contact Clio’s API support team by emailing firstname.lastname@example.org.
2. Understand how your account has been impacted.
If your Clio account is connected to an application that will be impacted by the API v2 deprecation, this means that the workflows, processes, automations, integrations, or reports serviced by that application will stop functioning when Clio drops support for API v2 on January 1st 2019.
3. Decide how you will respond.
Once you have identified the workflow(s) that will be impacted by the API v2 deprecation, you must decide how to mitigate the impact of this change. You have several options:
Reauthenticate into the API v4 version of your integration
Some integrations have been updated to work with v4, but your account may not be using the updated version. You should re-authenticate the integration and allow it to access data from your Clio account through API v4.
Note: This list is limited to integrations that have not yet updated from API v2 to API v4. There are many integrations in Clio’s App Directory that did not require an update; and those applications are not included in this list.
The list of apps that have not yet been updated to use Clio’s API v4 is:
- Click to File for Outlook/ Mac Mail
- Message Hub
If your application is listed above, the migration from API v2 to v4 is likely still in progress and should contact your integration's developer for assistance or proceed with one of the options listed below:
Migrate your application to v4
Clio has sent several pieces of correspondence to your application’s developer over the past year, reminding them of this deprecation. However, you may have success contacting them directly to make the necessary code changes to your application.
Replace your application with an equivalent solution
There may be an approved third-party application in Clio’s App Directory that is capable of replacing your current application.
Adopt a new workflow
If you can not migrate your application to v4 or replace it with another solution, you must find an alternate method of servicing your affected workflow. We recommend evaluating Clio’s Zapier integration as a user-friendly way to build custom integrations.