Generated by API Evangelist
Written by API Evangelist tooling for Clickup's API. It is a proposal applied on top of the contract, not a document Clickup publishes.
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Clickup Time Tracking (Legacy) API
version: 1.0.0
extends: openapi/clickup-time-tracking-legacy-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-09-26'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 4
- target: $.paths['/v2/task/{task_id}/time'].get
update:
x-apievangelist-phrasing:
intent: Get time tracked on a task (legacy)
effect: read
questions:
- How much time has been tracked on a task, using the legacy time endpoint?
- Can I read a task's tracked intervals with the older time tracking API?
instructions:
- text: Using legacy time tracking, get tracked time on task {task_id}.
slots:
task_id: path.task_id
- text: Show the legacy tracked-time intervals for custom task ID {task_id} in Workspace {team_id}.
slots:
task_id: path.task_id
team_id: query.team_id
method: generated
generated: '2026-09-26'
- target: $.paths['/v2/task/{task_id}/time'].post
update:
x-apievangelist-phrasing:
intent: Log a time interval on a task (legacy)
effect: write
questions:
- How do I log time against a task with the legacy time tracking endpoint?
- What start, end and duration values does the legacy track-time call need?
instructions:
- text: With legacy time tracking, log {time} ms on task {task_id} from {start} to {end}.
slots:
time: requestBody.time
task_id: path.task_id
start: requestBody.start
end: requestBody.end
- text: Track a legacy time interval on task {task_id} starting {start} and ending {end}, lasting {time}.
slots:
task_id: path.task_id
start: requestBody.start
end: requestBody.end
time: requestBody.time
method: generated
generated: '2026-09-26'
- target: $.paths['/v2/task/{task_id}/time/{interval_id}'].put
update:
x-apievangelist-phrasing:
intent: Edit a tracked time interval (legacy)
effect: write
questions:
- Can I fix the start or end of a time interval logged with the legacy endpoint?
- How do I change a legacy tracked interval's duration?
instructions:
- text: Edit legacy interval {interval_id} on task {task_id} to run from {start} to {end}, total {time}.
slots:
interval_id: path.interval_id
task_id: path.task_id
start: requestBody.start
end: requestBody.end
time: requestBody.time
- text: 'Correct tracked interval {interval_id} of task {task_id} using the legacy API: start {start}, end {end}, time {time}.'
slots:
interval_id: path.interval_id
task_id: path.task_id
start: requestBody.start
end: requestBody.end
time: requestBody.time
method: generated
generated: '2026-09-26'
- target: $.paths['/v2/task/{task_id}/time/{interval_id}'].delete
update:
x-apievangelist-phrasing:
intent: Delete a tracked time interval (legacy)
effect: destructive
questions:
- How do I remove a time interval I logged with the legacy endpoint?
- Can I delete one tracked interval from a task without touching the others?
instructions:
- text: Delete legacy interval {interval_id} from task {task_id}.
slots:
interval_id: path.interval_id
task_id: path.task_id
- text: Remove tracked time interval {interval_id} on task {task_id} via legacy time tracking.
slots:
interval_id: path.interval_id
task_id: path.task_id
method: generated
generated: '2026-09-26'
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.