In your list of companies, you may see a connection that is Deauthorized.
There are many reasons for a deauthorization. This guide will explain the common reasons and show you way to find out the reason.
Audience
This guide is written for Codat Admins.
Pre-requisites
- Access to your Codat Portal account
- Finding the cause of deauthorization requires making API calls
What can cause a deauthorization?
- A change in the connected integration account. These include a change of credentials, removing authorization of Codat or uninstalling a Codat Ad-on\installed connector
- Not syncing for 90 days
- For banking connections, the open banking 90 day rule.
- In rare circumstances, outages in the connected integration
How to find the cause of a deauthorization
It is not always possible to determine the cause of a deauthorization. If we can detect a cause, you will see the cause on the dataConnectionErrors object on the /companies/{companyId}/connections endpoint.