Get my expense totals for a day
Returns the caller's number of expenses and their total incl. / excl. VAT, in the system currency, for one day.
A day summary for a "my expenses" view: how many expense rows the CALLER registered with that purchase date and their sum including and excluding VAT, converted to the account's system (base) currency at each expense's save-time rate. Counts both employee expenses and project expenses the caller registered. Always the caller — there is no user parameter.
Use it to:
- Mobile time/expense client: show 'today: 3 expenses, 1,250.00 DKK' next to the day's time registrations
Not for:
- The expense lines themselves —
GET /v1/employee-expense - Reimbursement amounts in the employee's currency —
GET /v1/employee-expense-financial-data/get-all-time-total(legal-entity currency, personal expenses only) - Another user's totals — not supported
Behaviour:
- Idempotent.
- Safe to retry.
- Changes are visible to the next read immediately.
Next: GET /v1/employee-expense
See also: GET /v1/employee-expense-financial-data/get-by-date-range, GET /v1/employee-expense-financial-data/get-all-time-total, GET /v1/time-registration-financial-data/get-by-date
Not yet documented: examples; response → empty result.
curl -X GET "https://app3.timelog.com/your-account/api/v1/employee-expense-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/employee-expense-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/employee-expense-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/employee-expense-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/employee-expense-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",
"TotalEmployeeExpenseCount": 10,
"TotalAmount": 3.14,
"TotalAmountWithoutVat": 3.14,
"CurrencyID": 123,
"CurrencyABB": "example_string",
"CurrencyRate": 3.14
},
"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/employee-expense-financial-data/get-by-date'.",
"MessageDetail": "No action was found on the controller 'EmployeeExpenseFinancialData' that matches the request."
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v1/employee-expense-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 (the time part is ignored for the day selection). An expense counts when its stored purchase date is EXACTLY midnight of that day — expenses saved with a time part are missed. Omitted → 404.
Filters on ProjectExpenseRead.PurchaseDate (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 (the time part is ignored for the day selection). An expense counts when its stored purchase date is EXACTLY midnight of that day — expenses saved with a time part are missed. Omitted → 404.
Filters on ProjectExpenseRead.PurchaseDate (eq).
Date only — no time component.
Responses
Expense totals of the CALLER — a count and a sum incl. / excl. VAT — for one day (by-date, and each day of by-date-range) or for an optional period (all-time total). Built for a "my expenses" summary in a mobile/time client. Not a per-expense list (use GET /v1/employee-expense) and not usable for another user.