Skip to main content

I received the following notification when updating an email template…

 

 

You are calling at least one API revision that will be retired in less than 6 months.

What does this mean?
Key account features like profile creation, flow and segment enrollment, consent management, and more are at risk of disruption if you fail to update your revisions to a supported version. In many cases, this is a one line code change, but could require more work in the case of breaking changes between revisions.

To understand the scope of work needed to update your revisions, please go to your account’s Developer Dashboard and review the API Revisions tool for more information.

The following accounts require revision updates:

Retiring in less than 6 months:

  • Creative Designs By Kari (UifCTC)

 

9/4/2024

 

 

...when I use the Developer Dashboard link , in the API Revisions area, it shows 0 for each and Stable Revisions shows as good.

 

I just need, in plain english, what I need to do if anything, and where to do it.

 

 

Hi @CDBK2022 

Unfortunately, I don’t have an answer but just wanted to jump on board to request a laymen’s version of how to handle this notification!

Unlike you I have a few deprecated API revisions appearing, and would like to know if following through with the ‘Update revision’ button is all that is required to resolve this - and whether this action will take me onto a path that requires developer skills, or is just a straightforward update process?

 

Thanks, much appreciated.


I’m having this same issue and am completely lost. Wouldn’t this be something that is automatically handled by our ecommerce platform integration? I’m not a developer and need some serious help here.


Hello @CDBK2022 @SSATTLER  I think these are coming form legacy client apis. Look at the Revision date in the new client APIs here:

https://developers.klaviyo.com/en/reference/create_client_event


I’m having the exact same problem.

This is What I got:

 

 

 

 

 

 

You are calling at least one API revision that will be retired in less than 6 months.

What does this mean?
Key account features like profile creation, flow and segment enrollment, consent management, and more are at risk of disruption if you fail to update your revisions to a supported version. In many cases, this is a one line code change, but could require more work in the case of breaking changes between revisions.

To understand the scope of work needed to update your revisions, please go to your account’s Developer Dashboard and review the API Revisions tool for more information.

The following accounts require revision updates:

Retiring in less than 6 months:

 

 

 

How do I fix this???


Hello @CDBK2022 @SSATTLER  I think these are coming form legacy client apis. Look at the Revision date in the new client APIs here:

https://developers.klaviyo.com/en/reference/create_client_event

What does that mean?


Hi @CDBK2022 

Unfortunately, I don’t have an answer but just wanted to jump on board to request a laymen’s version of how to handle this notification!

Unlike you I have a few deprecated API revisions appearing, and would like to know if following through with the ‘Update revision’ button is all that is required to resolve this - and whether this action will take me onto a path that requires developer skills, or is just a straightforward update process?

 

Thanks, much appreciated.

I’m having this same issue, any help?


I am having the same issue, no idea where to start. Any advice?


Hey @Rober13rr @CDBK2022 @Maxbuzz @SSATTLER @Tiwinkle @Mary_s 

I’ve looked back into my Account>Integrations>Developers(top right button)>Developer Tools>API Revisions>View details and can now see only 1 up to date revision which says ‘stable’. 

Perhaps it took some time to reconcile Klaviyo’s notification with what was actually appearing in the API details page, and hopefully, like me, your issue has just disappeared!

Even when I click on ‘Deprecated’ and ‘Retired’ statuses there is nothing, so perhaps as stated above, these were legacy apis (just in the process of being removed).

 

**I’m still receiving a notification from Klaviyo, which doesn’t inspire confidence...so if anyone knows anything more to it, it would be great to hear it**


@Katzzz My issue seems to have disappeared too. Thanks so much for alerting me to this. I hope this means there’s nothing more we need to do. I always thought it was strange that Klaviyo would require non-developers to try to figure out how to make these changes.


My issue seems to have disappeared too!!


Reply