ProjectsList the allocations of a task

List the allocations of a task

Returns every allocation on a task, completed ones included.

Lists who is allocated to the task, with allocated and registered hours, hourly rate (name, amount, project currency), period, and the recurring / completed flags — regardless of allocation status. Not paged. Requires the same project privilege as the writes (ViewCreateEditDelete); a user who can only view the project gets 403.

Use it to:

  • Read a task's staffing and burn (allocated vs registered hours) into a PSA / BI tool

Not for:

  • Allocations across tasks or users — not offered by this route

Behaviour:

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

Call first: GET /v1/task

See also: POST /v1/task/{taskID}/allocation

Not yet documented: errors; examples; response → default ordering; response → empty result; response → pagination → total count.

curl -X GET "https://app3.timelog.com/your-account/api/v1/task/123/allocation" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "AllocationID": 123,
        "TaskID": 123,
        "UserID": 123,
        "AllocatedHours": 3.14,
        "RegisteredHours": 3.14,
        "HourlyRateID": 123,
        "HourlyRateName": "null",
        "HourlyRateAmount": 3.14,
        "HourlyRateCurrencyAbb": "example_string",
        "StartDate": "null",
        "EndDate": "null",
        "IsRecurring": true,
        "IsCompleted": true
      },
      "Links": [
        {
          "Href": "example_string",
          "Rel": "example_string"
        }
      ],
      "Actions": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}
GET
/v1/task/{taskID}/allocation
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
taskIDinteger
Required

The task whose allocations are listed. Route constraint :int.

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

taskIDinteger
Required

The task whose allocations are listed. Route constraint :int.

Responses

Entitiesarray

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

Linksarray