List my time tracking items by date, most recent first
Lists the calling user's own time registrations between two dates, most recently CREATED first.
Same data, scope and paging as get-by-date, but ordered by the registration's creation time, newest first, and not re-sorted. It returns registrations (one row each), not distinct tasks: to build a "recently used tasks" picker, de-duplicate on TaskID / AbsenceCodeID client-side.
Use it to:
- Show the caller's latest registrations first (e.g. a mobile 'recent' list)
- Derive recently used tasks for quick re-entry
Not for:
- Chronological day view →
GET /v1/time-tracking-item/get-by-date
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/time-registration
See also: GET /v1/time-tracking-item/get-by-date, GET /v1/customer/search-for-time-tracking-order-by-recent-registration
Not yet documented: examples.
curl -X GET "https://app3.timelog.com/your-account/api/v1/time-tracking-item/get-by-date-order-by-recent-registration?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z&$page=1&$pagesize=10" \
-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-by-date-order-by-recent-registration?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z&$page=1&$pagesize=10"
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-by-date-order-by-recent-registration?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z&$page=1&$pagesize=10", {
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-by-date-order-by-recent-registration?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z&$page=1&$pagesize=10", 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-by-date-order-by-recent-registration?startDate=2024-12-25T10%3A00%3A00Z&endDate=2024-12-25T10%3A00%3A00Z&$page=1&$pagesize=10')
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": {
"TotalRecord": "example_string",
"TotalPage": "example_string",
"PageNumber": "example_string"
},
"Entities": [
{
"Properties": {
"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",
"AbsenceIsActive": "null",
"AdditionalTextIsRequired": true,
"DefaultBillable": true,
"IsETCProject": true,
"ShowBillable": true,
"AllocatedHour": "null",
"TimeRegistrationID": 123,
"EntityID": 123,
"EntityType": 42,
"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,
"IsFavourite": true,
"StartTime": "null",
"EndTime": "null",
"IsTimestampOverlapping": true
},
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
],
"Actions": [
{}
]
}
],
"Links": [
{
"Href": "example_string",
"Rel": "example_string"
}
]
}
{
"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-by-date-order-by-recent-registration
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 (inclusive). Omitting it → 404 (no action matched).
Filters on TimeTrackingItemRead.Date (gte).
Last day (inclusive).
Filters on TimeTrackingItemRead.Date (lte).
Page number.
Page size (no maximum in the API layer).
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 (inclusive). Omitting it → 404 (no action matched).
Filters on TimeTrackingItemRead.Date (gte).
Last day (inclusive).
Filters on TimeTrackingItemRead.Date (lte).
Page number.
Page size (no maximum in the API layer).
Responses
Paging values. They are returned as STRINGS, for example "TotalRecord": "12".
Omitted (not []) when the list is empty.