ExpensesList a project's expenses

List a project's expenses

Lists the project expenses (company costs) booked on one project, newest first, one page at a time.

Returns the project expenses of projectID, ordered by ProjectExpenseID descending (newest created first, not by purchase date), paged with $page / $pagesize. Every entity has the full cost / sales-price breakdown of ProjectExpenseRead, but NO download URLs (FileUrls empty, IsFileUrlLoaded false) — HasReceiptPictures tells you which ones to fetch with GET by ID. Employee expenses booked on the project are not included.

Use it to:

  • Project-cost reconciliation: pull all supplier costs on a project to compare with the ERP's purchase ledger
  • BPP integration checking which supplier invoices were already booked on a project (by ExternalID / InvoiceNo) before creating new ones

Not for:

  • Employee expenses on the project — GET /v1/employee-expense
  • Getting the attached invoice PDFs — GET /v1/project-expense/{expenseID}

Behaviour:

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

Next: GET /v1/project-expense/{expenseID}

See also: GET /v1/employee-expense, POST /v1/project-expense

Not yet documented: examples; request → query params.

curl -X GET "https://app3.timelog.com/your-account/api/v1/project-expense?projectID=123&$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": {
        "ProjectExpenseID": 123,
        "ExpenseNo": "example_string",
        "ProjectID": 123,
        "EmployeeID": 123,
        "PurchaseDate": "2024-12-25T10:00:00Z",
        "InvoiceNo": "example_string",
        "CustomerID": 123,
        "ExpenseCurrencyISO": "example_string",
        "AmountExpenseCurrency": 3.14,
        "VatExpenseCurrency": 3.14,
        "ExpenseDirectProjectExchangeRate": 3.14,
        "ProjectCurrencyISO": "example_string",
        "ExpenseCostProjectCurrency": 3.14,
        "ExpenseCostSystemCurrency": 3.14,
        "ProfitRatio": 3.14,
        "SalesPriceProjectCurrency": 29.99,
        "SalesPriceSystemCurrency": 29.99,
        "SalesPriceProjectExchangeRate": 29.99,
        "InvoicedAmountSystemCurrency": 3.14,
        "InvoicedAmountProjectCurrency": 3.14,
        "Comment": "example_string",
        "PaymentMethodID": 123,
        "ExpenseTypeID": 123,
        "IsBillable": true,
        "IsApproved": true,
        "ApprovedBy": 42,
        "InvoiceLineID": 123,
        "UnitType": 42,
        "ProductNo": "example_string",
        "DisbursementGuid": "123e4567-e89b-12d3-a456-426614174000",
        "ExternalID": "example_string",
        "ProjectSubContractID": 123,
        "InstallmentID": 123,
        "LegalEntityID": 123,
        "FileUrls": [
          "null"
        ],
        "IsFileUrlLoaded": true,
        "HasReceiptPictures": true
      },
      "Links": [
        {
          "Href": "example_string",
          "Rel": "example_string"
        }
      ],
      "Actions": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}
GET
/v1/project-expense
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
projectIDinteger
Required

The project. Omitted → 405 (captured). An unknown or expense-less project → 200 with no entities. Filters on ProjectExpenseRead.ProjectID (eq).

Format: int32
query
$pageinteger

Page number.

query
$pagesizeinteger

Page size. 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

projectIDinteger
Required

The project. Omitted → 405 (captured). An unknown or expense-less project → 200 with no entities.

Filters on ProjectExpenseRead.ProjectID (eq).

$pageinteger

Page number.

$pagesizeinteger

Page size. 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