Solved

Legacy v1/v2 API Retirement

  • 13 March 2024
  • 5 replies
  • 550 views

Userlevel 1
Badge +4

Hi there,

 

I received this email for a client re: Legacy v1/v2 APIs being retired.

Could I get some tips on how to start addressing this / what to look out for? 

 

 

Thank you

icon

Best answer by StefanUE 13 March 2024, 16:17

View original

5 replies

Userlevel 5
Badge +18

@Pamela-MJ hey, thanks for your question, this is actually happening across the board with all Klaviyo accounts where legacy V1 and V2 APIs are being used. Nothing to worry about, though!

Here are some resources to help you navigate this:
 

Tools and Steps To Take:
 

Documentation:

 

Happy to chat further!

Userlevel 1
Badge +4

Awesome. Thank you @StefanUE ! ✅

Hi @StefanUE - just a clarification (from a non-developer), if we don’t have any custom API integrations and are only integrating through Klaviyo partners (shopify / meta) - do we need to take an action? Doesn’t seem so, but I don’t want to miss anything. Thanks! 

Userlevel 5
Badge +18

@rory hey, sadly I’m not a developer myself (although I dabble), so I can’t really confirm this with 100% certainty although I’m pretty confident that’s the case based on a few Klaviyo accounts I’ve seen so far. Might be best just to double check this with support so you have it in writing. 

Hope that helps!

Thanks @StefanUE! I’ll check with support just to be sure. 

Reply