Changelog - April 2023
This month, our product and engineering teams have been working on expanding coverage across our existing integrations as well as introducing some exciting new features.
This month, our product and engineering teams have been working on expanding coverage across our existing integrations as well as introducing some exciting new features.
On the 24th July 2023, we will be deprecating the legacy version of Account Categories
and all related features, including:
We've improved our data type coverage for a number of integrations.
On July 10, 2023, Codat will deprecate the GET /metrics/companies
endpoint previously used to display the status of companies on the Portal dashboard.
On July 10, 2023, Codat will change the mappings for the Direct incomes data type for the QuickBooks Desktop on-premise connector.
On July 10, 2023, Codat will deprecate the use of bankAccounts
and bankTransactions
data types for syncing banking data connections via Plaid, TrueLayer and Basiq. The use of these data types for accounting data connections will remain unchanged.
See what's new in Codat this week
Some UAT domains have remained aliased to our production instance. These aliases will be disabled on the 1st November 2024.
If you are still pointing to, for example, https://api-uat.codat.io
, you should instead point to https://api.codat.io
.
Additional action required to link new companies in migrated Test accounts following the DNS switchover from UAT to Production
We've now switched over the existing public DNS for the UAT environment to point to Production.
In some scenarios, you now need to make minor configuration changes to the Redirect URIs used in your third-party developer apps. This is required in order to start linking new companies in your Codat Test account.
For details of the affected integrations and the Redirect URIs you need to add, see the Knowledgebase article.
A new product for easy syncing with bookkeeping software and ERPs, and other qualithy of life improvements.
On April 11, 2023, Codat will deprecate endpoints used to manage API keys. This is to support our extended API key management that allows multiple keys.