ProjectsList project categories

List project categories

Lists the account's project categories, by name.

The value set for ProjectCategoryID on project create and update. Active and inactive categories are both returned. The list is not gated by the ProjectCategory feature; that feature only decides whether project create / update write the field (see ProjectCreate).

Use it to:

  • Build a name -> ProjectCategoryID map before creating projects from templates

Behaviour:

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

Next: POST /v1/project/create-from-template, PUT /v1/project/{projectID}

curl -X GET "https://app3.timelog.com/your-account/api/v1/ProjectCategory?$page=1&$pagesize=10" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "TotalRecord": "2",
    "TotalPage": "1",
    "PageNumber": "1"
  },
  "Entities": [
    {
      "Properties": {
        "ProjectCategoryID": 4,
        "Name": "Selection 1",
        "IsActive": true,
        "ProductNo": "",
        "ID": "ea03d68d-5afb-48d2-908f-56bd12b232e6"
      }
    },
    {
      "Properties": {
        "ProjectCategoryID": 5,
        "Name": "Selection 2",
        "IsActive": true,
        "ProductNo": "",
        "ID": "7805fec2-67b9-41be-a1ad-4cc0e990c130"
      }
    }
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v1/ProjectCategory",
      "Rel": "self"
    }
  ]
}
GET
/v1/ProjectCategory
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
$pageinteger

Page number.

query
$pagesizeinteger

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

$pageinteger

Page number.

$pagesizeinteger

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