/v3.2/* → version retirement
LiveChat API
Stopped working
On March 31, 2023, the provider retired the v3.2 API. Requests to any /v3.2/* endpoint fail after that date. The change affects all callers sending requests to these paths.
Calls it hits
/v3.2/*
What to use instead of these calls
Migrate your application to v3.3 or to a stable version such as v3.5 or later. From v3.3 on, the move requires updating how you configure integrations, as webhooks and properties are registered per application and enabled per license.
In LiveChat API's words
Make sure to migrate your application to v3.3 or, most preferably, to the current stable API version (v3.5) by 31-03-2023 .
Facts
- API
- LiveChat API
api.livechatinc.com - Kind
- Version retirement
- Announced
- February 8, 2023
- Takes effect
- March 31, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against LiveChat API's own pages
Questions
When does this change take effect?
Calls to /v3.2/* on LiveChat API stopped working on March 31, 2023.
What happens to calls after March 31, 2023?
They have failed since March 31, 2023.
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 LiveChat API 1
-
No date
/multicastEndpoint removal 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.