SettingsList the front-page feature flags

List the front-page feature flags

Always the same nine entries, in this order: FrontPageInternalMessage (the administrator's notice box), DesignSevenNotificationCenter, ShowMileStones (with value = the account setting FrontPageMilestonePeriod), WidgetInvoicedPerMonth, WidgetPlannedAbsence, WidgetProjectEconomyHealth, WidgetAverageHourlyRate, WidgetTimeTrackingDelay (with value = the setting FrontPageCompanyTarget) and WidgetVacationCalculation. Account configuration only — the same answer for every user of the account. Which widgets a given USER sees is decided by roles and personal order (GET /v2/page-settings/widgets).

Use it to:

  • Front-page client deciding which boxes and widgets to render for the account

Not for:

  • The caller's own widget list → GET /v2/page-settings/widgets
  • Any other feature → GET /v2/features/{id}

Behaviour:

  • Idempotent.
  • Safe to retry.

Next: GET /v2/page-settings/widgets, GET /v2/settings/frontpage-internal-message

See also: GET /v2/features/{id}, PUT /v2/features

Not yet documented: response → success → schema.

curl -X GET "https://app3.timelog.com/your-account/api/v2/features/front-page" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "FeatureList": [
      {
        "name": "FrontPageInternalMessage",
        "identifier": 468,
        "enabled": true
      },
      {
        "name": "DesignSevenNotificationCenter",
        "identifier": 442,
        "enabled": true
      },
      {
        "name": "ShowMileStones",
        "identifier": 133,
        "enabled": true,
        "value": 0
      },
      {
        "name": "WidgetInvoicedPerMonth",
        "identifier": 446,
        "enabled": true
      },
      {
        "name": "WidgetPlannedAbsence",
        "identifier": 445,
        "enabled": true
      },
      {
        "name": "WidgetProjectEconomyHealth",
        "identifier": 448,
        "enabled": true
      },
      {
        "name": "WidgetAverageHourlyRate",
        "identifier": 449,
        "enabled": true
      },
      {
        "name": "WidgetTimeTrackingDelay",
        "identifier": 458,
        "enabled": true,
        "value": 5
      },
      {
        "name": "WidgetVacationCalculation",
        "identifier": 459,
        "enabled": true
      }
    ]
  },
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v2/features/front-page",
      "Rel": "self"
    }
  ]
}
GET
/v2/features/front-page
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[]