Rebrand blog posts

blog/260331-update-suppliers-bill-pay.md

@@ -23,4 +23,4 @@ This update is relevant for all clients using Codat's Bill Pay solution who want
 
 ## How to get started?
 
-You can start using the endpoint right now. Check out the [Update suppliers](/sync-for-payables-v2-api#/operations/update-supplier) endpoint in our API reference, or explore Bill Pay's [Update supplier](/payables/sync/update-supplier) documentation for a full walkthrough.s
+You can start using the endpoint right now. Check out the [Update suppliers](/sync-for-payables-v2-api#/operations/update-supplier) endpoint in our API reference, or explore Bill Pay's [Update supplier](/payables/sync/suppliers#update-supplier) documentation for a full walkthrough.

blog/260420-codat-rebrand.md

@@ -0,0 +1,27 @@
+---
+title: "Codat’s got a new look 👀"
+date: "2026-04-20"
+tags: ["Product", "Update"]
+hide_table_of_contents: false
+authors: pzaichkina
+---
+
+Codat has been evolving for years. Today, our brand catches up.
+
+<!-- truncate -->
+
+Almost a decade ago, Codat started as the reliable, behind-the-scenes infrastructure layer that financial institutions use to connect and standardize business financial data. Hundreds of thousands of data connections later, we've become a strategic partner to the world’s largest financial organizations. 
+
+Our support goes beyond data connectivity and basic analytics. We give commercial bankers clear, timely, forward-looking insight that helps them anticipate client needs and act with confidence. We call this **advisory intelligence**. 
+
+Our new brand is a way to re-introduce Codat and its simple conviction: banks should be able to understand what their clients need before the client has to ask. 
+
+## What's new
+
+You'll see our new brand across every part of Codat: the website, the Portal, our documentation, and the Help Hub. At the heart of it is a new logo: an incomplete circle where the final piece clicks into place, representing the role Codat plays in completing the picture between data, insight, and action.
+
+## What's not changing
+
+Rest assured, the connections, integrations, and APIs your teams rely on are unaffected. Data flows, authentication flows, and existing implementations continue to work exactly as they did yesterday. If you ever have questions about continuity or compatibility, our [Support team](mailto:support@codat.io) is here for you. 
+
+Welcome to the new Codat.

blog/260420-link-portal-rebrand.md

@@ -0,0 +1,28 @@
+---
+title: "Visual changes to Portal and Link"
+date: "2026-04-20"
+tags: ["Product", "Update"]
+hide_table_of_contents: false
+authors: pzaichkina
+---
+
+Codat has a new look, and it's making its way into the products you use every day. 
+
+ <!-- truncate -->
+
+As part of our [newly launched brand identity](/updates/260420-codat-rebrand), we’ve updated interfaces of the Codat Portal and the Link connection flow to reflect a sharper, more modern visual identity.
+
+## What's new?
+
+From today, both Portal and Link reflect Codat's updated visual identity, boasting a new color palette and logo. These changes are subtle, and the Codat you know and rely on is still recognizable beneath them.
+
+#### Custom Link settings
+
+If you’ve previously configured custom branding settings for Link (for example, your own colors and logo), they will remain unchanged. Your overrides take precedence, as before. If you want to learn more about setting your own color palette, refer to [Branding in Portal](/auth-flow/customize/branding). 
+
+If you have the [Secured by Codat](/auth-flow/customize/customize-link#secured-by-codat) setting enabled in your Link settings, the Codat logo displayed in your Link flow will automatically update to the new logo.
+
+## Who is this relevant for?
+
+These changes are already live for all our clients, reflecting our commitment to our new visual identity, and don’t require any action on your part. 
+If you have any questions about the visual changes, get in touch with our [Support team](mailto:support@codat.io).

blog/260710-deprecation-otp-for-sage-bank-feeds.md

@@ -19,9 +19,9 @@ You must update your user journey to surface the verification code during authen
 
 ## Action required
 
-Clients using [Sage Bank Feeds](/integrations/bank-feeds/sage-bank-feeds/) must update their application to include the new OTP generation step before **July 10, 2026**. See how to [Surface the one-time password (OTP) to the user](/integrations/bank-feeds/sage-bank-feeds/sage-bank-feeds-setup#surface-the-one-time-password-otp-to-the-user) for implementation instructions. To test this change in your test environment, please ask [Codat Support](support@codat.io) to enable the feature for you.
+Clients using [Sage Bank Feeds](/integrations/bank-feeds/sage-bank-feeds/) must update their application to include the new OTP generation step before **July 10, 2026**. See how to [Surface the one-time password (OTP) to the user](/integrations/bank-feeds/sage-bank-feeds/sage-bank-feeds-setup#surface-the-one-time-password-otp-to-the-user) for implementation instructions. To test this change in your test environment, please ask [Codat Support](mailto:support@codat.io) to enable the feature for you.
 
-You may also want to update your internal and client-facing documentation in line with this change. Contact [Codat Support](support@codat.io) if you’d like any additional help with this update.
+You may also want to update your internal and client-facing documentation in line with this change. Contact [Codat Support](mailto:support@codat.io) if you’d like any additional help with this update.
 
 ## Expected impact if no action is taken
 

docs/payables/sync/suppliers.md

@@ -58,7 +58,7 @@ Supplier endpoints of the Bill Pay solution return only **active** suppliers fro
 
 ## Update supplier
 
-If your customer's existing supplier changes address or business name, you can reflect this change in their accounting software using the [Update supplier](sync-for-payables-v2-api#/operations/update-supplier) endpoint.
+If your customer's existing supplier changes address or business name, you can reflect this change in their accounting software using the [Update supplier](/sync-for-payables-v2-api#/operations/update-supplier) endpoint.
 
 Include all fields in the request, even if their values haven't changed. If you leave a field out, its value will be **deleted** from the supplier record.