ExpensesGet my expense totals per day for a period

Get my expense totals per day for a period

Returns, for each day of a period, the caller's number of expenses and their total incl. / excl. VAT in the system currency.

One entity per calendar day from startDate to endDate (inclusive), ascending — days without expenses included with zeros — paged over the days ($pagesize defaults to 10, so request $pagesize ≥ the number of days for a month view). Each entity has get-by-date's semantics: the caller's employee and project expenses, in the system currency at each expense's save-time rate.

Use it to:

  • Week / month calendar in a mobile client with an expense badge per day

Not for:

  • A single period total — GET /v1/employee-expense-financial-data/get-all-time-total
  • Another user's totals — not supported

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Changes are visible to the next read immediately.

Next: GET /v1/employee-expense-financial-data/get-by-date, GET /v1/employee-expense

See also: GET /v1/employee-expense-financial-data/get-all-time-total, GET /v1/time-registration-financial-data/get-by-date-range

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-range?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"
{
  "Properties": {
    "TotalRecord": "example_string",
    "TotalPage": "example_string",
    "PageNumber": "example_string"
  },
  "Entities": [
    {
      "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": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}
GET
/v1/employee-expense-financial-data/get-by-date-range
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

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.

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
startDatestring
Required

First day (inclusive; time part ignored for the day selection). Filters on ProjectExpenseRead.PurchaseDate (gte). Date only — no time component.

Format: date-time
query
endDatestring
Required

Last day (inclusive). Before startDate → no entities and a zero / negative TotalRecord. Filters on ProjectExpenseRead.PurchaseDate (lte). Date only — no time component.

Format: date-time
query
$pageinteger

Page number (over days).

query
$pagesizeinteger

Days per page. No maximum enforced in the API layer.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

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

startDatestring
Required

First day (inclusive; time part ignored for the day selection).

Filters on ProjectExpenseRead.PurchaseDate (gte).

Date only — no time component.

endDatestring
Required

Last day (inclusive). Before startDate → no entities and a zero / negative TotalRecord.

Filters on ProjectExpenseRead.PurchaseDate (lte).

Date only — no time component.

$pageinteger

Page number (over days).

$pagesizeinteger

Days per page. No maximum enforced in the API layer.

Responses

Propertiesobject

Paging values. They are returned as STRINGS, for example "TotalRecord": "12".

Entitiesarray

Omitted (not []) when the list is empty.

Linksarray