Codat developer update — Q3 2024
Review the upcoming changes and deprecations we announced this quarter, get ahead of them, and see what's new with Codat's products.
Product updates
UI improvements to connection flows
We have revised and improved the user interface of the connection flows for NetSuite, Sage Intacct, and QuickBooks Desktop. The updated connection flows are already available to all our clients that have these integrations enabled.
Your business customers will benefit from a clean design, improved and simplified copy, and linking journey support that includes deep links, end-user documentation, and autogenerated values.
Webhooks update: new event types
We're excited to introduce our improved webhook event types. They add context to our webhooks, allow you to increase the precision of your webhook messages, and provide detailed insights into the trigger events. They also use the payload structure recommended by the Standard Webhooks specification.
Introducing company tags
We've enhanced our company data model with a tags object. Tags provide a simple way to include additional information about a company.
For example, you can use tags to set a foreign key, define an operating region, or specify details about the financial services the company has requested. Each company can store up to 10 tags. This feature is available to all clients today.
Changes planned for January 10, 2025
Deprecation of legacy QuickBooks Desktop Integration
We have recently released our updated QuickBooks Desktop connector. It simplifies your customer’s linking journey and provides more resilient data acquisition.
As a result, we will be deprecating the legacy connector on January 10, 2025. Migrate your existing QBD connections to the new connector to continue syncing data with QBD after the deprecation.
Deprecation of legacy webhook event types
On January 10, 2025, we will deprecate our legacy rule-based webhooks service following the release of our new webhooks service and webhook event types.
If you are using our legacy rules-based webhook service, migrate to the new webhooks service to continue receiving notifications from us.
Deprecation extension for webhook changes
We previously announced the following deprecations after the release of our new webhooks service:
- Deprecation of /rules/alerts endpoints
- Deprecation of RuleId in rules webhooks
- Deprecation of rule-based email notifications
In our July developer update, we have extended the deprecation period to January 10, 2025. This deprecation is going ahead as scheduled on January 10, 2025.
Deprecation of legacy webhook event types
On January 10, 2025, we will deprecate our legacy rule-based event types following the release of our new webhook event types that provide more contextual information in the webhook payload.
If you are using our legacy rule-based event types, change your configuration to use the new event types instead and continue receiving webhook notifications.
Deprecation of company-specific webhooks
On January 10, 2025, we will deprecate company-specific webhooks delivered by our legacy rule services and replace them with company tags.
To continue receiving notifications, add the required metadata to the the company schema and update your webhook consumers to filter webhooks by company tags.
Changes to the bankFeeds.sourceAccount webhook payload
On January 10, 2025, we will update the payloads for the following event types to align with our new webhook schema definition:
bankFeeds.sourceAccount.connectedbankFeeds.sourceAccount.disconnected
If you are using these webhook event types, update your corresponding webhook consumers to handle the updated schema definitions.