ClickUp API
PUT /api/v2/task/{id}/time/{id} endpoint removal
Deprecated, no dateSubscribe to ClickUp APIShare
The ClickUp API deprecated the legacy time tracking endpoint PUT /api/v2/task/{id}/time/{id} without a shutdown date. Calls made to this route face removal and will fail. ClickUp API designates it as a legacy endpoint in favor of newer time tracking tools.
Calls it hits
PUT /api/v2/task/{id}/time/{id}
What to use instead of these calls
Use the Time Tracking API instead by sending requests to PUT /api/v2/team/{team_id}/time_entries/{timer_id}.
In ClickUp API's words
This is a legacy time tracking endpoint. We recommend using the Time Tracking API endpoints to manage time entries.
Facts
- API
- ClickUp API
api.clickup.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against ClickUp API's own pages
Questions
When does this change take effect?
ClickUp API deprecated PUT /api/v2/task/{id}/time/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: ClickUp 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 ClickUp API 3
-
No date
DELETE /api/v2/task/{id}/time/{id}Endpoint removal Deprecated, no date -
No date
GET /api/v2/task/{id}/timeEndpoint removal Deprecated, no date -
No date
POST /api/v2/task/{id}/timeEndpoint 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.