Time registrationsDelete a time tracker

Delete a time tracker

Discards a time tracker without turning it into a time registration.

Deletes the tracker row. The tracked time is discarded: no registration is created or changed, also when the tracker was linked to a registration. To keep the time, stop the tracker instead.

Not for:

  • Keeping the tracked time: use POST /v1/time-registration/stop-time-tracker/{timeTrackerId}.

Behaviour:

  • Not idempotent.
  • Safe to retry only under a condition. A repeat call after success returns 500 (tracker gone); treat that as already deleted.
  • Side effect: Deletes the tracker (TimeTrackerDeleted event). Tracked time is lost; linked registration is unchanged.
  • Changes are visible to the next read immediately.

Call first: GET /v1/time-tracker, GET /v1/time-tracker/active-time-tracker

See also: POST /v1/time-registration/stop-time-tracker/{timeTrackerId}

Not yet documented: examples (success).

curl -X DELETE "https://app3.timelog.com/your-account/api/v1/time-tracker/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
"null"
DELETE
/v1/time-tracker/{timeTrackerID}
DELETE
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.
path
timeTrackerIDinteger
Required

Integer tracker ID. A non-integer value does not match the route → 404 Page Not Found.

Format: int32
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).

The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.

Not yet documented: how to obtain a token.

Not yet documented: token lifetime.

Path Parameters

timeTrackerIDinteger
Required

Integer tracker ID. A non-integer value does not match the route → 404 Page Not Found.

Responses

Success without content: HTTP 200 with the literal JSON body null. Literal JSON null (TafSuccessResult).