Toggl Track API
/api/v8/* version retirement
Stopped workingSubscribe to Toggl Track APIShare
On April 1, 2023, Toggl Track retired version 8 of its API. Any requests targeting /api/v8/* endpoints stopped working and now fail.
Calls it hits
/api/v8/*
What to use instead of these calls
Update your integration to call the /api/v9/* counterparts instead, following Toggl's v8 migration guide.
In Toggl Track API's words
The deprecated /api/v8/* endpoints will be disabled starting on April 1 2023.
Facts
- API
- Toggl Track API
api.track.toggl.com - Kind
- Version retirement
- Announced
- October 1, 2022
- Takes effect
- April 1, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Toggl Track API's own pages
Questions
When does this change take effect?
Calls to /api/v8/* on Toggl Track API stopped working on April 1, 2023.
What happens to calls after April 1, 2023?
They have failed since April 1, 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 Toggl Track API 7
-
DELETE /api/v9/me/sessionsEndpoint removal Stopped working -
POST /api/v9/me/close_accountEndpoint removal Stopped working -
POST /api/v9/me/lost_passwordsEndpoint removal Stopped working -
POST /api/v9/me/sessionsEndpoint removal Stopped working -
POST /api/v9/signupEndpoint removal Stopped working -
/api/v9/workspaces/{id}/users/{id}/lost_passwordEndpoint removal Stopped working -
/api/v9/workspaces/*Parameter removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.