Implementing the “Add To Clio” workflow in your application doesn’t need to be a heavy lift. If you’ve built a working integration between Clio and your application, you’re already 90% of the way to supporting the Add to Clio functionality.
At its core, Add to Clio uses the same OAuth authorization flow that a “standard” integration uses. There are two key differences between the “standard” OAuth flow and the “Add to Clio” flow: where the user initiates the authorization process and where the user ends up when authorization is complete.
|
Standard OAuth Flow |
Add to Clio flow |
|
|
Where the user initiates the process |
Your application |
Clio Manage |
|
Where the user ends up after the process |
Your Application |
Clio Manage |
If you’ve already built your integration and the OAuth authorization flow, the steps you’ll need to build to support Add to Clio are as follows:
- Create a unique URL (the “Add to Clio URL”) that, when navigated to, prompts a user to sign up or log into your application and, after they’ve done so, starts the OAuth authorization process.
- Add logic to redirect to a specific Clio URL (
https://app.clio.com/app_integrations_callback) when someone in the “Add to Clio” flow completes the OAuth authorization process.
View the implementation guide is available here
After you’ve built those two pieces, the only thing left is to contact us at api.partnerships@clio.com to test and launch your Add to Clio flow.
Lastly: below is a diagram that walks through the “Add to Clio” flow and shows the overlap between it and the standard OAuth authorization flow used by all Clio integrations.
