Klaviyo API
/api/v2/* version retirement
Stopped workingSubscribe to Klaviyo APIShare
On July 1, 2024, API version v2 was retired across all /api/v2/* endpoints. Calls made to these endpoints after that day fail, returning a 410 GONE error code.
Calls it hits
/api/v2/*
What to use instead of these calls
Move to the date-versioned APIs, such as GET /api/lists and POST /api/profile-subscription-bulk-create-jobs, and include a revision header as outlined in the API comparison chart.
In Klaviyo API's words
v1/v2 API calls made on July 1, 2024 will return a 410 GONE error code.
Facts
- API
- Klaviyo API
a.klaviyo.com - Kind
- Version retirement
- Takes effect
- July 1, 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/v2/* on Klaviyo API stopped working on July 1, 2024.
What happens to calls after July 1, 2024?
They have failed since July 1, 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/identifyEndpoint removal Stopped working -
/api/trackEndpoint removal Stopped working -
/api/v1/*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.