+1Hi community,
I am currently using a buit-in app that integrates Shopify with Klaviyo. Recently, I have been receiving warnings related to the usage of the V1 API. As the original setup was not developed by our team, I am unsure of how to proceed with migrating to V2.
Could anyone kindly provide a guide or any advice on how to make this transition smoothly? Your assistance would be greatly appreciated.
Thank you in advance for your time and help.
Best answer by Ashley I.
Hi
Welcome to the Community!
If you haven’t already checked it out, Klaviyo has an awesome resource for the API migration here: Migrate from v1/v2 to the new Klaviyo APIs. There is also a FAQ available here if you have additional questions after reviewing the documentation.
If you have any difficulty during the migration, you can also reference the Migration resources.
Hope this helps!
-- Ashley Ismailovski
+42Hi
Welcome to the Community!
If you haven’t already checked it out, Klaviyo has an awesome resource for the API migration here: Migrate from v1/v2 to the new Klaviyo APIs. There is also a FAQ available here if you have additional questions after reviewing the documentation.
If you have any difficulty during the migration, you can also reference the Migration resources.
Hope this helps!
-- Ashley Ismailovski
+1Hi
Welcome to the Community!
If you haven’t already checked it out, Klaviyo has an awesome resource for the API migration here: Migrate from v1/v2 to the new Klaviyo APIs. There is also a FAQ available here if you have additional questions after reviewing the documentation.
If you have any difficulty during the migration, you can also reference the Migration resources.
Hope this helps!
-- Ashley Ismailovski
Hi Ashley,
As I have said, I used the readymade option. The “Shopify” app/plugin was within the integration section in Klaviyo. As I or my team did not develop that, I cannot do anything with that. I guess, the option was developed by Klaviyo.
+1I have been trying to get my head around this. I’m currently using v1/v2 API’s for the following: Octane, Trustpilot and Yotpo SMSBump.
Am I correct in saying that because Octane and Trustpilot are in the ‘Klaviyo connect integration directory’ there is no action required on my part. The APIs are connected with these supported third parties and these third parties are making changes on their side?
For Yotpo SMSBump, this API connection would require action on my part?
Thanks,
Wes
+1Am I correct in saying that because Octane and Trustpilot are in the ‘Klaviyo connect integration directory’ there is no action required on my part. The APIs are connected with these supported third parties and these third parties are making changes on their side?
I am also confused, not getting any clear answer from anywhere.
+1This is clear as mud - I get these warnings but the Shopify app is up to date?
I am the user not the techincal developer of these products. Shopify app to Klaviyo integration.
Therefore what action do we take. Please dont just redirect to that very dense API help doc, Im not going to start rewrting Shopify’s app…
I’m having the same issue with Subbly to Klaviyo app as you are with Shopify to Klaviyo. There doesn’t seem to be available instructions for integrations when you’re not the developer.
+2Any update on this? Is the Shopify integration with Klaviyo using the latest API?
Hi everyone - Sorry about the delay getting back to you.
If you are using the native Shopify/Klaviyo integration, that is not impacted by the v1/v2 API retirement. We automatically converted that integration over to our new APIs a while ago so there’s no action required.
If you are still getting an email from us about being impacted by the retirement, I'd recommend going to this page: https://www.klaviyo.com/developer-tools/dashboard and if you don't have a yellow banner on top, you are all set. If there is a yellow banner you can scroll down and hit the "Export API Report" button to get more details on what calls are being made to old APIs. Then you can use this guide https://developers.klaviyo.com/en/docs/audit_your_klaviyo_api_usage to determine what lines on the report you should care about and where they might be coming from. Please note that a lot of 3rd parties have converted recently so I’d recommend keeping a close eye on the “Most Recent Request Timestamp” column. If that date is over a few days old, it’s a good sign that the 3rd party moved over and you don’t need to worry about anything.
I also see some questions around whether you need to do anything for Octane, Trustpilot and Yotpo SMSBump and I’ll generalize that question for everyone. Many 3rd parties we work with have recently moved over to the new APIs and don’t require any action from you. However, there are some that as part of this work enhanced their capabilities or require that you do update something on their website in order to switch over to using our new APIs. If you are still seeing v1/v2 calls in your report attributed to 3rd parties I’d recommend reaching out to them to see if there’s any action that you need to take.
Let me know if you have any other questions or if anything I said was confusing!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
