SettingsList the resource-management feature flags

List the resource-management feature flags

Returns the on/off state of the resource-management features — today only Competences.

Account configuration only — the same answer for every user. The list is code-defined; new resource-management features appear only when the code adds them.

Use it to:

  • Resource-management client deciding whether to show competence features

Not for:

  • Any other feature → GET /v2/features/{id}

Behaviour:

  • Idempotent.
  • Safe to retry.

See also: GET /v2/features/{id}, GET /v2/features/front-page

curl -X GET "https://app3.timelog.com/your-account/api/v2/features/resource-management" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "FeatureList": [
      {
        "name": "Competences",
        "identifier": 470,
        "enabled": true
      }
    ]
  },
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v2/features/resource-management",
      "Rel": "self"
    }
  ]
}
GET
/v2/features/resource-management
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

Propertiesobject

A fixed, code-defined list of feature flags with their current on/off state (a single TAF object, not a TAF list).

Linksarray
Actionsobject[]