Klaviyo API
/api/identify endpoint removal
Stopped workingSubscribe to Klaviyo APIShare
On June 30, 2024, the /api/identify endpoint was retired. Calls made to this endpoint fail. This change took place as part of the retirement of legacy APIs.
Calls it hits
/api/identify
What to use instead of these calls
Create or update profiles using POST /api/profile-import for server-side requests, or use POST /client/profiles with a public key.
In Klaviyo API's words
v1/v2 legacy APIs retired on June 30, 2024.
Facts
- API
- Klaviyo API
a.klaviyo.com - Kind
- Endpoint removal
- Takes effect
- June 30, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Klaviyo API's own pages
Questions
When does this change take effect?
Calls to /api/identify on Klaviyo API stopped working on June 30, 2024.
What happens to calls after June 30, 2024?
They have failed since June 30, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Klaviyo API 4
-
/api/trackEndpoint removal Stopped working -
/api/v1/*Version retirement Stopped working -
/api/v2/*Version retirement Stopped working -
No date
POST /api/templates/{id}/renderRemoval Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.