Toggl Track API
/api/v9/workspaces/{id}/users/{id}/lost_password endpoint removal
Stopped workingSubscribe to Toggl Track APIShare
On June 12, 2024, the /api/v9/workspaces/{id}/users/{id}/lost_password endpoint was removed. Calls sent to this endpoint now fail. Toggl Track API removed the endpoint without any brownout periods.
Calls it hits
/api/v9/workspaces/{id}/users/{id}/lost_password
What to use instead of these calls
Route password resets through Toggl's common accounts service as documented in the Authentication section.
In Toggl Track API's words
In this update, we are removing the following Track v9 endpoint: - /workspaces/{workspace_id}/users/{user_id}/lost_password There will be no brownout periods for this endpoint
Facts
- API
- Toggl Track API
api.track.toggl.com - Kind
- Endpoint removal
- Takes effect
- June 12, 2024
- 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/v9/workspaces/{id}/users/{id}/lost_password on Toggl Track API stopped working on June 12, 2024.
What happens to calls after June 12, 2024?
They have failed since June 12, 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 Toggl Track API 7
-
/api/v8/*Version retirement Stopped working -
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/*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.