Skip to main content
Sticky

IMPORTANT: Major API Retirement with Breaking Changes - Action Required

  • March 26, 2025
  • 0 replies
  • 246 views

carleygilmore
Forum|alt.badge.img+4

Attention Developer Group!

On June 15, 2025, API revision 2023-06-15 is set to retire. To avoid breakages, you should review the changelog to migrate to a stable API revision as soon as possible. We highly recommend that you upgrade to the latest revision (2025-01-15).

 

What will happen if I don't update? 

Starting on this date, all API calls using the 2023-06-15 revision (or earlier) will fall forward to the 2023-07-15 revision. A large set of breaking changes was introduced in 2023-07-15, so it is likely that your integration will experience breakages if you do not upgrade.

 

As a Klaviyo customer, what do I need to do? 

Review the API activity dashboard in Klaviyo for details on your deprecated API usage.

  • If you're using Klaviyo's Swift SDK, we recommend upgrading to the most recent version (4.2.0), and at a minimum (2.2.1).
  • If you're using Klaviyo's Android SDK, we recommend upgrading to the most recent version (3.3.0), and at a minimum (1.3.0).
  • If you're using Klaviyo's React Native SDK, we recommend upgrading to the most recent version (1.1.1), but all versions of this SDK use the 2023-07-15 revision (or later).
  • If you're using a 3rd-party application that is making deprecated API calls, please contact their team to verify that they will upgrade and ensure that no further action is needed before retirement.

As a Klaviyo partner, what do I need to do? 

If you maintain an OAuth app, you can view your deprecated API usage for your app and upgrade your app to use a stable API revision. We recommend upgrading to the latest revision (2025-01-15).

If you are not yet on OAuth: 

  • Check your codebase to see which revision you are using. 
  • Please note that OAuth and using stable APIs are both requirements for listed apps.
     

Act now to safeguard against any disruption!