Closed ademarco17 closed 1 month ago
@ademarco17 thanks for raising, looking into this now
@ademarco17 All our calls have been updated to use curl
and have a X-Klaviyo-User-Agent
header. We don't use the Guzzle HTTP client. My guess is you potentially have another module that is using this client to interface with Klaviyo's legacy API. Would you mind sharing your accounts Public API key so I can dig into this futher?
@cykolln thanks for getting back to me! See our Public API in my BitWarden link here: [https://send.bitwarden.com/#515Zh0uk0E6WULFyASJYzg/I0Jr4BGmIwCM6H2KiruIzw]
@ademarco17 hey there, I'm seeing some ReviewsIO related API metrics on your account that are likely the culprit here. All calls originating from this extension are properly on v3, but you still must update all custom event tracking requests. Here is a guide that should help! If these requests are from another 3rd party extension, please reach out to the developers so they can update the endpoints they are using.
If you have any more specific questions about the V3 API migration, please reach out to Klaviyo support! They will be able to dive into the details with you more fully than I am able to here.
Description
Klaviyo is updating their APIs, so we upgraded the extension in Magento to the latest version, but Klaviyo is still seeing an active legacy API on their end. As per their team, "It's the '/track' endpoint and it's on a public API key. The user agent for this API endpoint is called "guzzlehttp"."
I am not familiar with this module and would appreciate input from anyone who has a better understanding of its integration with Klaviyo and what steps that can be taken to update the "guzzlehttp" API.
Our Magento is on version 2.4.6-p5 with Klaviyo version 4.1.3.