Update time tracking timer

Update time tracking timer in the credential-bound company. Idempotency-Key is required and stores the terminal response for safe retries for 24 hours. This changes draft or operational data without posting accounting entries. Requires the time-tracking:write OAuth scope.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Fields accepted to update time tracking timer. The schema identifies required and optional values.

Start (POST /time-tracker/start) or patch (PATCH /time-tracker) the
acting user's running timer.

There is NO author_id on either, and there never will be: a timer is a live
personal state and every domain path is scoped by author_id. Starting or
pausing somebody else's timer is not an operation this API has — writing time
on their behalf is the time-LOG endpoint, where there is a durable record to
attribute the action on.

task_id distinguishes the two verbs: required to start (a timer with no
task has nothing to log against) and prohibited on the patch, because moving
a running timer to another task would silently re-file the elapsed time.
Switching tasks is stop-then-start, which is two decisions the caller makes
explicitly.

string
required
string | null
boolean
Headers
string
required
length ≤ 191

Required unique key whose request hash and terminal response are stored durably for 24 hours.

Responses

Language
Credentials
OAuth2
Missing 1 required scope
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
*/*