Get my time and billable totals for a day
Returns the calling user's registered hours, billable hours, billable amount and registration count for one day.
Aggregates the caller's time registrations on date that already have financial data. The financial data is written asynchronously after a registration is saved, so a just-saved registration may be missing from the totals; check get-status-by-date first when the numbers must be final.
Use it to:
- Day summary in a time-tracking client (worked vs billable, value of the day).
Behaviour:
- Idempotent.
- Safe to retry.
- Consistency: eventual — financial data rows are written by the asynchronous time-registration service handler; unprocessed registrations are not counted
Call first: GET /v1/time-registration-financial-data/get-status-by-date
See also: GET /v1/time-registration-financial-data/get-by-date-range
Not yet documented: errors; examples (success); response → success (no legal entity currency).
curl -X GET "https://app3.timelog.com/your-account/api/v1/time-registration-financial-data/get-by-date?date=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/v1/time-registration-financial-data/get-by-date?date=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/v1/time-registration-financial-data/get-by-date?date=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/v1/time-registration-financial-data/get-by-date?date=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/v1/time-registration-financial-data/get-by-date?date=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,
"Date": "2024-12-25T10:00:00Z",
"TotalActualHour": 3.14,
"TotalBillableHour": 3.14,
"TotalActualMinute": 42,
"TotalBillableMinute": 42,
"TotalBillableAmount": 3.14,
"BillableCurrencyABB": "example_string",
"TotalRegistrationCount": 10
},
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
],
"Actions": [
{}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"Message": "No HTTP resource was found that matches the request URI 'https://app{server-number}.timelog.com/{account}/api/v1/time-registration-financial-data/get-by-date'.",
"MessageDetail": "No action was found on the controller 'TimeRegistrationFinancialData' that matches the request."
}
/v1/time-registration-financial-data/get-by-date
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 day. Compared for EQUALITY with the registration date (stored at midnight): send a date without a time part, or nothing matches and every total is 0.
Filters on TimeRegistrationRead.Date (eq).
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
The day. Compared for EQUALITY with the registration date (stored at midnight): send a date without a time part, or nothing matches and every total is 0.
Filters on TimeRegistrationRead.Date (eq).
Date only — no time component.
Responses
Totals for one employee and one calendar day: registered time, billable time, billable amount and the number of registrations, computed from the time registrations' financial data.