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"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v2/features/front-page"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v2/features/front-page", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://app3.timelog.com/your-account/api/v2/features/front-page", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v2/features/front-page')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"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"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v2/features/front-page
Target server for requests. Edit to use your own host.
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.
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
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
A fixed, code-defined list of feature flags with their current on/off state (a single TAF object, not a TAF list).