Kolleno uses Clio’s OAuth 2.0 Authorization Code flow.
An authorized Clio admin is redirected to Clio to approve access during the initial setup. Once approved, Clio issues secure tokens that Kolleno uses to access the API.
One-Time Admin Authorization
Authorization is completed once during setup by a Clio admin user. After this step, Kolleno does not require repeated logins or ongoing user interaction.
Token-Based API Access
All API requests from Kolleno to Clio include an access token using the Authorization Bearer header. This allows secure, continuous access without user credentials.
Token Handling and Security
Automatic Token Refresh
Kolleno securely stores the refresh token and uses it to automatically obtain a new access token when needed. This process happens in the background without customer action.
User Credentials and MFA
No Username or Password Storage
Kolleno does not store or use Clio usernames or passwords.
No MFA Codes Required After Setup
After the initial authorization, Kolleno operates entirely using OAuth tokens. MFA codes or prompts are not required for ongoing access.
When Re-Authorization Is Required
Re-authorization is only needed in specific cases:
The Clio admin revokes Kolleno’s access in Clio
The refresh token is deauthorized as part of access removal
The integration configuration changes and requires new consent