ProjectsList a project's time registrations

List a project's time registrations

Returns every time registration on a project — all employees, all dates — with hours, rate, amount, billability and invoicing state.

Runs the time-registration drill-down report for one project with no other filter and no date range: every registration on every task of the project, of every employee, ordered by date, task name, last change and ID, in one unpaged TAF list. List Properties: AdditionalCommentFieldName (the account's label of the additional text field, "" when that feature is off), TimeRegistrationsTotalActualHours and TimeRegistrationsTotalActualAmount (sums over the rows, en-GB number strings; the amount sum adds the rows' amounts as they are, in each row's Currency).

Use it to:

  • Show who registered what on a project, and whether it is invoiced

Not for:

  • Your own or a date-bounded list of registrations → GET /v1/time-registration/{timeRegistrationID} (scoped, paged)

Behaviour:

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

Call first: GET /v2/projects

See also: GET /v1/time-registration/{timeRegistrationID}

Not yet documented: response → empty result.

curl -X GET "https://app3.timelog.com/your-account/api/v2/projects/123/time-registrations" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "TimeRegistrationId": 123,
        "Date": "2024-12-25T10:00:00Z",
        "ProjectName": "John Doe",
        "TaskName": "John Doe",
        "EmployeeInitials": "example_string",
        "EmployeeName": "John Doe",
        "Comment": "example_string",
        "AdditionalText": "example_string",
        "Currency": "example_string",
        "ActualHours": 3.14,
        "HourlyRate": 3.14,
        "Factor": 3.14,
        "ActualAmount": 3.14,
        "NonBillable": true,
        "BillableStatus": "NonBillableRegistrationOnBillableTaskWithZeroHourlyRate",
        "BookingStatus": "Booked",
        "BookedVoucherId": 123,
        "BookedInvoiceId": 123,
        "DraftVoucherId": 123,
        "DraftInvoiceId": 123,
        "RegInvoiceLineId": 123
      },
      "Links": [
        {
          "Href": "example_string",
          "Rel": "example_string"
        }
      ],
      "Actions": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}
GET
/v2/projects/{projectId}/time-registrations
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
projectIdinteger
Required

The project. Not an integer → 400; unknown, 0 or negative → 500.

Format: int32
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

projectIdinteger
Required

The project. Not an integer → 400; unknown, 0 or negative → 500.

Responses

Entitiesarray

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

Linksarray