Saved filter viewsDelete a saved filter view

Delete a saved filter view

Permanently deletes a saved filter view and all its values by its ID.

Deletes the view and its values. The route takes only the view's integer ID (no page). Deleting the default view does not promote another view to default. A second delete of the same ID, or any unknown ID, fails with 500.

Not for:

  • Clearing a view's selections but keeping it — PUT /v2/filter-view/{pageIdentifier} with an empty FilterValues list

Behaviour:

  • Not idempotent.
  • The first call answers 204; a repeat answers 500 Code 100 (captured).
  • Safe to retry only under a condition. After a lost response, a 500 Code 100 on retry most likely means the first call succeeded; confirm with GET.
  • Duplicates: n/a
  • Side effect: Deletes all values of the view, then the view.
  • On failure: Not transactional: values are deleted before the view row; if the view delete fails, the view remains without values.
  • Changes are visible to the next read immediately.

Call first: GET /v2/filter-view/{pageIdentifier}

See also: PUT /v2/filter-view/{pageIdentifier}

curl -X DELETE "https://app3.timelog.com/your-account/api/v2/filter-view/123" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{}
DELETE
/v2/filter-view/{id}
DELETE
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.
path
idinteger
Required

The view's FilterViewId. No route constraint: a non-integer reaches model binding and gives 400 (captured), not 404.

Format: int32
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.

Path Parameters

idinteger
Required

The view's FilterViewId. No route constraint: a non-integer reaches model binding and gives 400 (captured), not 404.

Responses