Clockify API
GET /api/v1/workspaces/{id}/scheduling/assignments/projects/totals endpoint removal
Deprecated, no dateSubscribe to Clockify APIShare
The Clockify API provider has deprecated GET /api/v1/workspaces/{id}/scheduling/assignments/projects/totals without specifying a shutdown date. This change affects callers making requests to the endpoint within the Scheduling endpoint group. When the removal takes effect, requests to this endpoint fail.
Calls it hits
GET /api/v1/workspaces/{id}/scheduling/assignments/projects/totals
What to use instead of these calls
Use POST /api/v1/workspaces/{workspaceId}/scheduling/assignments/projects/totals with the filters in the body instead.
In Clockify API's words
This endpoint group contains deprecated endpoints from the Scheduling endpoint group.
Facts
- API
- Clockify API
api.clockify.me - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Clockify API's own pages
Questions
When does this change take effect?
Clockify API deprecated GET /api/v1/workspaces/{id}/scheduling/assignments/projects/totals without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Clockify API has not given a shutdown date yet.
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 Clockify API 3
-
No date
POST /api/v1/workspaces/{id}/approval-requestsEndpoint removal Deprecated, no date -
No date
POST /api/v1/workspaces/{id}/approval-requests/users/{id}Endpoint removal Deprecated, no date -
No date
/api/v1/workspaces/{id}/templates*Removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.