Navigation (menus, bookmarks, pages, filters)List my bookmarks

List my bookmarks

Returns the caller's own bookmarks, sorted by name, each with an absolute URL and create / delete actions.

Lists the bookmarks ("favourite pages") of the CALLER — there is no parameter to read another user's. Bookmarks whose page the caller can no longer open (role or licence change, feature off, deactivated report) are silently left out but not deleted. Names are as stored at creation (the creator's language then), URLs are rebuilt absolute.

Use it to:

  • Render the bookmark menu of the web app

Not for:

  • Reading another user's bookmarks — not possible

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Consistency: immediate for the caller's own create / delete.

Next: DELETE /v2/bookmarks/{bookmarkId}

See also: POST /v2/bookmarks

Not yet documented: behaviour → consistency.

curl -X GET "https://app3.timelog.com/your-account/api/v2/bookmarks" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "Id": 123,
        "Name": "John Doe",
        "Url": "example_string"
      },
      "Links": [
        {
          "Href": "example_string",
          "Rel": "example_string"
        }
      ],
      "Actions": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}
GET
/v2/bookmarks
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