Skip to main content

Integration Troubleshooting Guide

Troubleshoot issues connecting your Practice, Case, or Document Management systems to Legl and resolve common integration errors.

Written by Shanté Simpson
Updated over a week ago

This guide supports firms and implementation partners using native or third-party integrations to connect Practice Management, Case Management, or Document Management systems with Legl.

❗ Never include authentication secrets e.g. API keys, over email communication


Clio (EU & AU) and ActionStep

If your integration is with ActionStep (EU or AU) or Clio (EU or AU), as a first step, please refer to our Clio and ActionStep troubleshooting resources.

If this does not resolve your issue, please contact [email protected] with the following details:

✅ Include in your email

  • Description of the issue

    • What is the name of the instance you are working in (the below example has 'Lucky Luke LLP')?

    • When does the issue occur?

    • Which users are affected, and which are not?

  • Screenshots showing the issue and the expected behaviour.

  • Impact of the issue:

    • Is this blocking operations entirely, affecting a workflow, or just a minor display issue?


Troubleshooting for Other Integrations

If your integration is not with ActionStep (EU/AU) or Clio (EU/AU), please follow the guidance below.

For Users

As a first step, please contact:

  • Your Legl Admin

  • Your Internal IT Support

In some firms, these may be the same team or person.

✅ Provide the following details to your Legl Admin and Internal IT Support

  • Description of the issue

    • What is the name of the instance you are working in?

    • When does the issue occur?

    • Which users are affected, and which are not?

  • Screenshots showing the issue

  • A description of expected behaviour

  • Impact of the issue:

    • What is this issue blocking? Is it a complete operational halt, a workflow error, or a UI bug?

Your internal IT team will determine whether the issue requires resolution from:

  • The Legl side

  • The middleware management side

  • Or the third-party platform side


For IT Administrators

If you have confirmed that the error originates from Legl’s APIs, please contact [email protected] and include:

✅ Include in your email

  • Description of the issue

    • What is the name of the instance you are working in?

    • When does the issue occur?

    • Which users are affected, and which are not?

    • What is the expected behaviour?

    • The API call being used and (if applicable) any error message returned.

  • Screenshots showing the issue

  • Impact of the issue:

    • What is this blocking? Is it a complete operational halt, a partial data sync issue, or a UI error?

  • Logs (if available):

    • Are API calls failing to Legl?

    • What are the status codes and timings?

Did this answer your question?