API rootGet the TimeLog news feed

Get the TimeLog news feed

Returns TimeLog's news RSS feed for the caller's language, as raw XML.

Picks a feed URL from the account settings by the caller's profile language — Danish → RSSFeedUrl_DK, Swedish → RSSFeedUrl_SE, English and every other language → RSSFeedUrl_EN (defaults: http://help.timelog.com/<dk|en|se>/feed/) — downloads it server-side, parses it as XML and returns the document unchanged with Content-Type application/xml. The body is NOT the TAF JSON envelope.

Use it to:

  • Show TimeLog product news on the front page.

Not for:

  • Anything account-specific — the feed is TimeLog's public help-site feed unless the settings were changed.

Behaviour:

  • Idempotent.
  • Safe to retry.

See also: GET /v2

Not yet documented: behaviour → consistency; examples (success).

curl -X GET "https://app3.timelog.com/your-account/api/v2/feed" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
"example_string"
GET
/v2/feed
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

The body is returned without the TAF envelope. The remote RSS document re-serialized by XmlDocument (OuterXml), UTF-8, application/xml.