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 connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. flows
We have revised and improved the user interface of the connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. flows for NetSuite, Sage Intacct, and QuickBooks Desktop. The updated connectionConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. 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 linksLink The authorization flow that allows end users to connect their accounting, banking, or commerce platforms to your application via Codat., end-user documentation, and autogenerated values.
WebhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. update: new event types
We're excited to introduce our improved webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. event types. They add context to our webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status., allow you to increase the precision of your webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. messages, and provide detailed insights into the trigger events. They also use the payload structure recommended by the Standard Webhooks specification.
Introducing companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. tags
We've enhanced our company data model with a tags object. Tags provide a simple way to include additional information about a companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources..
For example, you can use tags to set a foreign key, define an operating region, or specify details about the financial services the companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. has requested. Each companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. 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 connectionsConnection A link between a Codat company and a data source (like an accounting platform). Each connection represents authorized access to pull or push data from that platform. to the new connector to continue syncing data with QBD after the deprecation.
Deprecation of legacy webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. event types
On January 10, 2025, we will deprecate our legacy rule-based webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. service following the release of our new webhooks service and webhook event types.
If you are using our legacy rules-based webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. service, migrate to the new webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. service to continue receiving notifications from us.
Deprecation extension for webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. changes
We previously announced the following deprecations after the release of our new webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. 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 webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. 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 webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. payload.
If you are using our legacy rule-based event types, change your configuration to use the new event types instead and continue receiving webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. notifications.
Deprecation of companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources.-specific webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status.
On January 10, 2025, we will deprecate companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources.-specific webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. delivered by our legacy rule services and replace them with company tags.
To continue receiving notifications, add the required metadata to the the companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. schema and update your webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. consumers to filter webhooksWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. by companyCompany In Codat, a company represents your customer's business entity. Companies can have multiple connections to different data sources. tags.
Changes to the bankFeeds.sourceAccount webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. 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 webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. event types, update your corresponding webhookWebhook An automated notification sent from Codat to your application when specific events occur, such as when data syncs complete or connections change status. consumers to handle the updated schema definitions.