Clockify API
Template API removal
Deprecated, no dateSubscribe to Clockify APIShare
Clockify has deprecated the /api/v1/workspaces/{id}/templates* endpoint group without a shutdown date, stating that it should not be used. Requests to these template endpoints fail as part of this removal.
Calls it hits
/api/v1/workspaces/{id}/templates*
What to use instead of these calls
Stop relying on timesheet templates through the API. Clockify documents no replacement endpoint, requiring teams to adjust their integrations accordingly.
Clockify's reference names no replacement for the Template endpoints.
In Clockify API's words
This endpoint group is deprecated and should not be used.
Facts
- API
- Clockify API
api.clockify.me - Kind
- 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 /api/v1/workspaces/{id}/templates* 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
GET /api/v1/workspaces/{id}/scheduling/assignments/projects/totalsEndpoint removal Deprecated, no date -
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
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.