Updates

Following the release of version 2.0 of our Zapier app, we will deprecate version 1.0 on April 10, 2025. To ensure uninterrupted service, update your existing Zaps to the latest version.

We have introduced a new PATCH endpoint, designed to let you update specific company properties without impacting others. For most scenarios where you are currently using the PUT endpoint, we recommend switching to PATCH to enjoy greater flexibility and precision when updating company details.

What's new?​

With the new PATCH endpoint, you can:

• Update one or more specific properties without overwriting properties not included in the request.

To clarify the distinction between these methods, we've updated their names:

• PATCH -> Update Company
• PUT -> Replace Company

Who is this relevant for?​

This feature is ideal for users who need to make partial updates to a company's details without replacing the entire record.

How to get started?​

To start using the PATCH method either:

• Use our client libraries - leverage our libraries for quicker implementation and reduced maintenance.
• Update your existing libraries - if you're already using our client libraries, just update to the latest version, and the update method will automatically use PATCH.
• Review the API reference - find detailed examples and usage guidelines to ensure a seamless integration.

Learn more about our libraries and start streamlining your updates today!

We’re excited to announce that our Zapier integration now supports subscriptions to the latest webhook event types, making it easier than ever to automate your workflows.

What's new?​

• Subscribe to our latest event types - stay updated with the newest triggers available.
• Multiple subscriptions - subscribe to one or more event types at the same time.
• New webhook schema - take advantage of our updated webhook schema for seamless integration.

Who is this relevant for?​

This is relevant for anyone looking to simplify and automate their workflows using Zapier's no-code platform.

Zapier enables you to connect different web applications and automate repetitive tasks by setting up "rules" that define how data flows between tools and services. With Codat now part of Zapier, you can easily build workflows tailored to your needs without writing any code.

Why should you care?​

With the Codat Zapier app, all Codat webhooks are available as triggers. This makes it possible to automate processes and streamline operations, no matter your technical expertise.

Example use cases​

Here’s how you can use Zapier with Codat:

• Real-time notifications - send a Slack message or email whenever a new company shares data with you.
• Error tracking - post an alert when a sync error occurs to ensure quick resolution.
• Data management - automatically add onboarded companies to a spreadsheet.

If you’re looking to save time and enhance efficiency, this integration is perfect for you!

How to get started?​

To start building your own workflows today, you need:

• A Zapier account - you can create one for free.
• Admin or Developer access to your Codat instance.

Read more

The List companies endpoint now supports querying by tags, streamlining company management in Codat. This feature lets you retrieve companies based on specific criteria.

You can now replay missed messages from the previous two weeks with this update to our webhooks service.

Building and launching a best-in-class bank feeds solution has never been easier than with our new Bank Feeds SDK.

We have added a new onConnectionStarted property to the callback functionality of the Link SDK. It is called with a Connection argument, including its connectionId.

We have expanded our support for connection-related notifications. Use the connection.failed webhook to be alerted if your SMB customer encounters issues when connecting their business software.

Review the upcoming changes and deprecations we announced this quarter, get ahead of them, and see what's new with Codat's products.

On January 10, 2025, we will update the webhook payloads for the bankFeeds.sourceAccount.connected and bankFeeds.sourceAccount.disconnected event types to align with our new webhook schema definition.