Get my time-registration accuracy for a period
Returns how many days, on average, the caller registered project time after the work date — for a period and for the equally long period before it.
Computes, for the CALLER only, the average delay in days between a project time registration's work date and its creation day, over registrations whose work date lies in [startDate, endDate] (AccuracyCurrentPeriod) and in the equally long period immediately before startDate (AccuracyPreviousPeriod), plus the timestamp of the caller's latest change to a project registration (LastRegistrationDate). Full formula, rounding, exclusions and the previous-period arithmetic are on WidgetDataTimeRegistrationAccuracyRead. Both dates are reduced to calendar days (time part dropped); no timezone conversion. There is no validation that startDate ≤ endDate: with startDate after endDate no registration matches and both values are 0.
Use it to:
- Show a user how promptly they register time, and the trend against the previous period
Not for:
- Another employee's or a team's registration delay — the route always computes the caller's own
Rules across fields:
- startDate ≤ endDate is expected but not checked; a reversed range returns 0 for both periods.
Behaviour:
- Idempotent.
- Safe to retry.
- Changes are visible to the next read immediately.
See also: GET /v2/widget-data/external-percentage, GET /v2/widget-data/billable-percentage
Not yet documented: errors; examples.
curl -X GET "https://app3.timelog.com/your-account/api/v2/widget-data/time-registration-accuracy?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v2/widget-data/time-registration-accuracy?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v2/widget-data/time-registration-accuracy?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z", {
method: "GET",
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("GET", "https://app3.timelog.com/your-account/api/v2/widget-data/time-registration-accuracy?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z", 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/v2/widget-data/time-registration-accuracy?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"Properties": {
"UserId": 123,
"StartDate": "2024-12-25T10:00:00Z",
"EndDate": "2024-12-25T10:00:00Z",
"LastRegistrationDate": "null",
"AccuracyCurrentPeriod": 3.14,
"AccuracyPreviousPeriod": 3.14
},
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
],
"Actions": [
{}
]
}
{
"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": "Not Found",
"message": "The requested resource was not found",
"code": 404
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v2/widget-data/time-registration-accuracy
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.First day of the period (inclusive). Any time part is dropped. Omitted → 404 action not matched (captured).
Filters on time registration work date (gte).
Date only — no time component.
Last day of the period (inclusive). Any time part is dropped. Omitted → 404 action not matched.
Filters on time registration work date (lte).
Date only — no time component.
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.
Query Parameters
First day of the period (inclusive). Any time part is dropped. Omitted → 404 action not matched (captured).
Filters on time registration work date (gte).
Date only — no time component.
Last day of the period (inclusive). Any time part is dropped. Omitted → 404 action not matched.
Filters on time registration work date (lte).
Date only — no time component.
Responses
"Time registration accuracy" of ONE user (the caller): on average, how many days after the work date the user's project time registrations were created, for a period and for the equally long period just before it. 0 = registered on the day (or no registrations); higher = registered later. Only project time counts (registrations of EntityType 43 = Allocation, i.e. on a task allocation); absence is excluded.