ExpensesGet an employee expense (v2)

Get an employee expense (v2)

Returns one employee expense, including short-lived download URLs for its receipts (v2 route; no approval status).

The v2 route of GET /v1/employee-expense/{employeeExpenseID} — same controller code, owner check, $expand and 15-minute receipt URLs. The one difference is the body: the v2 model has no Status field, so a v2 caller cannot see whether the expense is approved (update / delete answer 37700 / 37703 when it is).

Use it to:

  • Finance / ERP integration fetching an expense and its receipt (v2 clients)
  • Confirming an expense after create or update

Not for:

  • Reading the approval status — use GET /v1/employee-expense/{employeeExpenseID} (Status)
  • Searching by employee or date — GET /v2/employee-expense

Behaviour:

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

Call first: GET /v2/employee-expense, POST /v2/employee-expense

Next: PUT /v2/employee-expense, POST /v2/employee-expense/{employeeExpenseID}/image, DELETE /v2/employee-expense/{employeeExpenseID}/image

See also: GET /v1/employee-expense/{employeeExpenseID}

Not yet documented: request → query params → $expand.

curl -X GET "https://app3.timelog.com/your-account/api/v2/employee-expense/123?$expand=project" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "EmployeeExpenseID": 123,
    "Date": "2024-12-25T10:00:00Z",
    "Amount": 3.14,
    "VatAmount": 3.14,
    "IsBillable": true,
    "Number": "example_string",
    "Comment": "null",
    "ExchangeRate": 3.14,
    "CurrencyID": 123,
    "EmployeeUserID": 123,
    "ExpenseTypeID": 123,
    "PaymentMethodID": 123,
    "ProjectID": 123,
    "ProjectSubContractID": 123,
    "FileUrls": [
      "null"
    ],
    "IsFileUrlLoaded": true,
    "ImageUrls": [
      "null"
    ],
    "IsImageUrlLoaded": true,
    "HasReceiptPictures": true,
    "Project": {
      "ProjectID": 123,
      "ID": "123e4567-e89b-12d3-a456-426614174000",
      "Name": "John Doe",
      "No": "example_string",
      "ExpenseIsBillable": "null",
      "CustomerID": 123,
      "Customer": {
        "CustomerID": 123,
        "ID": "123e4567-e89b-12d3-a456-426614174000",
        "Name": "John Doe",
        "No": "example_string",
        "DefaultMileageDistance": 25,
        "CustomerStatusID": 123,
        "VATNo": "example_string",
        "OrganizationNo": "example_string"
      },
      "MainContractId": 123
    },
    "Currency": {
      "CurrencyID": 123,
      "CurrencyABB": "example_string",
      "DescriptiveName": "John Doe",
      "CurrentRate": 3.14,
      "IsActive": true
    },
    "ExpenseType": {
      "ExpenseTypeID": 123,
      "ExpenseTypeName": "John Doe",
      "ShowInTravel": true,
      "AccountNo": "example_string",
      "VAT": 3.14,
      "ProductNo": "example_string",
      "SalaryCode": "example_string",
      "IsActive": true,
      "IsEquipment": true,
      "CostPrice": 29.99,
      "SalesPrice": 29.99,
      "EquipmentText": "example_string"
    },
    "PaymentMethod": {
      "PaymentMethodID": 123,
      "Name": "John Doe",
      "IsPaidByEmployee": true,
      "IsDefaultForEmployeeExpense": true,
      "IsDefaultForProjectExpense": true,
      "IsActive": true,
      "IsDefaultForImport": true,
      "IsPersonalCreditCard": true,
      "CreditCardEmployeeUserID": "null"
    }
  },
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ],
  "Actions": [
    {}
  ]
}
GET
/v2/employee-expense/{employeeExpenseID}
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.
path
employeeExpenseIDinteger
Required

The expense's integer ID.

Format: int32
query
$expandstring

Comma-separated list of nested objects to embed. Several values: one string, separated by ,. Allowed values: | Value | Name | Meaning | |---|---|---| | project | project | Fill Project (and its customer). | | currency | currency | Fill Currency. | | expenseType | expenseType | Fill ExpenseType. | | paymentMethod | paymentMethod | Fill PaymentMethod. |

Options: project, currency, expenseType, paymentMethod
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.

Path Parameters

employeeExpenseIDinteger
Required

The expense's integer ID.

Query Parameters

$expandstring

Comma-separated list of nested objects to embed.

Several values: one string, separated by ,.

Allowed values:

ValueNameMeaning
projectprojectFill Project (and its customer).
currencycurrencyFill Currency.
expenseTypeexpenseTypeFill ExpenseType.
paymentMethodpaymentMethodFill PaymentMethod.
Allowed values:projectcurrencyexpenseTypepaymentMethod

Responses

Propertiesobject

An employee expense (out-of-pocket cost the employee wants reimbursed) as stored: amount and VAT in the expense's own currency, the exchange rate used, project / contract / expense type / payment method, the owner (EmployeeUserID) and short-lived download URLs for the attached receipts — but, unlike v1, not the approval status. Optional nested objects (Project, Currency, ExpenseType, PaymentMethod) are filled only on $expand. The TAF self link points to GET /v2/employee-expense/{EmployeeExpenseID}; each entity also carries the expense TAF actions.

Linksarray
Actionsobject[]