Reference data and account settingsList unit types

List unit types

Lists the unit types switched on for the account.

Only the active ones are returned, in enum order, without paging.

Use it to:

  • Validate a unit before sending it on an invoice line or product

Behaviour:

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

See also: GET /v1/user-setting

curl -X GET "https://app3.timelog.com/your-account/api/v1/unit-type" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "UnitTypeID": 0,
        "Name": "Undefined"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 1,
        "Name": "Hours"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 2,
        "Name": "Minutes"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 3,
        "Name": "Days"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 4,
        "Name": "Km"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 6,
        "Name": "Pieces"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 7,
        "Name": "Liters"
      }
    },
    {
      "Properties": {
        "UnitTypeID": 9,
        "Name": "Kilograms"
      }
    }
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v1/unit-type",
      "Rel": "self"
    }
  ]
}
GET
/v1/unit-type
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.
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.

Responses

Entitiesarray

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

Linksarray