Toggl Track API
POST /api/v9/me/close_account endpoint removal
Stopped workingSubscribe to Toggl Track APIShare
On April 8, 2024, the Toggl Track API removed the POST /api/v9/me/close_account endpoint. Calls made to this endpoint fail. Support ceased on that date and the deprecated endpoint was removed without further notice.
Calls it hits
POST /api/v9/me/close_account
What to use instead of these calls
Authenticate each request with the API token or basic auth instead of session endpoints. Account closing, sign-up, and password resets now go through the common accounts service described in the documentation.
In Toggl Track API's words
On 2024/04/08 the official support for the deprecated endpoints will cease and they will be removed without further notice.
Facts
- API
- Toggl Track API
api.track.toggl.com - Kind
- Endpoint removal
- Announced
- November 2, 2023
- Takes effect
- April 8, 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 POST /api/v9/me/close_account on Toggl Track API stopped working on April 8, 2024.
What happens to calls after April 8, 2024?
They have failed since April 8, 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/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.