Skip to main content

Authorization

Follow this guide to create a new Clio credential that will allow Nexla to authenticate to and exchange data with your Clio account.
clio_api_auth.png

Clio

Prerequisites​

Clio uses the OAuth 2.0 authorization code grant to authorize API access. Before creating a credential in Nexla, you must register a developer application in Clio to obtain a Client ID (also called the App Key) and a Client Secret (also called the App Secret). You must also identify the regional API endpoint that matches the data center where your Clio account is hosted.

Register a Developer Application in Clio​

A developer application represents your integration within Clio and provides the OAuth credentials that Nexla uses to authenticate. You must have administrator access to your Clio account to create and manage developer applications.

  1. Sign in to your Clio account, and navigate to the developer applications page for your region:

    • US: https://app.clio.com/settings/developer_applications
    • Europe: https://eu.app.clio.com/settings/developer_applications
    • Canada: https://ca.app.clio.com/settings/developer_applications
    • Australia: https://au.app.clio.com/settings/developer_applications

  2. Click the Add button to begin creating a new application.

  3. Enter the details for your application. The application name and description are shown to Clio users when they are asked to authorize the integration, so use clear, recognizable values (for example, "Nexla Integration").

  4. In the Redirect URI field, enter the Nexla OAuth callback URL: https://app.nexla.io/oauth/callback. This is the address that Clio redirects to after a user authorizes the application, and it must match exactly for the authorization to succeed.

  5. Select the OAuth scopes that grant access to the data your flows will read or write (for example, matters, contacts, activities, bills, tasks, and documents). Granting only the scopes you need follows the principle of least privilege and keeps your integration secure.

  6. Save the application, and make note of the generated Key and Secret.

    The Key corresponds to the Client ID and the Secret corresponds to the Client Secret that you will enter in Nexla. Store the secret securely—treat it like a password, as it grants access to your Clio data.

For complete information about registering developer applications and the OAuth flow, refer to the Clio Developer Documentation: Create a Developer Application and the Authorization guide.

Create a Clio Credential​

  • To create a new Clio credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Configure Clio OAuth2 Authentication​

Clio authentication uses the OAuth 2.0 authorization code grant, which is a three-legged flow that requires you to sign in to Clio and grant Nexla access during credential creation.

  1. Select the Base URL that matches the regional data center hosting your Clio account from the Base URL menu. Clio data is region-specific, so the correct endpoint is required for Nexla to reach your account:

    • US: https://app.clio.com/api/v4
    • Europe: https://eu.app.clio.com/api/v4
    • Canada: https://ca.app.clio.com/api/v4
    • Australia: https://au.app.clio.com/api/v4

  2. Enter the Key value from your Clio developer application in the Client ID field. This value identifies your integration to Clio.

  3. Enter the Secret value from your Clio developer application in the Client Secret field. This value authenticates your integration and should be kept secure.

  4. Click the Authenticate button to begin the OAuth authorization flow. You will be redirected to Clio to sign in (if you are not already signed in) and to review the requested permissions.

  5. Review the permissions, and click Allow Access to authorize Nexla. Clio will redirect you back to Nexla, and the access and refresh tokens will be stored automatically with the credential.

    Nexla automatically refreshes the access token using the stored refresh token, so you do not need to re-authorize the credential under normal operation. Re-authorization is only required if access is revoked in Clio or if the requested scopes change.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.