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}
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"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v1/time-tracker/123"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.delete(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v1/time-tracker/123", {
method: "DELETE",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("DELETE", "https://app3.timelog.com/your-account/api/v1/time-tracker/123", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v1/time-tracker/123')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Delete.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
"null"
{
"Message": "Authorization has been denied for this request."
}
{
"Message": "Page Not Found",
"Timestamp": "…",
"RawUrl": "https://app{server-number}.timelog.com/{account}/api/v1/time-tracker/{timeTrackerID}"
}
{
"Code": 100,
"Message": "Unknown error occur in system, please contact system administrator.",
"Details": [],
"Parameters": "…",
"Url": "https://app{server-number}.timelog.com/{account}/api/v1/time-tracker/{timeTrackerID}"
}
/v1/time-tracker/{timeTrackerID}Target server for requests. Edit to use your own host.
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.
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.Integer tracker ID. A non-integer value does not match the route → 404 Page Not Found.
Request Preview
Response
Response will appear here after sending the request
Authentication
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.
Path Parameters
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).