Skip to main content

Identifying the Source of /track and /identify Klaviyo v1/v2 Endpoint Calls

  • June 25, 2024
  • 1 reply
  • 41 views

Forum|alt.badge.img+2

I'm in the process of migrating to the latest version of the Klaviyo API. However, I have noticed that on several accounts, the /track and /identify endpoints are still being called using the v1/v2 API versions.
 

The main issue is that the API Report does not provide enough information about the source of these calls because they use a public API key.
 

Klaviyo support suggested going to the Metrics page and filtering by the API category. Unfortunately, this method does not give me enough details to identify the origin of the problem.
 

Has anyone experienced a similar issue with these endpoints? How did you resolve it? Any tips or tools that could help trace the source of these API calls would be greatly appreciated.

1 reply

kaila.lawrence
Community Manager
Forum|alt.badge.img+32

Hi @Damjan! I don’t have any anecdotal experience to share. Hopefully someone else in the community can chime in with theirs!