Get my weekly registrations
Returns the calling user's registrations for the 7 days from startDate, grouped by day and task, with daily and weekly norm hours and the difference.
The weekly-timesheet view of the CALLER's time. The window is startDate through startDate + 6 days (no alignment to a week start: send the Monday yourself if you want an ISO week). All registrations of the window are read (no paging), grouped by day, then by task, and each day gets the employee's norm hours and registered − norm. Week totals: TotalRegisteredHours (days with registrations) and TotalNormHours — so a day with no registrations is missing from Tasks but still counts in TotalNormHours.
Use it to:
- Weekly timesheet grid in a time-tracking client
- 'Am I short this week?' — TotalHoursDifference
Not for:
- A flat, paged list →
GET /v1/time-tracking-item/get-by-date - Approval status per day →
GET /v1/approval/timesheets/get-status-by-dates
Behaviour:
- Idempotent.
- Safe to retry.
- Duplicates: n/a (read)
- Changes are visible to the next read immediately.
Next: GET /v1/time-tracking-item/{timeRegistrationID}, POST /v1/approval/timesheets/submit-period
See also: GET /v1/time-tracking-item/get-by-date
Not yet documented: examples.
curl -X GET "https://app3.timelog.com/your-account/api/v1/time-tracking-item/get-weekly-registrations?startDate=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-tracking-item/get-weekly-registrations?startDate=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-tracking-item/get-weekly-registrations?startDate=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-tracking-item/get-weekly-registrations?startDate=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-tracking-item/get-weekly-registrations?startDate=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": {
"TotalRegisteredHours": 3.14,
"TotalNormHours": 3.14,
"TotalHoursDifference": 3.14,
"Tasks": [
{
"Date": "2024-12-25T10:00:00Z",
"RegisteredHours": 3.14,
"NormHours": 3.14,
"HoursDifference": 3.14,
"TaskInfos": [
{
"CustomerID": "null",
"CustomerName": "John Doe",
"CustomerNo": "example_string",
"ProjectID": "null",
"ProjectName": "John Doe",
"ProjectNo": "example_string",
"TaskID": "null",
"TaskName": "John Doe",
"TaskFullName": "John Doe",
"IsFixedPrice": "null",
"TaskNo": "example_string",
"TaskIsActive": "null",
"AbsenceCodeID": "null",
"AbsenceName": "John Doe",
"AbsenceCode": "example_string",
"AdditionalTextIsRequired": true,
"DefaultBillable": true,
"IsETCProject": true,
"ShowBillable": true,
"IsFavourite": true,
"EntityID": 123,
"EntityType": 42,
"AbsenceIsActive": "null",
"Registrations": [
{
"AllocatedHour": "null",
"TimeRegistrationID": 123,
"UserID": 123,
"Created": "2024-12-25T10:00:00Z",
"CreatedBy": 42,
"LastModified": "2024-12-25T10:00:00Z",
"LastModifiedBy": 42,
"IsBillable": true,
"Status": true,
"Date": "2024-12-25T10:00:00Z",
"MonthlyPeriod": "example_string",
"Comment": "example_string",
"Hours": 3.14,
"AdditionalTextField": "example_string",
"InvoiceStatus": true,
"TimeRegistrationApprovalStatus": 42,
"TimeTrackingFormat": 42,
"Minutes": 42,
"BillableHours": 3.14,
"BillableMinutes": 42,
"StartTime": "null",
"EndTime": "null",
"IsTimestampOverlapping": true
}
]
}
]
}
]
},
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
],
"Actions": [
{}
]
}
{
"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"
}
/v1/time-tracking-item/get-weekly-registrations
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 7-day window; the window ends startDate + 6 days (inclusive). Omitting it → 404.
Filters on TimeTrackingItemRead.Date (between).
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 7-day window; the window ends startDate + 6 days (inclusive). Omitting it → 404.
Filters on TimeTrackingItemRead.Date (between).
Responses
The calling employee's registrations for one 7-day window, grouped first by day and then by task, with the employee's norm (expected) time per day and the difference. It is the data behind TimeLog's weekly timesheet: "how much did I register each day, on what, and how far am I from my norm". Despite its name, Tasks is the list of DAYS. The object has no ID; it is identified by (caller, startDate).