Change a time tracker
Replaces the task or absence, billable flag, comment, additional text and factor of a time tracker.
Loads the tracker by TimeTrackerID, overwrites its six editable fields with the request (full replace: omitted fields become null / 0 / NotSpecified) and saves it without stopping it. Start time, minutes and status are not changed. Returns HTTP 200 with body null.
Rules across fields:
- R1: When EntityID is sent, EntityType must be Task (98) or AbsenceCode (149) and IsBillable must be set.
- R2: EntityType must be sent (98 or 149) even when clearing EntityID: omitted = 0 = NotSpecified → 60071.
Behaviour:
- Idempotent.
- Safe to retry.
- Side effect: Updates the tracker row (TimeTrackerUpdated event when something changed). Does not stop the tracker or touch registrations.
- Changes are visible to the next read immediately.
Call first: GET /v1/time-tracker/active-time-tracker, GET /v1/time-tracker
Next: POST /v1/time-registration/stop-time-tracker/{timeTrackerId}
Not yet documented: examples (success).
curl -X PUT "https://app3.timelog.com/your-account/api/v1/time-tracker" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{
"TimeTrackerID": 123,
"EntityType": 42,
"EntityID": "null",
"IsBillable": "null",
"Comment": "null",
"AdditionalTextField": "null",
"Factor": 3.14
}'
import requests
import json
url = "https://app3.timelog.com/your-account/api/v1/time-tracker"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
data = {
"TimeTrackerID": 123,
"EntityType": 42,
"EntityID": "null",
"IsBillable": "null",
"Comment": "null",
"AdditionalTextField": "null",
"Factor": 3.14
}
response = requests.put(url, headers=headers, json=data)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v1/time-tracker", {
method: "PUT",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
},
body: JSON.stringify({
"TimeTrackerID": 123,
"EntityType": 42,
"EntityID": "null",
"IsBillable": "null",
"Comment": "null",
"AdditionalTextField": "null",
"Factor": 3.14
})
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
"bytes"
"encoding/json"
)
func main() {
data := []byte(`{
"TimeTrackerID": 123,
"EntityType": 42,
"EntityID": "null",
"IsBillable": "null",
"Comment": "null",
"AdditionalTextField": "null",
"Factor": 3.14
}`)
req, err := http.NewRequest("PUT", "https://app3.timelog.com/your-account/api/v1/time-tracker", bytes.NewBuffer(data))
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')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Put.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
request.body = '{
"TimeTrackerID": 123,
"EntityType": 42,
"EntityID": "null",
"IsBillable": "null",
"Comment": "null",
"AdditionalTextField": "null",
"Factor": 3.14
}'
response = http.request(request)
puts response.body
"null"
{
"error": "Bad Request",
"message": "The request contains invalid parameters or malformed data",
"code": 400,
"details": [
{
"field": "email",
"message": "Invalid email format"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v1/time-tracker
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.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.
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.The media type of the request body
The tracker to change. NOT validated by the API: 0 or an unknown ID gives 500 (Code 100), not 400. Identifier of this object, unique per TimeLog site.
What EntityID points to. Omitted = 0 (NotSpecified), which fails the save with 60071 even when EntityID is null.
Allowed values:
| Value | Name | Meaning |
|---|---|---|
| 98 | Task | EntityID is a task ID. |
| 149 | AbsenceCode | EntityID is an absence code ID. |
| 0 | NotSpecified | Default when omitted; rejected on save (60071). |
Task or absence code ID. Omitted/null clears the entity: the tracker then cannot become a registration on stop.
Refers to TaskRead | AbsenceCode (see EntityType).
Conditional. Required when EntityID is sent.
Null: Omitted or null clears the comment (full replace).
Null: Omitted or null clears the value (full replace).
Overtime factor. Non-nullable: omitted is written as 0. Unit: percent
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.
Not yet documented: how to obtain a token.
Not yet documented: token lifetime.
Body
The tracker to change. NOT validated by the API: 0 or an unknown ID gives 500 (Code 100), not 400.
Identifier of this object, unique per TimeLog site.
What EntityID points to. Omitted = 0 (NotSpecified), which fails the save with 60071 even when EntityID is null.
Allowed values:
| Value | Name | Meaning |
|---|---|---|
98 | Task | EntityID is a task ID. |
149 | AbsenceCode | EntityID is an absence code ID. |
0 | NotSpecified | Default when omitted; rejected on save (60071). |
981490Task or absence code ID. Omitted/null clears the entity: the tracker then cannot become a registration on stop.
Refers to TaskRead | AbsenceCode (see EntityType).
Conditional. Required when EntityID is sent.
Null: Omitted or null clears the comment (full replace).
Null: Omitted or null clears the value (full replace).
Overtime factor. Non-nullable: omitted is written as 0.
Unit: percent
Responses
Success without content: HTTP 200 with the literal JSON body null. Literal JSON null (TafSuccessResult).